d.

I tried it. I was able to select SEOPress from the new set of options, but something about the beta version was crashing my WP dashboard and creating 500 errors. Had to uninstall it roll back to the 0.9.97.22.

Excellent–thanks!

I run into this issue as well. Kind of defeats the purpose of writing in markdown…

Does the newly announced partnership between Cloudflare and Backblaze change this?

They’re now essentially acting as a direct feed for Cloudflare CDN, which would seem to bypass some of the speed issue because the files will now presumably be served from Cloudflare on the front end. I, for one, was drawn to Media Cloud precisely because of this.

There’s nothing showing up in PHP error logs, but while AMP for WP is activated then WP/LR Sync can no longer authenticate and log in. Disabling AMP for WP resolves the issue immediately. This is a new issue–they’ve previously worked without issue together.

Amazon does not need referrer information to process affiliate links. When they give you an affiliate link, then it contains information in that link that is specific to your account. Somebody clicking that link is clicking that special link and explicitly telling them where they came from. A noreferrer in the rel won’t change that or indeed have any effect on Amazon whatsoever.

There are two parts to this. One is a code that is part of the special link. That identifies your affiliate account and allows for segmentation within your account. It identifies which account should get the credit for the referral, but it doesn’t identify where they came from–those links can technically be placed on any site anywhere because they’re simply a URL.

But an important part of the Amazon TOS is that they are very strict on where those links are placed and they track that closely. If I was to place my affiliate link here, for example, and it generated referral sales, Amazon would send me a “please explain” at best or ban me at worst because I don’t own or control this site and it’s not listed among my allowed sites. It is also explicitly a violation of Amazon’s affiliate agreement to obscure the source of the links “such that we cannot reasonably determine the site or application from which a customer clicks through such Special Link to the Amazon Site.”

• This reply was modified 7 years, 7 months ago by d.. Reason: Edit: added direct link to source of quote

Same issue here. Just adding a note in case it helps anyone else…

The WP Rollback Plugin doesn’t work with multisite.

But you can manually overwrite the plugin files–the repository version from the plugin’s download button links to 1.4.1.

Thanks. Have tried that, but it’s not making any difference. Will continue fiddling to see if I can narrow it down. Odd that it only started happening recently, and there haven’t been any other major changes or plugins added other than update to Jetpack 4.5 and WP 4.7.1 release.

-some +same

I had some problem. I eventually traced it to an issue with minification in the Cache Enabler plugin. Disabling javascript minification fixed it.

I tried with and without the Bounce Rate option.

I’ve completely uninstalled and reinstalled it but doesn’t appear to have solved it.

The wp-content, plugins and the host-ga-locally folders are all 755 and the local-ga.js file itself is 644 (also tried changing it to 755).

Have also tried deactivating all plugins (except host locally) but no luck.

Must be something on the server setup, it seems.

I was mistaken–it’s not working on the other site either. I was thrown because that site was still tracking in GA, but it must have been accessing a separate cached version. But checking the local-ga.js file on that install and it’s still empty.

Yes, there’s plenty of traffic to trigger the cron–1M/month. And running it manually with WP Control didn’t seem to fix it. Have also visited with Pingdom Tools and GTMetrix.

Same issue.

Multisite. Working for me on the sites that are subfolders of the root domain but not on sites that are using domain mapping.

The default groups also aren’t being created, which means I can’t add any redirects since I can’t add them to a group.

Redirection plugin activated on per-site basis.

Same issue here, from same camera. I’m still in the process of finding a solution, but in my case it appears to be related to caching and/or minifying of the javascript by Cloudflare or on CDN.

Short version is works normally on uncached pages not running through Cloudflare or CDN but is stuck on loading for cached pages on the same site using exactly the same image file.

Not sure if this is related to your case, but I mention it in case it offers a place to look.

Sean: here’s an example: https://havecamerawilltravel.com/washington-photos/arlington-national-cemetery
I suspect the culprit might be the CDN paths.

+1. This would be a very handy addition.