Search Results for 'cloud library'

Hi, after updating to the latest version of Newspaper, my site started having issues where some articles or sections are not displaying properly. The layout appears broken — the featured image shows as a large black “?” placeholder, the text size is incorrect, images appear smaller than they should, and the sidebar is misaligned (sometimes centered). Overall, the page looks completely broken. This only happens on certain articles.

I rolled back to the previous Newspaper version and everything seems to work fine again.

Do you have any idea what might be causing this?

Also, when I first installed the latest version, the plugins didn’t install correctly (tagDiv Composer and tagDiv Cloud Library). That’s the first time this has happened. After the failed install, I updated them manually from the Plugins section and they appear to be working fine.

One more thing: when I view the site while logged in, everything looks perfect. The issue only appears for regular visitors (logged-out users).

Hello,

I would like to integrate a WooCommerce shop into my website, which is running on Newspaper 12 with WP Bakery Pag Builder. I would like to use a shop template for the woocommerce shop. What is the best way to do this?

Can I use a template from the TagDiv Cloud Library, or can I use any shop template from the WooCommerce Marketplace? Or would that conflict with the existing Newspaper/WP Bakery installation?

Also, which tool would I use to edit and customize the shop templatesa after installation?

Thank you very much and best regards

Sönke

Hello Support,

I am contacting you because I am running into what looks like a compatibility or translation-handling issue between WPML and the Newspaper theme by tagDiv.

My setup is:

WordPress

Newspaper theme (Today News PRO demo/import)

tagDiv Composer / Cloud Library

WPML

Secondary language: German (/de)

Default language: English

What I am trying to achieve is straightforward:
I want to have an English footer on the English site and a German footer on the German site. The footer content was created with the tagDiv Composer as a footer template / Cloud Template.

The issue is that I cannot create or manage the translation workflow for these Cloud Templates correctly, and as a result the German footer keeps showing English text for posts.

Here is what I observed:

In WPML → Settings → Post Types Translation, I set the Cloud Template post type to:
“Translatable – use translation if available or fallback to default language”

However, in the Cloud Templates area in the WordPress backend, I do not see the WPML translation controls I would expect, such as the language columns or the “+” translation icon for German.

Because of that, I cannot create a proper German translation of the footer template through WPML.

I also checked WPML String Translation and Translation Dashboard / Other texts (Strings), but the footer text does not appear there.

The footer text is not coming from a normal theme option or a menu string. It is content inside a tagDiv footer block created in the tagDiv Composer.

I tried creating a copied/duplicated footer and also a copied single post template as a workaround, but that led to additional problems:

changes in the copied version affected the English version as well, or vice versa

at some points, post formatting broke for both languages

I had to manually restore several pages/templates in tagDiv Composer

some templates disappeared or behaved inconsistently in the backend, even though the frontend still partially worked

Another related symptom:
In English posts, I can select the template “Single Template – Today News PRO”.
In German posts, I only see “Default”, not the same Single Template option.
This makes me think WPML may not be recognizing or linking the tagDiv Cloud Templates correctly for the secondary language.

At one point, setting Cloud Templates to a stricter translation mode caused header/footer/template behavior to break more severely, so I reverted to the fallback setting above.

At the moment, the frontend is mostly restored, but one core problem remains:
the German version — all posts — of the site still displays the English footer text, and I have no reliable WPML-based way to translate the footer Cloud Template.

From my perspective, the main issue is:
WPML seems not to expose the translation UI for tagDiv Cloud Templates in this setup, and the footer content is also not available through String Translation.

Could you please help me with the following:

Is this a known compatibility issue with Newspaper/tagDiv Cloud Templates?

Should WPML show translation icons / language columns for these Cloud Templates in the backend?

Is there a recommended WPML workflow for translating tagDiv footer templates created with tagDiv Composer?

Why would the English Single Template be selectable in English posts, but only “Default” appear in German posts?

Is there any additional configuration, compatibility plugin, or troubleshooting step required so WPML recognizes these Cloud Templates properly?

