Hi @mattkeys,
Thank you for reaching out!
The plugin sends only one request per day to the server to save data in the database. This process is lightweight and won’t consume significant resources, so there’s no need to worry.
Best regards
hi James, can you reread my original post and look at the screenshot I attached? I agree if this was happening once a day it wouldn’t be much of a problem but that’s not what is happening.
I’ve been able to identify the bug causing this issue.
/wp-content/plugins/cost-calculator-builder/includes/lib/admin-notifications-popup/classes/ApiNotifications.php Line #26.
if ( false === $transient_data || get_option('_transient_timeout_' . $transient_name ) < current_time( 'timestamp' ) ) {
This looks innocent enough but if you know how WordPress handles transients it explains why this bug is coming up.
By default transients are stored in the database like a WordPress option. And in that case this code will work totally fine.
However once you enable object caching (which many hosting providers do for performance reasons), transients are no longer stored in the database. They are stored in memory with memcache.
And it is in that situation that the code above will always execute, because the call to get_option('transient_timeout' . $transient_name ) < current_time( 'timestamp' ) will ALWAYS evaluate as TRUE because that option does not exist. It doesn’t exist because with object caching/memcache, the transient is in memory, not in the options table in the DB.
And because it is always true, on every single page load in the admin area, it will phone home to promo-dashboard.stylemixthemes.com. This is why our server is getting hammered with these calls.
The solution is easy. The transient API takes care of expiring transients on its own, you do not need to check it yourself in the code. So the line I referenced should just read:
if ( false === $transient_data ) {
I will manually apply this fix to our servers to resolve this issue until it can hopefully be patched in the next version of this plugin.
Hi @mattkeys,
Thank you for your reply, and the details of the information you provided.
I informed our development team about the issue, they will analyze the issue and address it accordingly.
For now, we suggest following our changelog for further information about the issue here – https://docs.stylemixthemes.com/cost-calculator-builder/changelog/release-notes
Best regards,
James
This thread is marked ‘resolved’ but this bug is still present in the latest version of this plugin. In addition to the area I reported earlier, the same bug is present on line #88 of calculator-builder/includes/lib/admin-notices/classes/STMDashboard.php
Hello @mattkeys ,
Thank you for following up.
At the moment, our development team is working on a major update for the plugin, which will significantly improve the performance of the calculators. However, this is not a quick task, as the plugin is being rebuilt almost from scratch, and we also need time for thorough testing to ensure everything works seamlessly. We understand how important it is for you to have this resolved quickly, which is why we’ve mobilized all our resources to focus on this update.
Once the work is complete, we’ll release a new update that should include the fix for your case, and we’ll notify you in the changelog. You can find the link to the changelog in James’ previous response for your reference. Thank you for your patience, and I’ll keep you updated on our progress!
Best regards,
Julia Ten
Stylemix Support Team
