Search Results for 'cloud library'

I just installed newsmag and i am having hard time customizing it. I imported the demo template but it looked nothing like the demo i imported. I have tried every possible trick i could think of but nothing. Now i read that there is something called tag div cloud library on the theme’s plugin section but i don’t seem to see it on mine. Please i need assistant. Thanks

Hi I am using tagDiv Cloud Library version 3.9.5 and I am still getting the Vulnerability message, can you please fix it.

The tagDiv Header Search element generates invalid ARIA markup in both desktop and mobile header instances.

The generated HTML is:

<div class=”tdb-drop-down-search”
aria-labelledby=”td-header-search-button”>

The W3C validator reports:

The aria-labelledby attribute must not be specified on any div element unless the element has an appropriate role.

The search itself works correctly. The issue is specifically the generated markup.

I confirmed the source in:

wp-content/plugins/td-cloud-library/shortcodes/header/tdb_header_search.php

The original PHP output was:

$buffy .= ‘<div class=”tdb-drop-down-search” aria-labelledby=”td-header-search-button”>’;

I changed it to:

$buffy .= ‘<div class=”tdb-drop-down-search” role=”search” aria-labelledby=”td-header-search-button”>’;

After clearing caches and revalidating, both validator errors disappeared. Desktop and mobile search continued to function normally.

This confirms that the issue is not caused by search placement, template layout, or custom CSS. It is caused by the Header Search element omitting an appropriate role from the .tdb-drop-down-search container.

Please update the plugin output to include:

role=”search”

on that container, or otherwise revise the ARIA structure so aria-labelledby is used on an element with a valid role.

The error appeared twice because the page contains separate desktop and mobile Header Search elements.

Hello,

I am getting repeated PHP warnings inside TagDiv Composer:

Warning: Undefined array key "location" in
/wp-content/plugins/td-cloud-library/includes/tdb_config.php
on line 63782

The warnings appear across the Composer interface and make it difficult to edit my templates. I am also unable to save changes in TagDiv Composer.

Could you please advise what could cause this and how to fix it? Could it be a compatibility issue between my PHP version, Newspaper theme, TagDiv Composer, and TagDiv Cloud Library?

I have attached a screenshot. Thank you for your help.

If the img doesn’t appear : https://ibb.co/vxyNVKS3

Hi tagDiv team,

I want to set my content width to 1200px (modern news-site layout: full-bleed bars, centered 1200px content column) on zzpnieuws.nl, running Newspaper 12.7.6 with a child theme.

In this forum, your staff has described the solution as follows:

– Simion C. (Sep 2025, topic “How to customize the page width”): “So for a page like your homepage, you must edit it with the composer, click on the rows and stretch them to 1200px, it takes very little time.”
– Calin (Aug 2025, topic “banner in my header”): “you can adjust the row width using tagDiv Composer […] the row to be stretched to 1200px instead of the default.”

However, this stretch control does not appear anywhere in my tagDiv Composer:

1. When I select a Row (both on a regular Composer page and in my header Cloud Template), hovering over the left/right edges of the row in the preview shows no drag handles and no resize cursor.
2. The Row settings panel (tabs General / Divider / Layout / Css) contains no stretch or row-width dropdown. The Layout tab only has column layout, alignment, order and “occupy remaining space”. The Css tab only has a manual pixel Width field.
3. Theme Panel → Template Settings has no global site/content width setting either.

My questions:

– Where exactly is the “stretch row to 1200px” control in Newspaper 12.7.6? Is it a drag interaction in the preview, a setting, or something that must be enabled first?
– Is this feature version-, license- or configuration-dependent?
– If it is genuinely unavailable in my setup: what is your recommended, update-safe way to achieve a 1200px content width site-wide (including the default single post and category templates) without breaking the responsive grid and thumbnail calculations?

Setup: Newspaper 12.7.6 (deploy mode: deploy), child theme (originally generated on Newspaper 9), tagDiv Composer + Cloud Library active, header built as a Cloud Template, LiteSpeed Cache, hosting at Cloud86.