I can provide screenshots of:

WPML Post Type Translation settings, the Cloud Templates backend screen where no translation icons appear and
the footer output on the German frontend

See here:

https://ibb.co/M5p25kGH
https://ibb.co/s9MCdJFY
https://ibb.co/tTF1dXHN
https://ibb.co/dJsgKd69
https://ibb.co/hxGqZZk0

Thank you in advance for your help.

Best regards,
Marcus

PS here’s the response by WPML support:

Hello there,

Thanks

Hi, I’ve been seeing this error in my log for a while now: PHP Warning: Array to string conversion in /home/ilneraz1/public_html/wp-content/plugins/td-cloud-library/includes/tdb_functions.php on line 456

What could it be? How can I fix it?

We are using Newspaper 12.7.5 with td-cloud-library 3.9.4 and WPML. We need a native language switcher element in the header Cloud Template builder, but tdb_header_language does not exist in our shortcodes/header/ directory and does not appear in the editor element list.
Available header shortcodes in our installation: tdb_header_categories, tdb_header_date, tdb_header_logo, tdb_header_mega_menu, tdb_header_menu, tdb_header_menu_favorites, tdb_header_search, tdb_header_user, tdb_header_weather.
Questions:

Is tdb_header_language available in a newer version of Newspaper or td-cloud-library?
Is there a dedicated WPML + tagDiv integration plugin that adds this element?
Is there an official recommended approach to integrate WPML language switcher natively in the header Cloud Template builder?

Tagdiv cloud library plugin suddenly deactivated itself when restarting mariadb or mariadb crashed. This has happened several times recently. Can this plugin remain active even if mariadb restarts or the server restarts?

Hello tagDiv Support,

I need help with a serious issue that started after updating Newspaper. I have spent hours troubleshooting this and I want to give you a clear, detailed summary so you can understand exactly what is happening.

My site:
MarryCaribbean.com

Theme:
Newspaper

Problem summary:
After the update, my single post pages began crashing and showing the WordPress critical error message. At the same time, several layout behaviors changed unexpectedly, including my post hero styling and category/archive display.

Here is what I observed and tested.

1. Single posts started failing after the Newspaper update

Before the update, my single posts were working normally.

After the update:

* Single post pages began showing “There has been a critical error on this website.”
* This was happening under Newspaper, while the site worked under a default WordPress theme.
* Category pages and other parts of the site were not failing in the same way at first, which made this look specific to the Newspaper single post rendering path.

2. Debugging pointed to td-composer

I enabled WordPress debug logging and found fatal errors pointing to td-composer, specifically memory exhaustion in this path:

/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php

I also saw repeated notices for translation loading from other plugins, but those did not appear to be the main cause of the front-end post failure.

The key fatal I saw was memory exhaustion inside td-composer.

3. Default WordPress theme worked

To isolate the issue, I temporarily switched to a default WordPress theme.

Result:

* The single posts loaded
* The content itself was fine
* This suggested the problem was not with WordPress core or the post content itself, but with Newspaper/tagDiv rendering

4. Backup restore did not solve the issue

I restored a backup using UpdraftPlus, including:

Database
Plugins
Themes

However, this did not restore the previous Newspaper behavior on its own. The single post issue remained. What actually made individual posts load again was manually opening them and explicitly selecting a post template such as FROM PANEL or DEFAULT and then updating the post.

5. tagDiv Composer / Cloud Library behavior was inconsistent

After the restore:

* tagDiv Composer and tagDiv Cloud Library had to be reactivated
* Header/footer/custom appearance behavior changed depending on whether these plugins were active
* At one stage, single posts worked with Composer off, but the custom header/footer/design was degraded
* With Composer on, other design pieces came back, but single post behavior was still unstable or altered

6. The biggest discovery: post template behavior changed

This appears to be the most important clue.

I found that many posts would work again only after I manually opened the post and explicitly selected a post template, for example:

* FROM PANEL
or
* DEFAULT

