Timothy Jacobs
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Mail Debugger] Blank page after upgrade to WordPress 6.6Sorry about that @pyereniuk. I’ve just pushed an update to add WP 6.6 compatibility, you’re right it was due to the Polyfill removal. I also threw in a couple of new features.
Hi @borjamerino,
As @nlpro mentioned, WordPress does include the
sodium_compatlibrary which should ensure that the needed PHP functions are always defined. However, the compatibilty library isn’t always loaded which is causing this fatal error.We’ve opened a Core Trac ticket to fix this issue. However, we’ll also be updating iThemes Security to account for this scenario in the next update.
In the meantime, you can also reach out to your hosting provider and ask them to update the
libsodiumlibrary to the latest version.v1.0.11, what you have installed, is many years outdated.Hey All,
The UI holds onto unsaved settings in a local cache. We don’t want you to lose your progress if you navigate away from the page to read things like documentation.
We have it as a separate button so that you can adjust multiple settings for a feature at once and you can easily undo your changes if you change your mind.
As you mentioned, the indicator that you have unsaved changes is that the “Save” and “Undo Changes” buttons become active. We’ll explore additional ways to make it more clear when you having pending changes that need to be saved.
Thanks for the report @nlpro.
We’ve fixed this on the latest development version and the fix will be included in the next release.
I’m sorry you’re experiencing this issue @xberg, @nlpro is correct, you’ll want to look for errors in your browser console. That’s really the only way we can figure out what is causing the issue.
@simkog I’m glad you got your issue sorted. For future reference, the issue is that removing the query string from the script URLs prevents your browser from “busting the cache” and will end up serving stale versions of JavaScript files. We wouldn’t recommend using a code snippet like that without some other mechanism of “busting the cache”.
Hi All,
We’ve just released 8.1.2 which should fix this issue for you.
I’m sorry for the inconvenience.
– Timothy
Thanks @nlpro, that typo has been fixed!
Hi All,
I’m sorry for the trouble. We’ve identified the issue. An update is planned to be released tomorrow.
Thanks for the report! We’ll get this fixed in the next release.
From Peter Smits in Slack.
as far as I can see the lines mentioned were not translated, and one was set to fuzzy, because it was translated incorrectly. I modified the lines mentioned, so they should be sent as update to the installations
It looks like those three strings are appearing in GlotPress now.
Thanks for the ping @nlpro. Yeah, I’m not sure at the moment what would cause this but I’ll see if I can find out.
Yep, we’re working on a fix, but as @nlpro mentioned, it is a bit tricky.
The reason for the conflict is that both plugins were intentionally developed with the same API so that when the Two-Factor Feature Plugin is eventually merged into Core, there could be a seamless transition process. However, the plugins were never meant to run side-by-side and in the intervening years, the code bases have diverged a bit.
Hi @juvebalkan,
I’m sorry you ran into this issue. We’ve made a fix in the latest version of the plugin, 8.0.2, which will correct the issue going forward. Unfortunately, the easiest way to get back into iThemes Security would be to delete and then reinstall iThemes Security.
Hey @mmubashar,
For the settings that have been removed, the corresponding code has also been removed. So you shouldn’t have to make any changes to your site to get iThemes Security to our recommended configuration.
Your Server Config files (.htaccess) should have been updated automatically. If you see that they still have straggling references to those old settings (this could happen if there are issues with cron jobs firing on your site), then you can manually flush them. Go to the “Tools” menu, select “Server Config Rules” and then click “Run”. Alternatively, you can copy and paste the generated rules and manually edit your
.htaccessfile.The difficulty we had was in communicating the difference between iThemes Security not managing updates when “none” is selected, but that doesn’t mean there won’t be no automatic updates since in that case the native WordPress UI controls would be available.
Suggestions for better phrasing are definitely welcome!