Ah, you’re right — I totally missed that it’s on the first page. I was looking under the “Layout” tab like in the Post Loop block, so I didn’t spot it.

Thanks so much for the clarification and the screenshot!

Hi Calin,

Thanks for the quick response — I appreciate you escalating this to the dev team.

In some situations, I actually prefer the current behavior where child categories are displayed. So when you address the bug, it would be great if you could consider adding a third option in the dropdown for:

Display category

• Siblings
• Parents
• Child ✅ (suggested)

That way, we can explicitly choose the desired behavior depending on the context.

Thanks again for your support!

Best regards,
David

Hi Calin,

thanks for looking into this. A few additional details from our end:

1. We’ve used about ten different plugins that triggered the same “\_load\_textdomain\_just\_in\_time was called too early” notice, and they’ve all released fixes since WP 6.7 (November 12, 2024). The only one still spamming our logs is td-cloud-library.

2. To prove it’s definitely td-cloud-library, we spun up a fresh install with only the Newspaper theme plus tagDiv Composer and td-cloud-library active. With WP\_DEBUG (and/or WP\_DEBUG\_LOG) enabled, the notice appears—and disabling td-cloud-library alone removes it. Steps to reproduce:

* Install Newspaper theme + tagDiv Composer + tagDiv Cloud Library
* Add to wp-config.php:

`
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_DISPLAY’, true);
define(‘WP_DEBUG_LOG’, true);
`
* Visit any page and watch the notice flood the debug log.

3. We hunted down why that notice won’t go away under WP 6.7+. Here’s what we tried:

* Searched every PHP file in td-cloud-library for load\_plugin\_textdomain(…) calls—none exist.
* Made a small must-use plugin that removes WP’s JIT filters on “plugins\_loaded” and force-loads the text domain on init. But it still fails because WP 6.7+ attaches _load_textdomain_just_in_time so early that any __(…, 'td-cloud-library') call in the plugin’s global scope immediately triggers the notice—before our MU-plugin runs.
* In other words, as soon as the first translation function fires (e.g. __('…', 'td-cloud-library')), WP already tried and threw the warning.

What needs to happen: All translation function calls (__(), _e(), esc_html__(), etc.) in td-cloud-library must be moved out of the global scope so they don’t run before load_plugin_textdomain('td-cloud-library', …) fires on or after init. Until every translation call is wrapped in a callback (or otherwise deferred until after the domain is registered), that notice will keep spamming logs.

Hope this helps pinpoint the fix. Cheers!

Hi Calin,

Thanks for the clarification!

I’m using a Cloud Header but with the standard mobile menu, and your suggested CSS for the expanded subcategories works perfectly in this setup.

Also, your explanation regarding the social icons makes sense. Since I want to keep them on desktop but remove them on mobile, the CSS approach is exactly what I needed.

Appreciate the quick and helpful support!

Hi Calin,

Thanks for your reply!

Regarding the social icons in the mobile menu, you mentioned removing them via theme panel > social networks. Could you please clarify which exact setting disables them from showing in the mobile menu only? I would like to keep them on desktop (footer) but remove them from mobile menu.

As for the expanded subcategories, you mentioned it “should be working now” — does that mean there is now an option in the admin panel or menu settings to have subcategories expanded by default on mobile? Or is there a specific class, script modification, or menu setup required to enable that behavior?

Would appreciate a bit more detail on both points so I can implement the changes correctly.

Thanks again!
David

Hi,

If you’re using Yoast SEO, you can easily prevent the tdb_templates pages from being indexed by Google. Here’s how:

Go to Yoast SEO > Settings in your WordPress dashboard.

Under Content Types, look for Cloud Templates.

Toggle “Show Cloud templates in search results” to Off.

This will add a noindex directive to those pages and keep them out of Google’s index.

If you’re using a different SEO plugin, look for similar settings to disable indexing of custom post types. If you’re not using any SEO plugin, you can manually disallow them in your robots.txt or add a noindex meta tag via a custom function.

Hope this helps!

Hi,

The code in the current version seems to be slightly different from the one provided in the screenshort earlier in this tread. It seems like that just changing the “>” direction won’t do the trick with the current theme version. Is there anything else that needs to be changed? This is the current code (before changing the direction of the “>”)

// Update TO version 8.6 - add social networks.
// @since 14.12.2017
if ( empty($social_drag_and_drop) && ( version_compare($td_db_version, '8.6', '<') || TD_DEPLOY_MODE == 'dev' ) ) {
td_options::update_array('td_social_drag_and_drop', array (
'facebook' => true,
'twitter' => true,
'pinterest' => true,
'whatsapp' => true,
'linkedin' => '',
'reddit' => '',
'mail' => '',
'print' => '',
'tumblr' => '',
'telegram' => '',
'stumbleupon' => '',
'vk' => '',
'digg' => '',
'line' => '',
'viber' => '',
'naver' => '',
'flipboard' => '',
'kakao' => '',
'gettr' => '',
'koo' => '',
'copy_url' => ''
));

$update_social_drag_and_drop_option = true;
}

