katana_one

My solution was to use a different plugin. In the end, the project only needed to pull in the client’s Instagram feed, so I ended up going with Feed Them Social.

Looks like the issue was caused by our host running a legacy version of PHP. Once I convinced them to update, the plugin started working.

Server is running 5.2.9 it seems… Guess I will have to see if I can have the admin update us.

Disabled gzip compression via my wp-config.php file.

That seems to have solved it.

Did I post to the wrong forum?

Just wanted to add that dropping the database and reinstalling also didn’t change anything.

Also, wanted to add that I’ve already tried reinstalling WordPress via the update panel, and also tried manually re-uploading the WordPress core files. Deactivating all plugins has also been tried.

Try this:

Thanks. I had arrived at the conclusion that I would need to include conditional statements in the single.php file last night before falling asleep.

And your last paragraph is correct – in an ideal situation, I only want the category to be restricted if the user accesses the post from the category-specific page.

However, I’m willing to compromise at this point just to get the client off my back. ??

I activated permalinks and I added the TRUE condition to my previous and next links in the single.php file. Which I guess is where it’s supposed to go? But now, of course, I can only navigate between posts in the same category. But what about my “normal” blog (no category filter)? If I go to my normal blog page, I can now only navigate to other posts within the same category as the last post.

Do I need to set up a separate “single-post” page php file? How does WordPress find it and know when to use it?

Maybe I’m just dense, but I’m not getting this to work.