TD composer is sending so many unneeded internal queries to the site that even if having a powerful cloud server, it blocks the access and get tons of 500 and 429 errors
Hi,
Can you provide some more details about this situation?
Indeed, our theme is making a request for each block and element used on a page/template to get the right results and configuration, but there should not be such problems.
Thank you!
I’m experiencing severe performance and stability issues with the Newspaper theme and the TagDiv Composer. Even with proper caching enabled — Redis Object Cache plus WP Super Cache — the server load rises very quickly after only a few editing or viewing actions.
My site runs on an Infomaniak CloudServer (4 vCPU, 12 GB RAM), and yet PHP memory usage spikes drastically whenever multiple posts are opened or edited, or just visited by users, which results in 503 and 429 errors.
Additionally, I’ve observed that multiple duplicated MySQL queries are being sent to the database for a single page load, which suggests there’s room for optimization in the theme’s database handling.
I’ve also seen several other users report the same issue with the Newspaper theme after their sites have grown large over time.
Could you please clarify what exact details or logs you need from me to investigate this issue properly?
Once I know what information is required, I can provide it precisely to help you diagnose and resolve the problem.
Thank you,
I have even activade the cache of the Flex blocks to 1 day and 1 week… but still get the same problems
Hello,
To reduce the queries, you can check the fallow.
Check if you are using ajax pagination, mega menu, and many blocks (the theme is making a query for each block in parts, and if you are using mega menu, each element as mega menu makes queries, also ajax pagination makes queries to the database). Also, make sure that you use lazyload for images.
Other type of settings that can reduce the numbers of queries: use a good cache plugin WP Rocket, use object cache (redis), and use flex block cache – https://forum.tagdiv.com/use-flex-blocks-cache-option/ (with will reduce the number of request instead of a request for each page load for each flex block, this request will be only after 5-10 minutes for that flex block, it depends on the time set)
In addition, it’s a good idea to identify what’s consuming your server resources. Tools like Query Monitor and Code Profiler can help you pinpoint high CPU or resource usage caused by plugins, themes, or database queries.
Thank you!
Dear TagDiv Support,
I am writing to report several critical issues affecting the Newspaper theme and its bundled plugin td-cloud-library, which are causing instability and performance problems on my website (europeantimes.news).
After thorough debugging, I’ve identified key areas that require immediate attention from your development team.
🔧 1. Translation Loading Triggered Too Early
Error Message:
“Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ‘td-cloud-library’ domain was triggered too early.”
Location:
tdb_config::on_tdc_loaded() in /wp-content/plugins/td-cloud-library/includes/tdb_config.php
Issue:
The theme loads translation strings before WordPress is fully initialized. According to WordPress Codex , translations should be loaded at the init action or later.
Currently, this causes repeated “doing it wrong” notices and impacts system stability under high load.
Request:
Please ensure all text domains are loaded properly via the init hook:
php
1
2
3
add_action(‘init’, function() {
load_plugin_textdomain(‘td-cloud-library’, false, dirname(plugin_basename(__FILE__)) . ‘/languages’);
});
🔧 2. Deprecated Constructor in Mobile_Detect Class
File:
/wp-content/plugins/td-cloud-library/includes/Mobile_Detect.php
Issue:
The constructor uses outdated syntax that triggers deprecation warnings in modern PHP environments.
This affects compatibility and indicates code maintenance is needed.
Request:
Update the constructor to follow current PHP standards:
php
1
function __construct(?string $userAgent = null, ?array $httpHeaders = null)
🔧 3. Excessive Database Queries Due to Empty Email Lookups
Observed Behavior:
Repeated queries like:
sql
1
SELECT * FROM wp_users WHERE user_email = ‘d41d8cd98f00b204e9800998ecf8427e’
(This is the MD5 hash of an empty string.)
Cause:
Avatar functions call get_user_by(’email’) without validating that the email exists.
Impact:
Unnecessary database load, especially under automation or bot traffic.
Request:
Add validation before querying:
php
1
2
3
if ( ! empty($email) && is_email($email) ) {
$user = get_user_by(’email’, $email);
}
🔧 4. Aggressive Hook Execution Before Initialization
In tdb_config.php, translatable strings are used inside on_tdc_loaded(), which fires before init. This forces premature loading of language files and violates WordPress best practices.
Example Line:
tdb_config::on_tdc_loaded() → calls __() too early
Recommended Fix:
Defer any logic involving translation functions until after the init action.
✅ Environment Summary
Theme: Newspaper (latest version)
Plugin: td-cloud-library (bundled)
WordPress: 6.8.2
Caching: Redis Object Cache + Hummingbird
Traffic Type: High-volume, automated content publishing
🛠 Requested Actions
Please:
Acknowledge these issues
Confirm if fixes are planned in an upcoming release
Provide guidance on running the theme reliably at scale
These are not minor notices — they directly impact performance, scalability, and long-term compatibility with WordPress core.
Thank you for your time and support. I look forward to your response.
Best regards,
Hi,
Please create a full backup of your website and update the theme to the latest version (12.7.2). This update should resolve some of the reported issues. Our developers will review the remaining problems and determine the appropriate solutions.
https://forum.tagdiv.com/how-to-update-the-theme-2/
Thank you!