Screenshots attached: (1) the Row settings panel showing the four tabs without a width option, (2) a selected row in the preview where no drag handles appear on the edges. See images here: https://postimg.cc/gallery/3xm1fCyimages

Thanks,
Marco — zzpnieuws.nl

Hi

Please whenever I activate theme and plugins on my site NaijaVibe.net, loads really slow and my site goes down 504.

tagDiv Cloud Library
tagDiv Composer
tagDiv Opt-In Builder

Please advise what I need to do to resolve this

Thanks

Hi,

I really like how Newsmag automatically changes the Hero/Big Grid section on mobile (see Screenshot). The first featured article stays large, while the next four articles are displayed in a clean two-column grid.

In Newspaper, the same section keeps the desktop layout and the smaller articles become horizontally scrollable instead.

Is there a built-in Big Grid, Flex Block, Cloud Library template, or responsive option that reproduces the same mobile layout as Newsmag?

Screenshot

Thank you!

Hello,

I run the Newspaper theme (version 12.7.6, registered) with tagDiv Composer on a WordPress site hosted at WP Engine. The homepage intermittently breaks: the hero/feature grid renders as gray bands with no background images and the layout collapses. It happens every several days, with no edit or publish that I can tie to it.

I have diagnosed this fairly precisely and want to share the evidence, because it points to the Composer template failing to compose rather than a caching or browser issue.

WHAT THE BROKEN VS HEALTHY HTML SHOWS

I captured the HTML of the same homepage URL (page ID 370) in both states.

Broken state (~59 KB):

body class is MISSING: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
4 td_block instances
6 style blocks, about 9.8 KB of inline CSS
0 background-image rules (which is why no hero imagery paints)

Healthy state (~899 KB):

body class INCLUDES: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
324 td_block instances
41 style blocks, about 53 KB of inline CSS
about 200 background-image rules

So in the broken state the tagDiv block-builder template for the page is not composing at all. The tdb-template / global-block-template-1 output and inline CSS never generate.

WHAT FIXES IT AND WHAT DOES NOT

Purging the host cache does NOT fix it. The broken render is served even on a forced cache miss and on hard refresh, so it is not stale cache.
Re-saving the homepage in tagDiv Composer (Save, with the green Header/Footer/Content Successfully Saved confirmations) DOES fix it immediately, every time. This is now reproduced twice.

So a fresh Composer composition produces the correct page, and something later causes the page to revert to the un-composed render.

PATTERN

It stays healthy for several days, then suddenly reverts to the broken render.
One stable stretch lasted about 9 days before recurring.
A re-save fixes it for another multi-day stretch.

ONE POSSIBLY RELATED DETAIL

When the broken version was being served, the host cache had bucketed a desktop request into the mobile/iphone cache group. I mention it only in case Composer mobile/desktop template variant handling is relevant to why an incomplete render gets produced.

QUESTIONS

Is there a known issue where the Composer block-builder template fails to compose on a page regeneration, producing output without the tdb-template / global-block-template-1 body classes and without the inline CSS?
Could a periodic Composer cloud-library sync, a theme/Composer background process, or a license re-check trigger a re-render that lands in this un-composed state?
Is there a setting or maintenance step that forces the template to always fully compose, so I do not have to manually re-save in Composer every few days?
Is there a current recommended compatible pairing of Newspaper theme version and tagDiv Composer plugin version I should confirm I am on?

I can provide both full HTML captures (healthy and broken) on request.

Site: https://alstonhomes.com

Hello,

I run the Newspaper theme (version 12.7.6, registered) with tagDiv Composer on a WordPress site hosted at WP Engine. The homepage intermittently breaks: the hero/feature grid renders as gray bands with no background images and the layout collapses. It happens every several days, with no edit or publish that I can tie to it.

I have diagnosed this fairly precisely and want to share the evidence, because it points to the Composer template failing to compose rather than a caching or browser issue.

