Pavel Dosev
Forum Replies Created
-
Thank you, @hecttech08,
I was able to recreate the issue on my end. I passed the information to our developers for further review, and once we have an update from them, we will update the thread to let you know.
Hello @hecttech08,
I am afraid that I cannot recreate the error on my end, and the parse from the debug log isn’t sufficient.
If your website is hosted with Siteground, could you please provide us with its URL so that we can check and recreate the problem on a staging site and see what is causing it?
Hello @danielandsebastian,
I tried recreating the issue on a blank WordPress on my end, but I could not.
Could you please let us know which page you are testing with the AMP tool to get the error and if we can re-activate the plugin for your website or create a staging copy of the site to recreate the error?
Hello Annette,
Once the transfer is initiated, you can point out the domain to the new host.
However, we suggest doing this only after the transfer completes successfully and double-checking that the transferred website is working correctly.
As discussed in the topic below, the error comes from a rate limit imposed by the service we use to add this tool in SG-optimizer. You can see more information in it as well as a workaround for the error you are encountering:
Hello @xizzeeweb
The speed test feature in our plugin is integrated via a third-party service provided by Google. We use it to provide direct access from the plugin to the Google page insight tool.
Unfortunately, they impose restrictions on their end, which includes a rate limit that will restrict usage of the speed test when it is experiencing a higher load. Unfortunately, we have no control over this limit.
What we can recommend you is to try using it later or use the page insight directly from their website, which isn’t restricted in the same way and generates the same report:
Hi @alexg9,
Since we haven’t heard back from you regarding the posted topic, we will mark it as resolved on our end.
Nevertheless, if you have further questions, feel free to post another topic.
Hello @paddy-landau,
Thank you for the suggestion. Indeed the file is recreated on each update, and it must be manually removed through this option after each update.
I will pass your request to our developers for further consideration, and they will eventually implement it in one of the future releases of the plugin.
You are welcome, @mjoly2000.
We will mark the case as resolved and close it. However, if you encounter the same issue after applying the suggestion mentioned earlier, please update the thread and let us know.
Forum: Plugins
In reply to: [Security Optimizer - The All-In-One Protection Plugin] Only for Siteground?Hello @markussss,
I confirm what @boluda already said. The plugin can be used on any hosting, not only on sites hosted on Siteground servers.
P.S. Thank you @boluda, for the quick reaction.
It wouldn’t, as you are just declaring the path to your wp-content folder, which you already set using the symlink.
If by any chance there are any problems with the website after adding this line. You just need to delete this line from the wp-config.php, which will revert the path setting.
Hello @rwtwebdev,
I checked the site, and I see that the wp-content location is changed through a symlink, which is causing the problem.
You can get around it by declaring the wp-content folder location in the wp-config.php.
https://codex.wordpress.org/Determining_Plugin_and_Content_Directories
You can do this by adding the line below to your wp-config.php:
define ('WP_CONTENT_DIR', '/home/customer/www/static.renewed-edge.com/public_html');Hello @ilovewpcom,
I was able to recreate and resolve the issue by modifying the following line in File_Cacher.php line 780:
File_Cacher.php:
From:
'logged_in_cookie' => 'wordpress_logged_in_' . COOKIEHASH,to this:
'logged_in_cookie' => 'wordpress_logged_in_' . 'COOKIEHASH',The warning is no longer showing, and I can successfully save the settings in your Social widget plugin.
I also passed the information to our developers so that they can evaluate it and address it in a future update of the plugin.
Hello @axis9313,
I was able only to recreate the cookies are blocked message on my end. I cannot find the thrive lightbox and its location on your site to check it.
Still, I cleared the website’s cache, and after that, I excluded the Thrive lightbox from our cache and the custom login page.
The website is loading correctly, and the cookies error is no longer showing. I left all the cache options turned on. Please let us know if the problem reoccurs.
Hello @tvtronics,
I checked the site, but I could not recreate the issue you are describing.
I added 2 items to my cart, refreshed the page, and removed them. The bag counter showed 0, and it didn’t show 2 items initially. I also tried it without refreshing the page after adding items, and the problem did not occur as well.
Please see if your browser’s cache doesn’t cause this as I tested it both in Firefox and Chrome, and on both, I couldn’t replicate the problem you described.