jackrus60

Version 1.9.16.3 appears to have resolved the issue with the saving of a password-protected page (when logged in). Appreciate the fix.

I am able to reproduce this issue on multiple sites (different themes: Neve, Vantage). I’m not using WooCommerce on either site. Both sites are PHP 8.2.

I tested also and was able to update to 1.9.15.2 and all is working correctly. Thanks for the quick resolution.

• This reply was modified 7 months, 1 week ago by jackrus60.

I’m not seeing the reversion to the old version. Plugin is staying at the 1.9.15 release when I look to update the plugin.

Note: this happens to every site I host where the plugin has updated to 1.9.15. THis is a big issue.

I would love to hear an update – anything – about the status of this issue as I will soon be forced to switch to another event plugin. PLease let us know what the schedule for the fix for this security issue is.

I just checked Font Awesome but so far don’t see any icons for Threads yet. Makes sense that you need an icon to support it. Guess you’ll need an “X” soon too for Twitter. thanks for the quick reply.

No problem! Thank you for taking the time to look at the issue. I manually updated the nav_walker.php file and resolved the issue (temporarily) and passed the accessibility test. Appreciate your support!

thanks! I checked and I do have the most recent version of the Neve theme (which I really like). The space will appear if viewed using the Chrome/Firefox developer tools (the tool understands that there should be a space so it inserts it when viewing like you did in the screenshot). I did the same thing when the accessbility took complained about it.

However, if you view the source code of the page, you will see that the space is indeed missing and that is what is generating the accessibility error. Does that make sense?

<div role=”none”tabindex=”-1″ class=”caret-wrap 2″ style=”margin-left:5px;”><span class=”caret”>

Justin –

thank you! That fixed the issue for me. I re-ran the Health Check and it removed all the critical findings. Very much appreciated!

Thanks!
Rick

thanks, Phil! That’s exactly what I needed to know. I’ve deleted those extra files (per WordFence’s recommendation) and feel better about your confirmation of that.

I also checked the official list of WordPress 5.1 files and these 3 files are on the list!

Unknown file in WordPress core: wp-includes/js/codemirror/jshint.js
Unknown file in WordPress core: wp-includes/js/tinymce/wp-tinymce.js.gz
Unknown file in WordPress core: wp-includes/random_compat/random_bytes_openssl.php

Version 5.1

one thing I noticed is that the sites that have this issue were updated to WP 5.1 automatically (via Softaculous). I see no flagged files for the sites where I manually performed the update to WP 5.1. Must be a difference in the upgrade script (auto doesn’t clear these older files and Wordfence notices them as unneeded files). Can anyone else confirm this behavior?

If this is true it appears we can remove these 3 files (using Wordfence) with no adverse effect…

I am also receiving spam on many of my sites after switching over to V3.

Duh! Thank you. Sorry, should have looked there. Appreciate the response.