Start with the most common. First would be a redirection plugin or redirection directives in the .htaccess file. f you have a redirection plugin active then you will need to exclude the forum slug from it.

If not – are you using the Yoast SEO plugin? If so you will need to enable what it calls ‘ugly permalinks’.

If neither apply then you will see from the links being created that the ursl are being constructed just fine so something is peforming redirection… We can look deeper.

I am curious, however, as to how you created the initial topic? What was changed after that?

Thanks for the response.

I disabled my redirect plugin: nothing. 

Also disabled SEO Smartlinks, which I don’t even remember why I installed to begin with: nothing

“ugly permalinks” were already enabled in WordPress SEO.  I disabled, re-enabled, and finally deactivated: nothing

Since adding the forum I’ve created 2 or 3 posts, updated plugins normally, and backed up the site.  Getting the forum up and running has been my only real change recently and I was having no problems when I finally had it up and running a couple weeks ago.

I am having trouble loading it at the moment as the site is timing out waiting for data from Woopra.

And you’re right. Ugly permalinks have to be turned on.

The important thing here is what has changed on the site since it was working and then stopped. And whatever that is must be causing the permalink to be thrown out during processing. Ans the fact that it was working makes me hesitate to start discussing things like mod_security as that would almost certainly have caused problems – were it going to – from day 1.

It might be worth visiting the forum admin > Integration > Page and permalink panel and updating the forum permalinks but this shouldn’t really resolve this as if they were incorrect I would expect to see 404 pages. and, in fact, I am seeing the correct urls in all of the forum links so the correct requests are being made. But give it a try.

On a side but related note – when I was looking earlier I did notice that your jQuery libraries are being loaded from the Google CDN which will cause issues (not redirection though) with Sp and many other plugins. This codex article explains the problem and what to look for:

http://codex.simple-press.com/codex/faq/troubleshooting/what-is-this-jquery-conflict/

If you are lucky you may be able to turn this off in your theme options.

You, sir, are a genius.  

Solution: went to the Page and Permalink panel.  Apparently this problem was created when I tried to change the page name.  Even though I changed the name back, I guess I didn’t totally change it back.  I also thought that I had done this before the problems started (I’ve been moving from Asia to South America and somehow missed this for a long time).  There was an error message saying something along the lines of “error, page not found”.  Selected the page and updated – All corrected. 

Since you bring them up, I’d like to address two unrelated topics.  

1) Is Woopra causing problems for me?  I rarely use it so I’m going to deactivate for now anyways, but I would like to know if I should ****can it totally.  

2) I read the codex article on Google CDN.  I was using a plugin called “Use Google Libraries.”  I suppose I should can this as well, although I haven’t had any problems that I know of with it.  I’m not sure if a plugin specifically designed to integrate Google CDN with WordPress would resolve such issues.  

I know those have nothing to do with S:P and you’re probably busy dealing with relevant problems.  Again, thanks for all your help.  I feel like a complete moron.  

Curious, Se we had it around the wrong way. it is the 404 status page that is getting redirected! Glad we found it.

I don’t really know anything about Woopra short of hearing of it and looking it up once. But I spent around 10 minutes trying to get onto your site yesterday with it timing out on every attempt because it was waiting for Woopra. But this is pretty common any any site that makes third-party http requests. I commonly have to wait for users sites while it sits and waits for FaceBook to respond for example. (I know the user often won’t put the blame on FaceBook as well!)

As to using Google libraries the plugin is good simply because you can turn it on and off. I would argue that the saving in time can be calculated in nano-seconds! But if it works – then great – leave it be. But if you have any problems with SP – like being unable to open the editor, or popups not popping up – then it should be the fist thing to turn off for a test.

Thanks.  Woopra is out.  I don’t get enough traffic to make it worth while anyways.

I’ve disabled the Google Libraries plugin as well.  Nano-seconds aren’t that important and I again don’t get enough traffic for it to blow up my server.  But I’m still confused.  When I do a search for “jquery” in source code, I’m given dozens of different options.  

Selecting the first one results in this:   http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js?ver=1.7.1

Selecting one halfway down the list results in this:          http://thisgringotravels.com/wp-includes/js/jquery/ui/jquery.ui.resizable.min.js?ver=1.9.2

This is with the plugin deactivated.  Sometimes I just think I’m in over my head with this blogging thing, but it always works out one way or another.  🙂

Stick with it – it’s worth it!

The two things to be concerned about are ‘jquery.xxx.js’ and ‘jquery.ui.core’. or variants of either of those. Other jquery components – such as ‘jquery.ui.resizable.’ are add-on libraries and it would be rare to see a theme or plugin add a custom version of those. So there are usually just the two to worry about.

The key points are that (a) they should ALWAYS be loaded from the ‘wp-includes’ folder of your WordPress install and (b) should NEVER be loaded more than once.

So yes – that first loading via ajax.googleapis.com is troublesome. So – this means that the plugin to load it from google was masking the fact that you still have another component – WP theme or another plugin – misbehaving.

So – let’s check if it is the theme. Go to the Wpo admin > appearance > theme editor and open it and load the theme’s ‘functions.php file.

Scan down the code and look for any line that contains ‘googleapis.com’. If it is there it will be a small block that calls functions like wp_register-script(), wp_enqueue_script() etc. If you find it – copy three or four lines of code either side of it and paste it here and we can tell you how to fix it.