andypp
Forum Replies Created
-
The debug.log was already active, but nothing was written during the deletion attempt.
I’ll open a support request via the email address you provided and include the details and screenshots there.
Thanks!
Thanks for your reply.
Right before my latest test I cleared the old logs. After starting the deletion again, it stayed at 0% (“Cleaning Up Staging Site Tables”) and no new entries were written.
WP STAGING Logs panel: https://postimg.cc/grC1nJ14
Do i still need to email you the exported log files from WP Staging → System information?
Thanks
Hi, just an update on my tests:
I cleared both the WP-Optimize cache and the Redis object cache, and then ran the preload again.
This time, the plugin successfully detected and cached all URLs without any errors.
Thanks for your help and support!
Best regards
Hi, thanks for your reply!
- I’ve checked the sitemap_index.xml and confirmed that the total number of URLs listed across all sitemap files is well over 7,000.
- I did find this error in the debug.log, although I’m not sure if it’s directly related:
[24-Jul-2025 13:25:11 UTC] PHP Fatal error: Allowed memory size of 273678336 bytes exhausted (tried to allocate 4198400 bytes) in /usr/www/users/wmbicom/wp-content/object-cache.php on line 2553I’ll try another test to verify whether this memory issue is affecting the preload process and I’ll report back with the results.
Thanks again for your support!
Thanks for the quick fix, everything works perfectly now! Much appreciated 🙏
Thanks for the follow-up.
I checked the
debug.log, but it was empty — no specific errors were logged.
Unfortunately, simply reverting to the previous plugin version wasn’t enough to restore access to wp-admin. I had to restore a full database backup to get the site working again.
It was quite a mess, to be honest.Let me know if there’s anything else I can check.
Thanks again.
Thank you for your reply.
Here is the requested information:
- WordPress version: 6.6.2
- PHP version: 8.0.30
- Database server version: 10.5.26-MariaDB-log
Thanks again.
That fixed it, thank you!
I have contacted your customer care specialists via the provided form to request the fixed zip file. I’ll follow up with them directly for further support.
Thank you again for your help!
Thank you for your reply.
Here are the details you requested:
Poll Maker plugin version: 5.5.1.
PHP version: 8.0.30.
WordPress version: 6.6.2.
Video demonstration: https://streamable.com/p79pme.
Website link: keblog.Please let me know if you need any further information.
Thank you for your assistance!
Thank you for your reply.
Here’s a link to a screenshot showing the issue on the “Statistics” tab for a poll with active votes: https://ibb.co/GCdrLTx
Here is the additional information:
WordPress version: 6.4.5
Poll Maker plugin version: 5.4.8
URL of the page where the issue occurs: /wp-admin/admin.php?page=poll-maker-ays-results-each&poll=7&title=TITLE (where TITLE is an example)Thank you.
Thank you for your detailed response.
I apologize for the confusion. After further testing, I realized that I was not logged in on mobile and was logged in on desktop. Since my caching settings are configured to bypass the cache for logged-in users, this explains why the issue didn’t occur on desktop, as I was seeing the non-cached version of the page.
I’ll try adjusting the cache expiration time for non-logged-in users.
Best regards,
AndyThank you for your response.
I understand the limitations regarding dynamic content and caching.
I would also like to mention that I’ve discovered the issue occurs only on mobile browsers (iOS Safari and Chrome, in my case). On desktop (Chrome), when I reload the page after voting, the results are correctly displayed according to the settings.
If this additional detail helps in any way, please let me know.
Thank you again for your assistance!
The polls are integrated directly into the articles, which are the most important and frequently visited pages on the site. Therefore, excluding the articles from caching isn’t a viable option as it could negatively impact performance.
Since the articles need to be cached, it seems that the only option is to reduce the cache expiration time.
Do you think this approach could work, or would you recommend any specific settings or alternative methods to balance caching performance with dynamic poll updates?
Thank you for your assistance!
UPDATE: I had the ‘Disable Share Options Meta Box’ option selected in the Settings section under General. After I deselected this option, the errors disappeared. However, having to deselect this option to resolve errors is not a desirable solution.