Exo
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Accessibility] Plugin adds a Log Out on admin toolbar?Awesome, that’s so much better now… thanks Joe.
Will leave a 5-star review ASAP, and possibly looking to buy Accessibility Checker via your affiliate link.Forum: Plugins
In reply to: [WP Accessibility] Plugin adds a Log Out on admin toolbar?Thank you for your prompt reply and I look forward to having an option to turn that off, as ironically it’s causing accessibility issues for me, and my client… accidently clicking on it to view the site as it’s in place of the normal view site link, hence me saying it’s bad UX/UI.
Thank you for the official reply, it’s appreciated and make sense. Hopefully you are able to resolve the situation.
as for the moderators choice to delete ‘me too’ replies that’s just farcical of this WP support that will have to create a new topic even though it’s the exact same problem.
Forum: Plugins
In reply to: [Age Gate] Trigger Action after pass age verificationFound another thread, for those landing here this works:-
window.addEventListener(‘agegatepassed’, function () {
// your call here
})Forum: Plugins
In reply to: [Age Gate] Trigger Action after pass age verificationThis answer seems very vague to me, I’m needing the same solution – a simple JS hook or call I can make to confirm if the Age Gate has been as success.
Does anyone have some code they can share?
A real shame the documentation is incomplete, I would have thought the need for a hook was more common if a site has other popups or interaction once Age Gate is done?
Thanks in advance.Thank you, version 3.2.13 does indeed seem to fix this problem.
This is marked as resolved, and yet the problem still exists.
I activated WebP for the first time a month ago, and on 2 versions (and including Version 3.2.12) it causes Beaver Builder to fail.
Is this going to be fixed soon please?@shanedelierrr thank you, I can confirm the latest version now seems to have fixed this.
Please thank the rest of the team who worked on this update.All the best.
FYI
I have an update from David who’s kindly replied to my Pro support ticket asking about changelogs, he says:The changelog missing at www.ads-software.com is due to a line missing in the readme.txt to indicate where it begins, and that has also now been corrected.
So here’s a strange thing, in your actual installation and not easily reachable without FTP there’s a readme.txt
Even more strange is the update which came out today 3.2.9 (5th Oct 2022) is dated almost a month ago…
= 3.2.9 - 06/Sep/2022 = * FEATURE: Import and export settings * FIX: Avoid infinite loop while using unused images export csv * FIX: Scheduled cache preloading issue * FIX: WebP testing making unnecessary background HTTP checks * FIX: Google fonts compatibility with The7 theme * FIX: Prevent console error for undefined <code>wp_optimize</code> for smush scripts * TWEAK: Avoid PHP warnings on cache cleanup * FIX: Ability to disable webp serving while caching is on * TWEAK: Reset webp conversion method flags daily using cron job * TWEAK: Remove orphaned <code>wpo_weekly_cron_tasks</code> cron job upon uninstallation = 3.2.8 - 23/Aug/2022 = * FIX: Build system error led to a missing file in 3.2.7 which could cause an error when using related functions * FIX: Fix incorrect function name in admin class
I’ve just been searching for that too, since this plugin has a terrible track record on recent updates I wanted to read what’s been done before pressing update as I can’t trust auto-updates on this one (even though it’s a great plugin!).
Anyone know where we can find Change Logs now?
Kind of odd it’s hidden as the link (in the plugin option) just shows a white page now.Hi @shanedelierrr, thanks for your reply.
I’ve got this happening on ALL my installations, and all started since the last update. In answer to your questions:-
ALL browser (Edge,Firefox, Chrome etc) -Browser
7.4.32 & 8.0 -PHP Version
6.0.2 -WordPress Version
7.2.1 [latest] -Plugin Version
NONE -Any applicable WordPress/console/PHP errors.
Only debug which @nlpro mentions fixes it, or a reinstall -Steps taken leading to the error notice.If you PM me (is that possible here?), I’m happy to provide admin access to one of the sites for you to double check things.
FYI, I have exactly the same problem all of a sudden since a recent update.
For me it’s on 50+ sites.
I use WP-Optimize too, copied the instructions as above but get another new problem (have opened a support thread on that)But I can’t be doing this on 50+ sites, so I hope you discover what the issue is and update with a fix as I’ve not updated other plugins when this problem started, and as suggested no doubt a clash with something else.
What exact update took place ? (I prefer an answer like: Updated xxx plugin from version x to version y).
Only iThemes Security plugin was updated recently. I’ve not really updated anything else on the majority of my sites.
I mentioned WP-Optimize as I’ve seen it mentioned needs to be added to exclusions for file changes in it’s own folder, but I’ve not updated that for about a month.I use MAINWP to update my sites (100+), and updated 50+ on iThemes Security as it’s one of the few plugins I keep updated very frequently.
Otherwise, I’d be looking at other plugins possibly causing this. But it’s happened before and had been resolved in updates, so I can only hope it will again.
Thanks again for your reply, it’s appreciated.
Curiously I could not remove single entries, but had to delete all of this:-
"last_scan": 171524, "notify_admin": true, "show_warning": true, "email": false, "split": false, "last_run": 1522573523, "last_chunk": false, "method": "exclude",
Trying to remove just “notify_admin”: true, would not do it, upon save and then re-load it would be back.
On removing all of that above, maybe it’s just suppressed the warning and will still fail?
But I noticed a new entry now:
"compare_file_hashes": true,
In answer to your Global settings request:
"build": 4125, "initial_build": 4112,
Curiously, in those settings I can see log_location & nginx_file are totally wrong (possibly from a site hosting change a year or so ago), not sure why they should remain wrong.