Bielousov

There are 2 options: delete and mark as Ignored for each report.
It would be awesome if we could also mark them as “Done” (or Addressed/Resolved/Fixed, etc.), to keep track of all fixed errors, as opposed to deleting or ignoring them.

Using APO (with W3C Total Cache) and still logged in user page hits are cached and served to non-authenticated users. This was the reason I enrolled to the APO in the first place.

cf-apo-via: origin,cookie
cf-cache-status: HIT
cf-edge-cache: no-cache
cf-ray: 64a41f342bc94bc5-YUL
cf-request-id: 09da71d49a00004bc5d9360000000001
nel: {"report_to":"cf-nel","max_age":604800}
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=lOplVBJdWVv3FWjTLYylASc1oqjqUJhFzEZF0b4JUO5dkLov6ah9QhMLQswxlnWo33gXulY9L7ihcESdmw5xydY2fEcx0AadvEI%2BHn%2F%2B4jxHig%3D%3D"}],"group":"cf-nel","max_age":604800}

• This reply was modified 3 years, 11 months ago by Bielousov.

Had the same issue after I updated PHP 5.6 > 7.0 > 7.1 and cleaned up older versions. I checked PHP logs and found there:

PHP Fatal error: Uncaught Error: Class 'DOMDocument' not found …

Apparently php-xml module was missing.
Had to install it on Ubuntu:
sudo apt-get install php-xml

And AMP started working again.

• This reply was modified 7 years, 11 months ago by Bielousov.
• This reply was modified 7 years, 11 months ago by Bielousov.

Funny that SumoMe thinks they should follow Facebook strategy and not combining counters. The FB counters/share buttons are tools but not a marketing platform by itself, I guess so is SumoMe then and if you’ve been looking for one, keep looking.

AddThis, Shareholic, Mashare they all think different, for they understand the value of a higher counter on page is better for branding rather than blindly following a social network guideline. To bad I found this out after spending all the time to implement SumoMe on my site.

Although the Like button doesn’t work the way FB intended it to work, it opens a modal instead of +1 in-place, so it’s useless UX-wise. Why wouldn’t SumoMe start following the FB logics from there?

A smart company would keep following FB guideline AND develop a combined counter.

Now I have to roll back all my changes only due to the fact that SumoMe team made a wrong decision at some point. And of course there goes a negative feedback to the plugin too for my time wasted.

I installed IME only for EXIF, not for so called “better quality”.
But those who don’t need it, may find Google Page notification that images are not optimized annoying indeed.

Have the same issue for 1.2.8.2 but only for some posts (in Russian).
Will use the fix from 1.2.5 above for now (reverting line 156 in wordpress-seo/inc/wpseo-functions.php fixed it) but I hope it won’t be broken again after next plugin update.

The page that was broken example