GerryBot

I would implement a regex redirect, something along the lines of

/careers/(.*?)$

and redirect it to /jobs/ That should take care of anything under the careers directory.

Thanks for getting back to me on that – I see a lot of attacks using the domain name or different types of admin account, so I want to block those as well.

My workaround is to press Escape to hide the media uploader and then save the post as a draft. When the page reloads, all the media functions have been restored.

Yeah, that’s the function. What I’m trying to do is inject it into the content, after the second or third paragraph to show some featured posts we’d like to highlight.

At the moment, I’ve manually inserted the code, but I’d like to automate this using a filter method like this: https://www.wpbeginner.com/wp-tutorials/how-to-insert-ads-within-your-post-content-in-wordpress/

Here’s roughly what I’m working from. https://pastebin.com/kpXexTBa

Obviously there’s another function in the single.php file that references this. If I put the code within the loop, it goes nuts and affects the post being displayed. However, if I put the code outside the loop, it displays as intended. How do I make this function work independently and not wreak havoc with other posts?

Hey everybody. We’re having the exact same problem on our Unreality TV site. We use categories as part of our permalink setup, and when Publicize posts these to the Facebook page, it’s dropping the category from the link. Here’s the link to our Facebook page (the links that *do* work are from a separate WordPress install where permalinks are simply post_title).

https://www.facebook.com/unrealitytv

Obviously changing our permalink structurwe at this stage is not an option. Is it worth backtracking to an earlier version of Jetpack?

Rahul: The earlier code sample runs a bit out of control since it’s not directed at a specific resource it simply blocks all access to the site with a 403 Forbidden error.

if ($http_cookie !~* "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX") {
                        return 403;
                }

Would it help to look at the Apache rules to see how the same effect is achieved? This is what they tell you to use in your .htaccess file.

RewriteCond %{HTTP_COOKIE} !^.*xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.*$
RewriteRule ^wp-comments-post.php - [F,L]

Thanks for that! Would you suggest putting that directive up above the location blocks in my Nginx rules then, @rahul286?

As a crude hack, I’ve set the refresh function to run whenever the settings page is loaded. This seems to do the trick for now, but I’m sure there’s a more elegant way to code this…

Glad I stumbled upon this thread – I’m running WP-SEO on an Nginx-based system, and I thought it might have been a problem related to Nginx.

I have exactly the same problem – the sitemap reports being built, but the sitemap files don’t exist in the WordPress root. After a bit of digging, I discovered that they were in wp-content/uploads/wpseo. It seems the plugin is generating the files, but not moving them to the root of the WordPress install. I could handle this via a rewrite rule, but if there were plans to fix this it would make things easier!

Just wanted to jump on here and say that I have two sites, same hosting, one a subdomain of the other – both are using Total Cache and FeedBurner, but one has experienced this problem while the other has not.

I’ve disabled feed caching for the moment and it’s returned to normal, although some amount of caching would be desirable!

One other thing I’d mention – the site that had the issue with feed caching also had a bizarre issue with using the APC opcode options – using that option stopped pages from loading. Again, the other site appears to be just fine. Don’t know if it’s related, but I thought I’d mention it just the same.