Thanks!

I can confirm that this message stems from “td-cloud-library” and is flooding the debug logs (if wp debug is enabled) when updating to the latest WordPress and Newspaper Version.

I’ve actually been looking for exactly this! It would make things so much easier to hook into the featured image caption without touching theme files. Really hope this gets added soon.

3. Is there a way to hide the sticky row after a certain scoll?
4. What classes / data attributes are used to make the row sticky? Is there a specific HTML structure or wrapper required for an element to be recognized as sticky? Are there JavaScript functions by the theme to manage sticky elements? Are there any action or filter hooks?

Also on mobile it seems to be “smart snap” and not “always”.

So my remaining questions are:

1. is there a way to change it from “smart snap” to “always” for mobile?
2. is there any way to make it just sticky on mobile?

Oh I see its sticky for mobile as well it was just covered by the mobile sticky header. But is there any way to make it just sticky on mobile? it looks like if I remove the checkmark for desktop its removed for mobile as well.

Hi,

Thanks for the tip, single image is working. Nevertheless, can you please add it to your bug / enhancement list, as the single background image offers other options that I miss with single image?

Thank you very much.

Ah, that’s where it’s hiding! Thank you very much!

Hi,
Thank you for your response. The settings were indeed different which I now changed but unfortunately, it’s not the cause of the issue. Any other ideas?
Thanks!

Hello Anamaria,

Thank you for your response. Unfortunately your Imgur link is broken. Also, are u sure that the options you provide via theme panel activate the default WordPress lazy load? If this is the case, why do I not see loading=”lazy” added to images added via theme builder in source code?

Thanks!

Hi Calin,

Does this mean this mobile menu setting in the theme needs always be active, no matter if the menu/ search is placed via a cloud template?

Thanks!

Hi Bettina,

Indeed, I did remove unused CSS a couple of years ago. Not with a cache plugin but with your inbuilt theme functionallity. However, this functionallity seems not actively used anymore. But to be sure I just run the “Critical CSS Analyser” and then clicked “Remove Generated CSS”. But it did not change anything, the menu and the search icon are both still not clickable. Also the hamburger menu has a menu selected like in your screenshot. Any other idea what could cause this issue?

Thanks!

Hi @Anamaria,

Thank you for your response. Where exactly is this Custom CSS code set? I see the class but I can nowhere track down from where it is defined. The custom css section in tagdive composer for this element is empty, also the themes custom css section and the wordpress default site edit custom css section, all empty.

Looking forward to your answer.
Thank you!

To be honest, I’m also a bit irritated about it. Ads everywhere, even in the composer. Luckily I only maintain my own sites but for people who use the theme for their clients the update must have been a shock.

Hi Calin,

Actually, the page was created when WPBakery was a built-in part of Newspaper and the only way to design pages. It’s a pity that this is no longer supported, as it means extra work. But yes, if I disable WPBakery and rebuild the pages with TagDiv Composer, it seems to solve the problem.

I add the post ID filter in exactly the same way. However, it doesn’t seem to work for the Single Post template, no matter which Post ID I try. Any idea what this could be due to?

Thanks!

Hi,

Now I understand that. In that case I have to select “Single – Current Category”. Didn’t notice that. Thanks!

Hello Bettina,

Thank you for the infos. The deactivation of the Loading Image Effects fixes the load issue but I would like to keep that for images below the fold. So is there any way to disable this effect just for the featured image? Any line of code that coud stop it just for the featured image?

Regarding Bg Featured Image vs Single Post Featured Image, I need caption + custom image size in one. Unfortunately this option is currently not given. Please add it to the wish list. Thanks!

For those who are also affected by the problem, the developers know about the problem and are working on a solution.

The problem occurs when the images have a caption.

Therefore, there are currently two ways around the problem:

1. omit captions
or
2. use the following CSS :

.single .wp-caption.alignright { width: 350px!important; margin-right: -100px!important; } .single .wp-caption.alignleft { width: 350px!important; margin-left: -100px!important; }

You can of course adjust the width and margin accordingly. The best way to do this is to set Custom CSS in the Theme Panel and adjust the values depending on the screen size.

For those who are also affected by the problem, the developers are aware of the issue and are working on a solution.

As a temporary fix, it helps to go back to version 11.2, because this bug only occurs from 11.3 and higher