holstebm

Hello,

I think this should do it, assuming you are just caching GET requests:

add_filter('nginxchampuru_get_reverse_proxy_key', function($url){
    $url_key = preg_replace('/(https?):\/\//u', '$1GET', $url);
    return md5($url_key);
});

Add that to your themes functions.php…

Let me know if that helps.

Sorry, yes, solved…I posted here in error in the first place. However, since I did not originate this thread, I cannot close this issue on my own.

My fault…it appear the Head Cleaner plugin replaces the script tag type to text/javascript and wraps the data in CDATA.

The problem is NOT with this plugin but the inappropriate changing of the defined type by the other plugin.

I was originally searching for ld+json which is why, in a large document, I couldn’t find the markup. That string had been replaced by Head Cleaner.

I verified that this data is not showing up via the Google Structured Data Testing Tool and by manually viewing the page source looking for applicaiton/ld+json script tags. In both cases, nothing was found.

On Feb 27, 2016, this plugin suddenly stopped working. It was working perfectly for weeks before but my Google Webmaster Tools shows a drop off of all schema data between 2/26 and 2/27.

The plugin is still installed. Also, I have this plugin installed on more than one site and it fails to produce output on the others as well.

Not sure what is going on here but I am unable to get schema output on any site where this plugin is enabled (I have also tried activating/deactivating, uninstall/reinstall).

I should add that the network in (A) is NOT the primary network under which multisite was installed but one of several secondary networks.

Also, all networks work properly. It is the subdomains under the networks that seems to be having issues.

I now see the directory statically set. I have moved my content and plugins directory so if this relies on wp-content, it wouldn’t work.

This wasn’t a limitation in the previous version. Not sure what the best fix would be for this. Is there any chance that this will be changed in the future?

errr, that would be switching back to 1.3.2 of the plugin, not WP 3.2

I am having the same issue. Redirect loop. I see the original poster is using Apache. I am using Nginx (with the rewrite rules).

Just so their is an abundance of information, I am using WP 3.5 Multisite in a multi-network configuration. On one network I do not use, I deactivated *all* other plugins except WordPress SEO. I am also used the TwentyEleven theme to eliminate all other variables.

I still get the redirect loop. I did not get the redirect loop in any previous version of WordPress SEO. I am going to move back to 3.2

I am not certain how my configuration compares to the others posting here.