WHAT THE BROKEN VS HEALTHY HTML SHOWS

I captured the HTML of the same homepage URL (page ID 370) in both states.

Broken state (~59 KB):

body class is MISSING: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
4 td_block instances
6 style blocks, about 9.8 KB of inline CSS
0 background-image rules (which is why no hero imagery paints)

Healthy state (~899 KB):

body class INCLUDES: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
324 td_block instances
41 style blocks, about 53 KB of inline CSS
about 200 background-image rules

So in the broken state the tagDiv block-builder template for the page is not composing at all. The tdb-template / global-block-template-1 output and inline CSS never generate.

WHAT FIXES IT AND WHAT DOES NOT

Purging the host cache does NOT fix it. The broken render is served even on a forced cache miss and on hard refresh, so it is not stale cache.
Re-saving the homepage in tagDiv Composer (Save, with the green Header/Footer/Content Successfully Saved confirmations) DOES fix it immediately, every time. This is now reproduced twice.

So a fresh Composer composition produces the correct page, and something later causes the page to revert to the un-composed render.

PATTERN

It stays healthy for several days, then suddenly reverts to the broken render.
One stable stretch lasted about 9 days before recurring.
A re-save fixes it for another multi-day stretch.

ONE POSSIBLY RELATED DETAIL

When the broken version was being served, the host cache had bucketed a desktop request into the mobile/iphone cache group. I mention it only in case Composer mobile/desktop template variant handling is relevant to why an incomplete render gets produced.

QUESTIONS

Is there a known issue where the Composer block-builder template fails to compose on a page regeneration, producing output without the tdb-template / global-block-template-1 body classes and without the inline CSS?
Could a periodic Composer cloud-library sync, a theme/Composer background process, or a license re-check trigger a re-render that lands in this un-composed state?
Is there a setting or maintenance step that forces the template to always fully compose, so I do not have to manually re-save in Composer every few days?
Is there a current recommended compatible pairing of Newspaper theme version and tagDiv Composer plugin version I should confirm I am on?

I can provide both full HTML captures (healthy and broken) on request.

I am trying to assign my staging site as the 2nd site for the license. There is no way to assign it because you say I have another staging site that is licensed. That is incorrect. The license applies to TravelMaine.com but the staging2.travelmaine.com was deleted a long time ago. Why are you making me buy another license for a new staging site? That does not seem fair to me. 

Also, my developer said the site is breaking on the staging site when they try to update because I need the two plugins (see message below). Why are they not included in the update? Is this happening because you will not allow me to use my license on a staging site? Please advise ASAP!

Hello Lisa,

Thank you for contacting our Help Desk.

We have completed testing of the theme update on the staging site.

The Newspaper parent theme was upgraded successfully, while the child theme remained in place as expected. However, after the update, we found an issue with two required companion plugins, td-composer and td-cloud-library. These plugins did not remain active properly after the upgrade, which caused problems with the theme functionality and page layout.

Because of this, we reverted the change after testing so the site would remain stable and continue working as expected.

At this point, the issue does not appear to be with the update process itself, but rather with the plugin versions that should match the updated theme version. The package provided seems to be missing the corresponding plugin files, or it does not include the correct versions needed for this release.

To proceed safely, we would need the complete theme package for this version, including the bundled plugin files, so we can install the matching versions and test the update again.

Please send over the full package if available, and we will be happy to continue from there.

Best Regards,

Kamen Kumanov
Technical Support Supervisor

Hi there,

I’ve been trying for awhile now to upgrade a site to 12.7.6 from 12.7.5 but each time it breaks the top portion of the site. After upgrading, I re-install and activate the tagDIV Composer and tagDIV Cloud Library as both installations are removed but the logo, nav menu, ad, weather widget and general formatting are removed. This is what it should look like:

This is what it looks like after updating the theme:

These are the theme plugins that are installed and activated:

Thoughts on what might be causing this?