mountbest
Forum Replies Created
-
I have upgraded Simply Static plugin to v 3.5..5 and its processing time jumped from 46 seconds to over 8 minutes. Is this normal?
[2026-01-12 11:50:16] Setting up
[2026-01-12 11:50:25] Fetched 1504 of 1504 pages/files
[2026-01-12 11:56:22] 404 Page generated
[2026-01-12 11:58:27] ZIP archive created: Click here to download
[2026-01-12 11:58:27] Wrapping up
[2026-01-12 11:58:27] Done! Finished in 00:08:11
Hey Patrick
My LiteSpeed server account has a cPanel utility that can disable LiteSpeed WordPress caching. So, if users have access to cPanel on their LiteSpeed server accounts – there should be no problems using Simply Static with LiteSpeed servers.
I use Simply Static for at least 2 years with WordPress Elementor website on a LiteSpeed server and this was the first time I encountered a problem. I was tempted to try older versions of Simply Static…
With 301 redirects – you can offer users a choice: to ignore these redirects or suggest that they reorganize their website to avoid redirects. But I suspect that delay in 301 redirects can be avoided by properly disabling all caching.
BTW. Elementor image carousels do not work in Simply Static generated website. They are frozen on the first image, Manual links to next and previous images are shown, but they do not work.
Tom
- This reply was modified 4 months, 2 weeks ago by mountbest.
Done some debugging and I saw that the plugin was instantly attempting to use more than 756MB of memory (exceeding the PHP memory_limit) resulting in the error.
I’ve manually configured PHP memory limit via .htatccess file to utilise the maximum available memory of my hosting service (2GB), along with some timeout rules:
php_value post_max_size 2048M
php_value memory_limit 2048M
php_value max_execution_time 0
php_value max_input_time 0It now appears that the plugin is running successfully.
P.S. This issue occurred only with LiteSpeed server. There is no such a problem on AlmaLinux , Apache and Nginx servers
BTW, the error triggered by Simply Static was
PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 172032 bytes) in /home/…/public_html/wp-includes/class-wpdb.ph
- This reply was modified 4 months, 2 weeks ago by mountbest.
No issues at the moment. But previously CleanTalk was working ok for some time and then suddenly stopped working.
I would appreciate email notice if any of my domains becomes out of synch with your server.
It works OK, thank you. The problem must have been with php initialization variables conflict, so php (and WordPress) could not load. Am I correct?
I am happy to wait for official release. I was suspecting some plugin conflict, but I have never seen a conflict so severe.
- This reply was modified 5 months, 1 week ago by mountbest.
After installing version 6.70 on my multi site the entire server was not accessible. There was “server error” before any php could be executed and before WordPress could load. Could not access WordPress dashboard. I had to restore the system from the backup and then prevent CleanTalk plugin from updating to have a system that works.
I actually tried TWICE to update to 6.70 and then revert to working backup with version 6.69.2 to MAKE SURE that the update to 6.70 is the exact culprit that crippled my server and caused hard server errors.
Because I had to restore functioning system from backup – no logfiles exist anywhere in the WordPress installation. I do not want to risk damaging the server functionality again by installing CleanTalk update that crashes the server with some misconfiguration…
Your developers should know exactly what they changed between version 6.69.2 and 6.70 that can affect multi site.
your hypothesis cannot explain why 14 websites on several servers in different countries were affected on the same day, reporting invalid access keys.
Forum: Plugins
In reply to: [Easy Updates Manager] Plugin reported updated, but deactivated !!EUM updated the Oxygen plugin on my multi-site without problems. The single-site encountered the deactivation glitch. For this reason I suspected some malicious interference and checked all error logs.
It would be REALLY NICE if EUM checked if the plugin is active after update and either reverted to previous version, alerted the User and/or activated the plugin.
Occasionally some plugin conflicts or transient condition occur during updates and automated tools such as EUM should be vigilant. For now I excluded Oxygen plugin from automatic EUM updates, so I can test everything during a manual update.
Thank you for your help
Forum: Plugins
In reply to: [Easy Updates Manager] Plugin reported updated, but deactivated !!no php errors anywhere. Here is a trace from your plugin
1 wp-cron.php (191): do_action_ref_array(‘wp_update_plugins’)
2 wp-includes/plugin.php (565): WP_Hook->do_action(Array(0))
3 wp-includes/class-wp-hook.php (348): WP_Hook->apply_filters(”, Array(0))
4 wp-includes/class-wp-hook.php (324): MPSUM_Disable_Updates->maybe_auto_update()
5 /plugins/stops-core-theme-and-plugin-updates/includes/MPSUM_Disable_Updates.php (191): do_action(‘wp_maybe_auto_update’)
6 wp-includes/plugin.php (517): WP_Hook->do_action(Array(1))
7 wp-includes/class-wp-hook.php (348): WP_Hook->apply_filters(”, Array(1))
8 wp-includes/class-wp-hook.php (324): wp_maybe_auto_update
9 wp-includes/update.php (861): WP_Automatic_Updater->run()
10 wp-admin/includes/class-wp-automatic-updater.php (676): WP_Automatic_Updater->update(plugin, Object(stdClass))
11 wp-admin/includes/class-wp-automatic-updater.php (487): Plugin_Upgrader->upgrade(oxygen/functions.php, Array(4))
12 wp-admin/includes/class-plugin-upgrader.php (237): WP_Upgrader->run(Array(7))
13 wp-admin/includes/class-wp-upgrader.php (988): do_action(‘upgrader_process_complete’)
14 wp-includes/plugin.php (517): WP_Hook->do_action(Array(2))
15 wp-includes/class-wp-hook.php (348): WP_Hook->apply_filters(”, Array(2))
16 wp-includes/class-wp-hook.php (324): MPSUM_Logs->log_updates(Object(Plugin_Upgrader), Array(4))
Forum: Plugins
In reply to: [LiteSpeed Cache] Drastic reduction of performanceWhen I purge UCSS the pagespeed performance instantly improves. As soon as UCSS cronjob is executed, the pagespeed performance drops to 74-77%.
I tried to sett UCSS generation to OFF , but it appears that it is set to ON by the Guest mode.
Question: how do I disable UCSS generation is the Guest mode???
Forum: Plugins
In reply to: [LiteSpeed Cache] Dectivation problemWhat changes to wp-config.php do I need to make to DEACTIVATE the LSC plugin? Setting WP_CACHE constant to false? Deleting this constant?
Forum: Plugins
In reply to: [LiteSpeed Cache] Drastic reduction of performanceI deleted LSC plugin so maybe this is why you cannot see the report. Simply Static plugin is dormant and works only during the specific request to generate a zip archive containing static version of the website. For the duration of this specific request all caches need to be disabled.
This is one of the reasons why I need a clear documentation how to deactivate, disable, delete and reinstall LSC plugin. At the moment the LSC plugin is a menace because it does not deactivate cleanly.
The content of the above mentioned Simply-Static-generated zip archive needs to be put in a separate folder to create a static website copy online. See for example https://alt.thiaoouba.com – it is a static backup of the WP website https://thiaoouba.com.
Forum: Plugins
In reply to: [LiteSpeed Cache] Dectivation problemwp-config.php is read only, which is a recommended security setting.
Yes, I see warning in the Admin when I try to deactivate, delete or reinstall your plugin.
I think plugins should not be allowed to modify wp-config.php for security reason. And if changes are required – they should be clearly documented. What changes LSC tries to do to system files when it is installed, activated, deactivated and deleted?
Forum: Plugins
In reply to: [LiteSpeed Cache] Drastic reduction of performanceI do not have any cleanup plugins. At this site I use Oxygen page builder that has its own css cache that I can manually refresh. I shared the report so you can see plugins that I use.