Hi,
Thank you for reaching out to us.
We have checked on our end and did not find the issue you mentioned. It might be occurring on your end due to a conflict with another plugin. Kindly check once, and if the issue still persists, please share a short video showing the steps you are taking and the issue occurring so we can check further.
Dear Akshay, the issue is simple if update the plugin to latest version the plugin section go in infinite loop, to go back I need to restore your plugin before the version 1.0.98, I have received an email from the hosting to a lot of resource used from your plugin when the latest version is active.
Please investigare more and fix the issue asap.
Thanks in advance
Hi,
Please enable the debug.log and check the exact error you are getting? Kindly share that error with us so we can check further.
this error appear in the debug log, other I can’t save any settings in the amp settings.
[27-May-2025 09:45:22 UTC] PHP Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /public_html/wp-content/plugins/accelerated-mobile-pages/includes/options/redux-core/framework.php on line 2862
Also I have received an email from the host the issue is caused from the mysq with slow queries please see down.
=== TOP 10 of 73 (total) Slow Queries for the past 4 hours =======================================================
1. Executed 1m 16s ago for 1.28588 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:15 Query_time: 1.285880 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151253.css’, ‘ampforwp-tree-shaking/_transient_post-151253-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
2. Executed 1m 16s ago for 1.255484 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:15 Query_time: 1.255484 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151258.css’, ‘ampforwp-tree-shaking/_transient_post-151258-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
3. Executed 1m 16s ago for 1.248268 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:15 Query_time: 1.248268 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000001 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151258.css’, ‘ampforwp-tree-shaking/_transient_post-151258-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
4. Executed 1m 17s ago for 1.238462 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:14 Query_time: 1.238462 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151250.css’, ‘ampforwp-tree-shaking/_transient_post-151250-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
5. Executed 1m 29s ago for 1.198736 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:02 Query_time: 1.198736 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151185.css’, ‘ampforwp-tree-shaking/_transient_post-151185-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
6. Executed 1m 29s ago for 1.196901 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:02 Query_time: 1.196901 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000003 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151185.css’, ‘ampforwp-tree-shaking/_transient_post-151185-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
7. Executed 1m 14s ago for 1.188112 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:17 Query_time: 1.188112 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-152307.css’, ‘ampforwp-tree-shaking/_transient_post-152307-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
8. Executed 1m 13s ago for 1.186654 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:18 Query_time: 1.186654 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-152713.css’, ‘ampforwp-tree-shaking/_transient_post-152713-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
9. Executed 1m 15s ago for 1.186536 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:16 Query_time: 1.186536 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000002 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151258.css’, ‘ampforwp-tree-shaking/_transient_post-151258-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
——————————————————————————————————————-
10. Executed 1m 24s ago for 1.184583 sec on Database –> b3qbq34b3rb3
Date: 2025-05-26 10:00:07 Query_time: 1.184583 Rows_examined: 246200: Rows_sent 0 Lock_time: 0.000001 Query_chars: 229
SELECT pm.meta_id, pm.post_id FROM d7b1_postmeta AS pm WHERE pm.meta_value IN ( ‘ampforwp-tree-shaking/_transient_post-151204.css’, ‘ampforwp-tree-shaking/_transient_post-151204-scaled.css’ ) AND pm.meta_key=’_wp_attached_file’;
Hi, kindly confirm if those warnings started appearing on your end after updating to version 1.0.98? Also, what version are you currently using?
This error appear in all version after the version 1.0.98 now I have active the version 1.1.5 but if I’ll try to active any plugin or deactivate the server load spike to over 100% of usage and the server return an error.
Please resolve the issue or I need to stop use your plugin.
Hi,
We have raised a GitHub ticket regarding this concern for review and will update you soon. You can track the progress here.
Hi,
Hope you are doing well. We have released an update version 1.1.6 in which this concern has been addressed. Kindly update the plugin to the latest version, clear the cache and give it a try.
ok thank you, I’ll try the new version asap!
