erikdebye
Forum Replies Created
-
Forum: Plugins
In reply to: [Meta for WooCommerce] Slows down pagesAlso experiencing this issue. Our Host also identified that cookies are preventing batcache from working.
I unfortunately am still having this issue, now with additional sites. It’s fairly clear that this is more than likely a hosting issue, but per the host’s previous response it isn’t a timing issue. This is almost certainly not a conflict with any particular theme or plugin, as I am now experiencing this issue on multiple sites on the same host with different themes/plugins.
Example Site 1:
Theme: Avada v7.12.1
Plugins: ACF Pro v6.4.2, Avada Builder v3.12.1, Avada Core v5.12.1, Breeze v2.2.11, Gravity Forms v2.9.9, Imagify v2.2.6, Object Cache Pro v1.23.1, Post SMTP v3.2.0, Safe Redirect Manager v2.2.2, WP 2FA v2.8.0, WP All Export Pro v1.9.10, WPS Hide Login v1.9.17.2, Yoast SEO v25.2
Example Site 2:
Theme: Custom ACF-Block Theme
Plugins: ACF Pro v6.4.2, Ajax Load More v7.4.0.1, Ajax Load More: Pro v1.3.1, Akismet v5.4, Beautiful & Responsive Cookie Consent v4.6.1, Better Search Replace v1.4.10, Gravity Forms v2.9.9, Gravity Forms Akismet Add-on v1.0.1, Header Footer Code Manager v1.1.40, Imagify v2.2.6, Jetpack v14.8-a.3, jetpack Protect v4.1.0, ManageWP Worker 4.9.23, Safe Redirect Manager v2.2.2, WP 2FA v2.8.0, WPS Hide Login v1.9.17.2, Yoast Duplicate Post v4.5, Yoast SEO v25.2
A third site is using a custom Genesis theme.
Additionally, I ran some testing with only having the 2025 theme active, with no plugins enabled, and still was not successful in logging in, but I did not reset my QR configuration. Are there any other reasons a hosting configuration could cause an issue? Outside of a timing issue?Hi Lucian,
By resetting, I mean that when the App-based OTP is failing I will usually deactivate the plugin via SFTP and login. Then, reactivate the plugin and head over to my user profile to click the “Change 2FA settings” button and delete the entry from the App. Then re-scan the QR code to add the site back into my app.
This will work for a day or so, even after repeated logins, but eventually fail in 24 hours+. Originally I figured this was a result of an environmental issue, but I am using the site on numerous sites with similar environments on the same host without issue. I also am experiencing the issue on a site we just acquired that is a completely different setup (we mainly use Avada, this new site is a custom theme). The issue will reappear even without changes to the site after a “reset”.
As for Apps, I am using Microsoft Authenticator (Android first, then iOS) and my colleague that is also having these issues is using Authy on iOS. She has also done the whole “resetting” process and sees the same issue.
I did recheck the email OTP this morning and that is still working, so the issue certainly seems limited to app-based OTPs.I’ve switched to using email on a site and after 24+ hours I can confirm that this method seems to be working.
I’ve only noticed the issue with the app-based OTP after an unspecified amount of time (24+ hours) after set-up or resetting the App OTP.
Note, that since I’ve opened my ticket I also got a new phone on a different OS, but the issue persists.Sorry for the late reply. I have check with the host and across two of the sites with this issue, both sites are within a few seconds of UTC. The issue still persists, and I will be more responsive going forward.
Edit: added image from hosting support- This reply was modified 1 year ago by erikdebye. Reason: Added image
Forum: Plugins
In reply to: [YITH WooCommerce Gift Cards] Fatal error: Uncaught TypeError: in_array():Hello,
I have the same issue when using the paid plugin. I have implemented your suggested solution above, and it did fix the critical error.
Thanks!Hi Maxime,
I can confirm that this has been fixed in v1.9.16.7! Thanks! 🫶Forum: Plugins
In reply to: [WPS Hide Login] Error 404Hey sf,
I am having the same issue and opened this topic here: https://ww.wp.xz.cn/support/topic/not-using-avada-404-template-correctly-or-redirecting-to-404-page/
The problem appears to affect versions above and including 1.9.16. Saving permalinks again did not solve the issue.One last note: I have this installed on a few sites, and can confirm that the template is being used correctly on v1.9.15.2, where I have the redirection URL as /404/ and an Avada 404 layout template in use. So the issue arose potentially as early as v1.9.16 through the current v1.9.16.6.