• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

404s on all external and internal links to forum threads

Joined
Jan 14, 2011
Messages
3,413
Location
St. Louis
I've noticed this happening on any links to forum threads inside or outside of the site. Apparently there was a change some time ago that modified the directory structure of the site. Google still has nearly everything indexed and ST threads still show in the results, but they all 404.

For example, this thread shows up in Google:

But the actual URL is now:

It appears that the issue is the "community" subfolder used to be in the URL, and now it isn't. This should be easy to fix with either a htaccess 301 redirect rule or a setting within the forum itself to add "community" back into the site structure. I think the htaccess option would be less likely to cause issues, as the other may require a deep overhaul of the database.

The 301 redirect rule would simply be that for any url containing /community, it would replace "/community" with "/". For example:

/community/threads/name-of-thread

would forward to

/threads/name-of-thread

The cost of not fixing this is not just all of the 404s making threads unreadable to potential visitors, but will be a huge loss in SEO. All of the old URLs have tons of backlinks that boost the site's overall search engine rankings. To search engines, the site is basically starting from scratch in its backlink profile and page indexing.
 
Last edited:
I've been reading through old threads for the last few years and noticed this a lot. I don't know much about website design and figured they were lost to the ether, so I never bothered to mention it. If it could be squared away that would be awesome, but again, I don't know how involved that is. Just happy to have all the info I have been able to access.
 
The URL's changed about 2 months ago. I used a quick find/replace to fix the links coming from my site. Google will eventually update but there may be a way to redirect anything in /community/ to the same URL without community to maintain continuity.
 
Back
Top