brunochartier

Reading the provided screenshot, the text “Never miss an important update… etc.” as well as the section “what permissions are granted” is far from clear that the WordPress account email address is used to register to an external service. It is very easily confused with a simple optin/out for local usage of local data by a locally installed plugin.

I’d strongly suggest clarifying the message and implement an optout approach instead. For example:

<li>
  <ul>changing the "Skip" button to be the default obvious choice and to be "Continue without subscription",
</ul>
<ul>changing the "Allow & Continue" button to "Subscribe to our great services and Continue"</ul>
<ul>
Also make it clear in the granted permissions that the email is used to subscribed to and create an account with freemius.com</ul>

</li>

Thanks!

• This reply was modified 5 years ago by Jan Dembowski.

same problem happened here on on 4.7. a few hours ago.
I confirm that no files were changed (compared with full files backup) and only the last post was “hacked” with previous revision still present.

Crawling a bit through Apache logs, I see weird IP address from Linux doing this:
POST //wp-json/wp/v2/posts/4929

I noticed that an empty user name is listed in the “Current Revision by…” text.

My plan of action: 1) updat to 4.7.2 (and hope for the best) and 2) restore previous revision of the post…

Hope to hear from WordPress soon on the matter.

Thanks Chrysti for checking it out.
I have tried up to 1024M of memory limit. Then the problem becomes the max_execution_time. When that is set to 300s (5min) then the request eventually times out in the browser I guess and without further error logged. Sounds like some serious memory allocation loop going on.

Some more digging shows with polylang 1.8.5 and keeping YOAST 3.1.2 activated but deactivating Lingotek also resolves the issue of accessing the plugins.php.

got similar issue preventing me from accessing plugins.php.

Looks like polylang 1.8.5 and YOAST SEO (wordpress-seo) 3.1.2 are incompatible.
downgrading YOAST SEO (wordpress-seo) from 3.1.2 to 3.0.7 fixed my issue.

further investigation actually points not to Lingotek but to upgrade from polylang 1.7 to 1.8.5 and upgrade of Yoast SEO from 3.0.7 to 3.1.2

resolved issue by downgrading Yoast to 3.0.7