If I manually selected one of those and updated the post, the post would usually load again.

This strongly suggests the update changed or broke how post template settings were being inherited or interpreted.

What is especially concerning is that this appears to affect many posts, not just one or two.

7. “From Panel” is not consistently broken, but behavior changed

I originally thought FROM PANEL itself was broken, but after more testing I found:

* Some posts work on FROM PANEL
* Some posts work on DEFAULT
* Some posts needed to be manually touched and saved before they would work at all

So the issue does not seem to be as simple as “FROM PANEL is broken.”
It feels more like the update disrupted how template/layout assignments are being inherited or loaded on a per-post basis.

8. My hero/header layout on single posts changed

Even after I got the posts loading again, the visual layout is not what it was before.

Before:

* My post hero had a stronger designed look
* The title, author, tags, and hero image styling appeared more integrated/overlaid
* There was more of a styled hero presentation

Now:

* The posts may load, but the hero/header presentation is simplified or degraded
* The featured image sits more plainly
* The old styled hero treatment appears to be missing

So even when the post works, the layout is not the same as before the update.

9. Article Display View options appear to be missing

In the Theme Panel, under areas where I remember having many layout/style choices, the “Article Display View” area appears blank or missing its usual options.

I specifically remember having many appearance/layout choices there before. Now those options do not appear to load properly.

This makes me think some template/module UI in Newspaper is no longer loading correctly after the update.

10. Category/archive behavior also changed

After the update:

* My category/archive sections changed layout
* I had 3 items per row before, but now it is showing 2
* I also started seeing little comment count boxes with “0”, which I never wanted and did not have before

I checked Block Settings and global module meta settings. Show Comment Count appears to be off globally, but the archive/category output is still not matching what I had before.

This makes it seem like the archive/module style or template behavior changed during the update as well.

11. Cloud Templates screen appears empty

In Cloud Templates, I currently do not see cloud templates assigned in the way I expected. For example, the Single Templates area appears empty.

That is confusing because I know my site had a more customized appearance before, and the current theme behavior no longer matches it.

12. Main concern

My biggest concern is that this update appears to have:

* broken or altered post template inheritance
* changed single post rendering behavior
* removed or failed to load layout options I previously had
* changed archive/category display unexpectedly

On a larger site, this kind of behavior is extremely disruptive because it can force manual repair of many posts.

What I need from you:

1. Help identifying exactly what changed in Newspaper that caused single post template behavior to break or stop inheriting correctly
2. Help restoring the original post hero/layout behavior I had before the update
3. Help restoring the archive/category display so it matches the previous layout
4. Help understanding why the Article Display View choices appear missing/blank
5. Guidance on whether this is a known issue in the current version and whether there is a patch or recommended fix

I would appreciate a serious look at this, because this has taken a lot of time to troubleshoot and it clearly appears connected to the Newspaper/tagDiv update path rather than WordPress itself.

Thank you,
MarryCaribbean.com

Hello,

I’m using Block 4 from the “Add Element” section to display my blog posts.

My webpage layout is wider, but I can’t find any setting within the Block 4 options to adjust the block width so that it matches the earlier part of my page.

The earlier section of the page is built using Pre-designed Templates from the tagDiv Cloud Library, where there are options available to control the section width. However, I cannot see a similar width option for Block 4.

Could you advise if there is a way to adjust the width of Block 4 so it aligns with the rest of the page?

Thank you.

Hello,

I’m using one of the Pre-designed Templates from the tagDiv Cloud Library, specifically Section 3 – Office Nexus.

As you can see from the link provided below, the template includes placeholder images. When I replace the existing images with my own, I can’t get them to position the same way as the originals.

I made sure my replacement image has the same width and height as the original, however when it appears in the template it shows up noticeably smaller.

Could you confirm the exact width and height of the images used in the template, and if there is anything else I might be missing when replacing them?

It’s likely something simple that I’m overlooking.

I would appreciate any guidance.

Thank you.

Link To Template: cloud.tagdiv.com Section 3 – Office Nexus