- NewsmagHow to use the Visual Composer plugin
- NewspaperFlex Block Builder and Flex Loop Builder
- NewspaperModules Builder in Newspaper Theme
- NewspapertagDiv Shop
- NewsmagtagDiv Composer Tutorial
- TutorialsFrom WPBakery to tagDiv Composer
- NewspapertagDiv Composer Tutorial
- TutorialsDefault Block Settings Guide
- NewspaperCreate Custom Code with the browser’s Inspector or the Live CSS Box
- NewspaperCompare theme files – Winmerge tutorial
- NewsmagWhat’s included in Newsmag theme package
- NewsmagNewsmag documentation
- NewsmagBlock settings tutorial
- NewsmagHow to update the WPBakery plugin
- NewsmagCustom ad spots
- NewspaperHow to update the WPBakery Page Builder plugin
- NewspaperBlock settings tutorial
- NewspaperPost Formats (for TinyMCE)
- NewspaperFont Customization
- NewspaperBackground Introduction
Hi,
Thank you for your previous guidance.
I’m following up because I already completed the recommended update process, but the issue still persists.
What has already been done:
WordPress was updated.
The Newspaper theme was updated from the old version 7 to the current version 12.
WPBakery / Visual Composer was updated.
The bundled Newspaper/tagDiv plugins were reviewed and updated.
The site files and database were backed up before making changes.
PHP/server compatibility was also reviewed.
After completing those updates, the main issue remains:
The frontend still displays the WPBakery / Visual Composer shortcodes as plain text instead of rendering the page content properly.
For example, the page still shows code like:
[vc_row][vc_column]…[/vc_column][/vc_row]
Also, when activating tagDiv Composer, the website shows an error, so the builder functionality is still not working correctly.
At this point, since the recommended update process has already been completed, could you please help us investigate the remaining issue directly?
It seems that one of these problems may still be happening:
WPBakery shortcodes are not being parsed correctly.
tagDiv Composer is failing during activation.
A required Newspaper/tagDiv component is missing or corrupted.
The old page content from Newspaper 7 / WPBakery is not being processed correctly after the migration.
The page content may need to be repaired, but we need confirmation before rebuilding anything.
For security reasons, I will not post credentials publicly here. I can send fresh temporary WordPress admin and cPanel access privately through email or the proper support channel.
Could you please confirm where I should send the access details so you can review the activation error and shortcode rendering issue?
Thank you.
Best regards,
Adalberto Larios
Hello,
Since updating to WordPress 7.0 today, I have detected a visual/functional issue in the builder’s CSS panel, specifically in the Margin / Padding fields of the Single Image module.
I’m leaving you a Loom video where the behavior can be seen clearly:
https://www.loom.com/share/26601c055dd3494d9745ede4635d838b
The problem is the following: before the update, within the visual margin/padding scheme, the fields allowed values of at least two characters or values with a unit to be displayed correctly. For example, if a padding value was 10%, the field allowed me to see 10 or 10%, or at least scroll inside the input in a useful way to check the full value.
Now the behavior has changed. The fields are displayed too narrow and only show one character of the value. For example, visually it may look like the padding is 1 / 1 / 1, but in reality the values are of the type 10% / 10 / 10%. When I move inside the field, instead of being able to see the full value or at least two characters, only one character is shown at a time; in this example, in order to see the %, I have to move within the field and instead of being able to see 0%, as part of 10%, only that is shown: the %.
This makes the CSS panel difficult to use, because I cannot visually check whether the real value is 1, 10, 10%, etc. The problem does not seem to be that the value has been lost, but rather that the panel input is displaying it cut off or with insufficient width. I have been using TagDiv for more than 7 years and I know what I am talking about when it comes to composition and the details of the composer.
I have tested it both in the desktop composer and in the mobile composer. I have also tested it in incognito mode, in case it could be due to browser cache. In addition, the page cache was cleared after the update.
For this reason, I understand that it could be a visual incompatibility of the builder after updating to WordPress 7.0, an internal CSS issue in the panel, a change in the width of the inputs, a rendering issue in the editor, or some incompatibility with the current version of WordPress/browser.
It is not necessarily that the page design has changed, but rather that the editor no longer displays the full values correctly inside the margin/padding fields.
The issue directly affects editing, because it makes it very difficult to review or modify margins and paddings without the risk of changing incorrect values.
Thank you. Please, I would really appreciate your help with this.
Hi,
There’s much to discuss here.
Did you maybe update wordpress before all these issues happened? I see the website uses wordpress 7, which is the latest version released recently. And it uses Newspaper 7, which from 10 years ago. Also WPBakery 5, which is from 10 years ago.
I suggest updating everything, because it will have to be done eventually. Then the remaining problems can be investigated.
We still provide WPBakery in the theme package -> https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
WPBakery does not require a license, it has always been provided by us as a bundled plugin according to the guide -> https://help.market.envato.com/hc/en-us/articles/213762463-Bundled-Plugins
So a bundled plugin doesn’t require activation -> https://prnt.sc/nAR4whjbEtY5
If a page is displaying code, it usually means that either the plugin that renders that code is not active, or the page is broken. If the WPBakery plugin is active and there is still code, then the page must be broken. Updating the theme will not fix a broken page. The code from the page must be reviewed to see why it is broken. Or, if a recent modification broke the page perhaps and the page worked fine before, then an older revision can be restored -> https://prnt.sc/JgbjlyL-i6W2
Worst case scenario, the page must be rebuilt, which takes a few minutes, but not necessary if it can be fixed.
My suggestion is to update everything first. Then I will investigate any remaining issues. You can send us an email at contact@tagdiv.com and provide admin login for the website so I can investigate. I’ll help as much as I can.
Let me know.
Thank you!
Hello,
We are currently working on the website:
https://www.sostenible.com.mx/
We are having an issue with the page editor / builder. The pages are no longer editable through the builder, and on the frontend the content is being displayed as raw Visual Composer / WPBakery shortcodes instead of being rendered properly.
For example, the homepage is showing content like:
[vc_row][vc_column][td_block_ad_box spot_id="custom_ad_2"]…
[td_block_2 custom_title="ACTIVIDADES PRIMARIAS"]…
[/vc_column][/vc_row]
The site was originally running an older version of the Newspaper theme, version 7. Everything was working correctly before, but the issue suddenly started. We then migrated/updated the theme to version 12, expecting the problem to be resolved, but the issue still persists.
Based on what we are seeing, it looks like the problem may be related to Visual Composer / WPBakery Page Builder, because the builder is not loading correctly and it appears to be asking for a license or activation. Since the content depends heavily on Visual Composer / WPBakery shortcodes, the site is currently unable to render the pages correctly.
Could you please help us review the following?
Confirm if the bundled Visual Composer / WPBakery plugin included with the Newspaper theme is active and compatible with version 12.
Check if the plugin requires a separate license or if it should be activated through the theme package.
Verify why the shortcodes are being printed as plain text instead of being parsed/rendered.
Confirm if there is a missing plugin, corrupted builder installation, or compatibility issue after the migration from Newspaper v7 to v12.
Let us know the recommended steps to restore the page builder functionality without losing the existing page content.
The main issue is that the website content is still stored using Visual Composer / WPBakery shortcodes, but the builder is no longer processing them correctly.
Thank you.
Best regards,
Adalberto Larios
Hi,
From what I see only the homepage is indexed https://prnt.sc/20wGw_TYFNur
The theme has no capability to use noindex, or index, or anything else. All the theme does is to display your content.
Perhaps the nature of the issue is more related to how the website looks.
I see broken and missing images everywhere and a very large ad at the top, also the sticky header has no background and it looks a bit bad. For example this is what I’m seeing when arriving on the homepage of your website -> https://prnt.sc/wwnagCba-OA_
Please check the website in incognito mode to see how it looks for a regular visitor. That’s how it looks to Google as well.
Here are some more broken things I’m seeing
https://prnt.sc/UKT_uotknb1n
https://prnt.sc/5SvO1ew1QN_M
https://prnt.sc/Ztmcn9qE6mh8
https://prnt.sc/oMhe6g8lG5uq
These could be a reason for not indexing the website’s content. If the website has visual problems Google may not index it. I suggest looking into these issues, maybe the visual issues are related to the litespeed optimization. And maybe the missing images https://prnt.sc/V56A1nVfHgWj are related to the Jetpack site accelerator, I see you use it.
Once those issues are fixed, the website should look better and it can’t hurt the indexing either. Let me know if you need help with it.
Thank you!
Hi,
It’s the same for me. The option still works when clicked, but visually there’s no indication to know if it’s clicked or not. We will have to test it more. I believe it used to work before, so it might be something related to WordPress 7, if you also use the same.
Thank you!
Hi,
Many of our users have updated already. There are no major issues that we identified, only a few minor ones, like the new visual revisions feature not working https://publishpress.com/blog/revisions/wordpress-70-revisions/ But this may not work because of other plugins as well.
If you want to make sure that there are no issues after updating, you could test first on a staging/testing clone of the website, if possible. If all is well there, then you can update on the main website.
Thank you!
The new Visual Revisions feature in WordPress 7.0 doesn’t appear to be compatible with the Newspaper theme.
Are there plans to make it work? It’s a very helpful feature and one I’m sure Newspaper users would like to take advantage of.
We have a support contract and are seeing two issues we’d like your help resolving.
I can send further sensitive or confidential information to your contact email referencing this specific ticket.
— Issue 1: Layout sync error blocking front-page edits —
When attempting to edit the front page in tagDiv Composer, the editor displays:
“Layout sync error in Header, row 2. The editor expects 1 element but the page is rendering 0. Usually caused by an unclosed HTML tag in a text block (e.g. <div> without </div>). View page | Undo (Ctrl+Z / Ctrl+Shift+Z) to restore.”
The error points to the header ad position in Header row 2, which renders as an “EMPTY INNER COLUMN” with a red outline in the editor.
The Undo shortcut (Ctrl+Z / Ctrl+Shift+Z) does not fix the problem.
This has been an ongoing issue for multiple months and is preventing front-page edits.
— Issue 2: Sidebar preview missing in post editor —
After updating our various web sites to 12.7.6, the post editor no longer shows the sidebar reservation area — the visual cue that previously showed the authors the actual rendered width of the post content with the sidebar reservation accounted for.
This affects both the production site and the dev site. Other sites we host using prior versions of the theme are not affected and continue to show the sidebar preview correctly.
Thanks — looking forward to getting this resolved.
Hello @Calin
I am writing to you after a deep technical audit that lasted two days, conducted by a Senior Infrastructure Engineer and Web Performance Specialist. We had to take this measure because our PageSpeed scores are stuck between 31% and 41% on mobile, despite running on a high-end VPS with persistent cache (Redis/Object Cache) and every possible server-side optimization.
Google has officially notified us regarding this poor performance, stating that our site is no longer a priority in search rankings due to failing Core Web Vitals. After a thorough investigation of the source code and database, we have pinpointed the root cause: The Newspaper theme is loading both Desktop and Mobile assets simultaneously on mobile devices.
Even with dedicated mobile pages (separate IDs), the theme “stacks” the entire desktop framework on top of the mobile one. This redundancy is killing our performance.
I need you to take this diagnostic to the tagDiv development team immediately. We need to know if and when a fix will be released. If this architectural flaw is not resolved, I will be forced to migrate to another theme or develop a custom one, as I cannot afford to lose my SEO ranking due to theme bloat.
Technical Diagnostic:
Problem: Mobile pages heavier than desktop pages
Date: 03/05/2026
Theme: Newspaper 12.7.5
Plugin: td-composer
Server: VPS Ubuntu — CyberPanel — LiteSpeed
CONTEXT
The site glostv.com uses the Newspaper 12.7.5 theme with the td-composer plugin and has a system of separate pages for mobile and desktop, where each version was built individually in the Newspaper visual editor (tagDiv Composer). The site owner reported that pages on mobile are significantly heavier than on desktop, even though there are separate and optimized mobile pages already built.
MOBILE SYSTEM ARCHITECTURE
The following pages were created as mobile templates inside the tagDiv Composer itself and are marked in the database with the flag tdc_is_mobile_template = 1:
ID 7584 — tv ao vivo Brasil (mobile version)
ID 7617 — POPULARES TOP (mobile version)
ID 8700 — Estados (mobile version)
ID 8872 — Homepage (mobile version)
ID 9944 — Política de Privacidade (mobile version)
ID 9948 — Termos de Uso (mobile version)
ID 10581 — Sobre Nós (mobile version)
ID 10597 — Política de Cookies (mobile version)
TECHNICAL PROBLEM IDENTIFIED
Problem 1 — td-composer loads assets WITHOUT any device distinction
Confirmed directly in the file:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php
Line 362 — Composer JS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_js_composer_front’, 1000);
Line 430 — Full Newspaper CSS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_front_css’, 1001);
Line 744 — Full theme JS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_front_js’);
None of these functions have any device check. They load for both desktop and mobile equally, without any condition whatsoever.
Problem 2 — The mobile engine loads ON TOP of the desktop engine
Confirmed in the file:
wp-content/plugins/td-composer/mobile/functions.php
Line 149 — Mobile CSS loads ON TOP of the desktop CSS already loaded:
add_action(‘wp_enqueue_scripts’, ‘tdm_load_front_css’);
Line 173 — Mobile JS loads ON TOP of the desktop JS already loaded:
add_action(‘wp_enqueue_scripts’, ‘load_front_js’);
Line 184 — Mobile specific script loads ON TOP of all previous ones:
wp_enqueue_script(‘td-site’, TDC_URL.’/mobile/js/tagdiv_theme.min.js’);
Problem 3 — The flag tdc_is_mobile_template does NOT remove desktop assets
Confirmed in the file:
wp-content/plugins/td-composer/includes/tdc_state.php
Line 42:
private static $is_mobile_template = false;
Line 202:
public static function set_is_mobile_template($is_mobile_template) {
self::$is_mobile_template = $is_mobile_template;
}
This flag only serves to let the visual editor know it is on a mobile page. It does not execute any removal of desktop CSS or JS. It is purely an internal state variable with no effect on asset loading.
Problem 4 — Proof: Zero wp_dequeue for mobile anywhere in td-composer
I ran the following command directly on the server via terminal:
grep -r “wp_dequeue|deregister” wp-content/plugins/td-composer/ -n | grep -i “mobile|desktop|css|js”
The only result found was the removal of Visual Composer scripts in the backend administrative editor, not in the frontend. Throughout the entire td-composer codebase, there is not a single wp_dequeue_style() or wp_dequeue_script() instruction conditioned on mobile device detection in the frontend.
WHAT THE MOBILE BROWSER IS ACTUALLY DOWNLOADING
When a user accesses the site from a mobile device, the browser downloads all of this before rendering the mobile page:
From the desktop engine (which should NOT load on mobile):
Full legacy CSS of Newspaper
td-composer frontend JS (desktop visual engine)
tagdiv_theme.min.js desktop version
td-cloud-library CSS
td-standard-pack CSS
td-multi-purpose/style.css
Desktop version fonts
From the mobile engine (which loads ON TOP of the desktop):
Newspaper mobile CSS
tagdiv_theme.min.js mobile version
Mobile specific scripts
Fonts loaded again
The mobile browser is downloading the complete Newspaper framework twice. Once for the desktop layout that is discarded and once for the mobile layout that is actually used. This directly explains why mobile pages feel heavier and slower than desktop pages. DIRECT QUESTION TO SUPPORT
Does td-composer 12.7.5 have any native mechanism to remove desktop engine assets—specifically the functions load_front_css, load_js_composer_front, and load_front_js located in td_wp_booster_functions.php—when the page being served is already marked with tdc_is_mobile_template = 1 in the database?
If yes, in which file and on which line does this asset cleanup occur?
If no, when is the development team going to release an update to fix this? It is unacceptable that a high-end theme like Newspaper forces a mobile device to download the entire desktop framework AND the mobile framework simultaneously. My server-side analysis confirms that even when using dedicated mobile pages, the theme simply “stacks” assets instead of “swapping” them.
This redundancy is causing a massive performance overhead and killing our Core Web Vitals. We have separate pages for a reason, and the theme should NOT be loading desktop junk on a mobile-dedicated template. We need a clear position on when this will be resolved so that tdc_is_mobile_template = 1 actually triggers a wp_dequeue of unnecessary desktop resources.
Hi,
Alt text is primarily for accessibility (screen readers for visually impaired users) and SEO. It’s not meant to be a tooltip (that image likely has a title attribute set. Browsers show the title as a tooltip on hover, not the alt text).
=> alt – for screen readers (not hover)
=> title – shows tooltip on hover
If you want all images to show hover text, set the title attribute for each image.
Thank you!
Hello,
Thank you for your previous help. I need assistance with two issues in the Newspaper theme / TagDiv Composer.
1. Google Fonts and local fonts
The theme is loading fonts from Google, and this is heavily affecting the site’s performance because of render-blocking requests. The theme does not properly use local fonts by default.
I tried using local fonts inside TagDiv Composer, but I had to do a workaround, and that is not the correct solution. I also created a Newspaper-child theme and managed to load local fonts from there, but the result was not good because the fonts do not look exactly the same as the original Google Fonts.
What I need is a proper solution that makes the theme use local fonts, while still allowing me to select the fonts normally in TagDiv Composer. In other words, I want the theme to keep the same visual appearance, but load the font files locally instead of requesting them from Google.
What is the correct way to do this?
2. Hiding the “Most Watched” section title
I am trying to hide the title of the “Most Watched” section shown here:
https://ibb.co/6cmh3VH8
This section appears in this post:
https://glostv.com/tv-ao-vivo/tv-cultura
and also in all other posts.
I used the following CSS:
CSS
.tdi_54 .entry-title,
.tdi_54 .td-module-title,
.tdi_54 .td-module-title a {
display: none !important;
}
The problem is that this is also hiding titles on the Popular page:
https://glostv.com/populares
This should not happen. These elements should not be sharing the same .tdi_54 behavior for this case, or at least I need a more specific way to target only the “Most Watched” section inside posts.
How can I hide that title only in the post section, without affecting the Popular page?
Thank you.
Hi, I need to update che WP Composer on my newspaper theme. I followe this tutorial https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/ but inside the last theme packages there is no js_composer.zip and without that i cannot update php version and use my site
Hi,
With Yoast SEO Pro, author (Person) and publisher (Organization) schema are automatically separated, each getting a unique @id.
The Newspaper theme mainly displays author info visually (name, bio, avatar, social links) but does not automatically pass this data into Yoast’s structured data. So Yoast generates its own author node based on WordPress user data, which is separate from the publisher node.
Thank you!
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 have created two custom blocks. I want to use them inside a “Module cloud template” to render items in a “Flex Loop Builder”
I used de td-api-plugin. I can drag and Drop de block inside de tag div editor but something is not working. I can save de “module template” the first time but when i edit again it returns an ERROR “Errors at columns elements: 1(models) : 0(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)”
What i am doing wrong?
This is how i add the api block (it has no parameters, all is coded into de file that renders the module -> td_video_empresa.php):
td_api_block::add('td_video_empresa',
array(
'map_in_visual_composer' => false,
'map_in_td_composer' => true,
"name" => 'Mòdul Video Empresa',
"base" => "td_video_empresa",
'tdc_category' => 'Modules elements',
'file' => $this->plugin_path . '/modules/td_video_empresa.php',
"params" =>
array_merge(
td_config::get_map_block_general_array()
)
)
);
This is the file that renders the block -> td_video_empresa.php
class td_video_empresa extends tdb_module_template_part {
function render( $atts, $content = null ) {
/* -- Call the parent render method -- */
parent::render($atts);
/* -- Retrieve the module post data -- */
$post_obj = self::$post_obj;
$post_type = null;
$postID=$post_obj->ID;
$url_video=get_field("url_video_empresa",$postID);
$video_extern=get_field("link_finestra_nova",$postID);
$logo=get_post_thumbnail_id($postID);
$linkEmpresa=get_permalink($postID);
$tituloEmpresa=$post_obj->post_title;
$string="";
$string.=renderVideo($url_video,220,$tituloEmpresa,$postID);
$string.='<div class="modul-caixa" >';
$string.='<h3 style="margin:0px;">'.$post_obj->post_title.'</h3>';
$string.='</div>';
return $string;
}
}
Hi,
1. There is no official minimum word count for Google AdSense approval. Quality, originality, and usefulness matter more than word count. However, most successful applicants publish: 600–1200
2. To create high-quality, valuable content using the Newspaper Theme, follow these best practices:
– Use clean, readable layouts – Choose simple templates and avoid clutter.
– Focus on in-depth, original content – Publish well-researched articles (800–1,500+ words).
– Optimize typography and spacing – Make text easy to read on desktop and mobile.
– Use high-quality images and media – Add relevant visuals to support your content.
– Structure properly – Use headings (H1, H2, H3), bullet points, and short paragraphs.
– Improve SEO settings – Optimize titles, meta descriptions, and internal linking.
– Ensure fast loading speed – Avoid too many ads or heavy plugins.
– The key is combining strong content with a clean, user-friendly design.
3. The TagDiv Composer will be used to create pages and templates, but not posts, for posts will be used the wordpress editor (Gutenberg or classic editor) – https://www.youtube.com/watch?v=SoGQ0d5kIBg
Thank you!
Hello,
It is not necessary to install any additional plugins. A well-structured and visually appealing design will be sufficient. For this purpose, you can use tagDiv Composer and tagDiv Cloud Library. You may select and customize one of the available Cloud templates, modify the existing theme templates, or create your own templates from scratch to meet your needs.
Just noticed on our website the join portion of the sign in/join menu is not working?
It only gives visitors the opportunity to login in with a username and password.
That explains why we have a ton of traffic and no members
Hello,
with WPML active on Newspaper I’m unable to properly translate Cloud Templates, in particular:
• Single Post Templates
• Author Templates
When I click the “+” icon to add a new language:
a new duplicated template is created
it is not assigned to the selected language
the “Used on” field is not preserved
the new template is not linked to the original one
WPML opens the standard WordPress editor instead of the WPML translation editor
I also followed your official guide:
https://tagdiv.com/wpml-newspaper-theme-compatibility/
However:
the UI/visual layout is different from what is shown in the guide
the described workflow does not work in my case
Setup:
Newspaper theme (latest version)
Cloud Templates enabled
WPML with Advanced Translation Editor
Languages: Italian / English
I would like to ask:
Is there an official and supported workflow to translate Single Post and Author Templates with WPML?
Is this a known bug or limitation?
Do Cloud Templates require any special configuration in WPML (post type tdb_templates)?
Thank you for your support.
Best regards,
Valerio Platania
WeSicily.it
Hello TagDiv Support Team,
I am building a multilingual news website using the Newspaper theme with Polylang for language management. My site requires support for three languages: Arabic (RTL), French (LTR), English (LTR)
I have created a child theme and need guidance on the best practices for implementing proper RTL/LTR support to ensure the theme layout adapts correctly for each text direction.
Specific questions:
How can i have a header & a footer for each type ? when i update anything it updated for all the website ? and for single post template or category template i cannot change the direction for only rtl languages, how can i achieve that ?
Current Setup:
Newspaper Theme (latest version)
Polylang plugin (for language management)
Child theme active
Languages configured: Arabic (RTL), French (LTR), English (LTR)
Goal:
A seamless experience where the theme automatically adapts its layout and design when users switch between Arabic (RTL) and French/English (LTR), while maintaining the same visual design across all languages.
Any documentation, code snippets, or best practices you can share would be greatly appreciated. If there are specific hooks, filters, or CSS classes I should be aware of, please let me know.
Thank you for your support!
Best regards,
Hi,
I’m switching theme to Newspaper, and am using a free version of Paid Memberships Pro plugin – it has already been in use and there are active subscribers.
I would like either to switch completely using Opt-In Builder, and be able to migrate existing subscription data from PMP plugin to Opt-In Builder – or be able to sync existing subscription data with PMP plugin. So that I could use tagDiv Composer’s locker paywall feature in the visual builder.
How to achieve this?
During a development day it’s entirely possible I’d be loading the page over a thousand times… They would charge 0.14 cents per each call over 1k calls per day. Plus this site actually reaches 1k loads a day.
Well, maybe your widget already does caching where a page load would not necessarily equate an API call, but my point is that the paid tiers of OpenWeather API are on the more expensive end of the spectrum.
In comparison Weather API has a million calls a month as it’s starting free tier. It’s first paid level is Starter with 3M calls a month at just $75 per year, in comparison to $35 per month as OpenWeather’s first paid level.
The most popular free widget Location Weather has integrations to both Weather API and OpenWeather API, but offers most of the visual configuration options in paid Pro version.
PS. Your widget does look good by default. It would be nice to be a bit more robust especially in terms of integration options. Your competitor JNews’s widget which I previously used offers, was it, 4 integration options out of the box.
Hi –
I cannot figure out how to select / adjust the fonts used in my site sidebar…
https://www.leanblog.org/2024/12/visual-management-gone-wrong-christmas-grocery-store/
I’d like the header and copy fonts to match the site defaults that I recently changed.
Thanks,
Mark
Hi.
I’m having a peculiar problem with the Slider Revolution bundled in Newsmag: the preview is not working on the slider editor. When I try to create a slider it just won’t show up in the preview window, I just get a blank (grey, in this case) window. However, the shortcode is generated and it works fine when I place it in a post or a page. So I’m working blind, cause I have to keep coming and going between the editor and a page in my site to visualize the work in progress, which off course is far from ideal.
I have already discarded conflicts with other plugins and found no relevant issues in the browser console. The PHP version, the WP memory limit, the PHP execution time and the PHP Max Input Vars comply with the theme requirements.
WordPress version 6.9
Newsmag version 5.4.3.4 (license bought a couple of weeks ago).
Tech prebuilt website
Slider Revolution version 6.7.38
I see SR is now on version 6.7.40, which means two updates have been released in the last two months. I wonder if this bug has been addressed in any of them.
My site is http://torundabit.com, but you find there any slider created with Revolution, given that I cannot adjust the one I’m trying to create.
Anyway, I would apreciate any help to resolve this issue.