hannahdapplecreative

Hi there, just been investigating this further.

The source code (var gdpr_consent__advanced =) still returns “true” when it shouldn’t. I tried checking if the plug-in is working in a different way: View the site in a private/incognito window, refuse cookies, then check if cookies are still being set (Chrome > Inspect > Application > Cookies). When I check this way, the plug-in appears to be working:

• If I accept: {“strict”:”1″,”thirdparty”:”1″,”advanced”:”1“,”performance”:”1″,”preference”:”1″}
• If I refuse: {“strict”:”1″,”thirdparty”:”0″,”advanced”:”0“,”performance”:”0″,”preference”:”0″}

I also tried checking re: Google Analytics, to see if it tracks me being on the site in ‘realtime’ and when I accepted, it did track me on realtime analytics and when I refused it didn’t.

So it does look like the plug-in is working. My question is, is that source code snippet (var gdpr_consent__advanced =) supposed to update based on what the user clicks? If it is (= true if accepted, = false if rejected), why isn’t it toggling correctly?

Thanks!

We are on Version 3.7.22. However, we don’t feel comfortable updating because we already know (via testing on our Dev site) that 3.8 will not work and will cause issues on our site (that we originally flagged in the first thread). Our developer looked at the 3.8 code and saw that the fix we needed wasn’t applied so we’re wondering when it will be.

Thanks!

Thank you!

Hi there,

Apologies for the repeat messages, but our developer was able to identify the issue and fix the problem we were having with your plugin using code. Please see the below. Is this something that could be implemented in the official plugin so when we update the plugin/WordPress in future everything works as expected? Thank you!

The basic issue is that in the recent update to the plug-in, Nonce verification was added to the “create revisions” Ajax handler, but it was only updated for the block handler and not the classic editor.

So the classic editor JS fails, and although it believes a revision was created successfully, it really wasn’t, and so the link to Edit the revision also fails and goes to the front end.

We added the nonce keys to fix this.

In the file “post-edit_rvy.php”, around line 130, we added the following code:

$args[‘createRevisionNonce’] = wp_create_nonce(‘create_revision’);

$args[‘submitRevisionNonce’] = wp_create_nonce(‘submit_revision’);

$args[‘createScheduledRevisionNonce’] = wp_create_nonce(‘create_scheduled_revision’);

$args[‘authorSelectNonce’] = wp_create_nonce(‘author_select’);

This provides the required nonce for the classic editor, and now things appear to work as expected.

There could be more to this, as we didn’t do a thorough investigation, but started where it made sense. As this appears to work, it’s probably a good starting point for the plug-in developers to look at.

Thanks, Steve. We just did a few tests.

We set the theme to be the most recent version of 2025. (the standard WordPress theme) which uses Gutenberg, to ensure nothing else in our theme is causing the issue.

Then we tested each of these two plug-ins, and in both cases, the Revisions plug-in did not work as expected. So it does not appear to be compatible with “Classic Editor”.

Classic Editor: https://en-ca.ww.wp.xz.cn/plugins/classic-editor/

Classic Editor+: https://en-ca.ww.wp.xz.cn/plugins/classic-editor-addon/

We are going to keep investigating on our side but any help you can provide would be great. Thanks!

Thank you for your help. I had a developer on our end look into this and we’ve identified the issue: Our theme disables the newer ajax based Gutenberg editor, in favor of the older editor. With a theme that only uses the new style editor, the Revisions plug-in does work. It seems any plug-in or theme which favors the older style editor is not compatible with the Revisions plug-in on the newer version of WP.

Would your plugin team be able the Revisions plug-in compatible with the older editor? Having to re-do our theme just to make this plugin work would be timely and expensive. We could upgrade to Pro if necessary.

Hi Riza,

Thanks for your help. Perhaps with the theme on our website, it is different. Please see below and let me know what you think. Thanks!

Here is what is happening on my Production site (which is working, and is how I’ve used the plugin for months): https://drive.google.com/file/d/1bE8k-oqQXsFbPbCS1qZLn3ZPO8V5z92L/view?usp=sharing

Here is where the issue is, on my Development site (which has updated WP to 6.9, Prod has not): https://drive.google.com/file/d/1gPnQNQlqGGKK22p3uvPSWORyzh8fd354/view?usp=sharing

As you can see when I’m on a page on Production and click ‘Create Revision’ then ‘Edit’, it opens up a new tab of the backend of the page where I can do my revision. After updating to 6.9 on Dev, when I click ‘Create Revision’ then ‘Edit’ it opens up a new tab of the FRONT end of the original page and I can’t revise anything, because if I go to ‘edit’, it just takes me back to the regular page and nothing saves as a ‘revision’. There’s no options under ‘publish’ to update revision/approve revision, etc as there is on Prod.