Hi @hiddenpearls,
In order for us to properly investigate the issue and understand if there is a conflict, we will need to recreate the issue on our end first.
Could you please provide us with the exact steps we should follow in order for the issue to appear on a test site?
Hello @hiddenpearls,
Could you please update the plugin to 7.1.5 version and update us here if the issue is resolved.
In case is not – please check my colleague reply above and provide us with more details on the matter.
Thank you for your cooperation in advance!
Best Regards,
Elena
Hello @hiddenpearls,
Since we haven’t heard back from you in the past couple of days we will be marking the topic as Resolved.
You will still be able to post a reply in case further assistance is needed.
Best Regards,
Gergana Petrova
Thread Starter
Adnan
(@hiddenpearls)
Accept my apologies for the delay in response @delyandelov
Here are the steps:
1. Deactivate “SiteGround Optimizer”
2. Install “Analytify” from “https://ww.wp.xz.cn/plugins/wp-analytify/advanced/”
3. Install and Activate “Transients Manager”
4. You will see transients are stored and display in “transients manager”
5. Activate “SiteGround Optimizer” again and browse some pages on the site.
6. Go to Analytify Dashboard, and now go to “transients manager”
7. Are you seeing a different in number of “”transients manager” data?
8. Delete “transients manager” data and browser pages again.
9. You will see no transient are stored anymore.
10. Disable your plugin and browse pages again, you will see data back again in “transients manager”
Ok?
Hi,
Thank you for the update.
We have installed Analytify alongside with Transients plugin and connected Analytify with Google Analytics. Then, we followed the provided steps, however identical transients were generated. We have performed extensive tests after flushing all possible caches, deactivating SiteGround Optimizer and so on.
Please assure that SiteGround Optimizer is the latest version and test again. If the issue still persists, please check if there is a more specific pattern of actions that we can follow for reproducing the issue on our end and update this thread with that information.
Best Regards,
Dimitar Petrov
@hiddenpearls ,
We have not heard back from you and we will be closing the thread marking it as resolved. You can contact us again in case the issue continues and additional recreation steps can be followed up.
Best regards,
Georgi
