- NewspaperHeader Builder
- NewspaperHeader ads
- NewspaperHeader styles
- NewspaperSearch setup for custom post type
- NewspapertagDiv Composer – Website Manager
- NewspaperBookmark – Save For Later
- NewspaperWooCommerce: Happy “Add to Favorites!”
- NewspaperModal Popup
- NewspaperFlex Block Settings Guide
- NewspaperPosts Loop Element
- NewspaperHow to Add a Logo in Newspaper
- NewspaperDefault Category Settings
- NewspaperWhen tagDiv Composer is Not Working
- NewspapertagDiv Cloud Library Plugin
- NewspapertagDiv Composer Tutorial
- NewspaperUsing the Theme Translations with WPML
- NewspaperInstagram in Newspaper WordPress Theme
- NewspaperWeather Shortcode
- NewspaperThe Mobile Theme
- NewspaperLogin – How to Enable User Registration
Hi,
Most of the time, the problem is from a shortcode that is not compatible with our theme or a plugin conflict; therefore, after you set it with tagDiv Composer and save the page/cloud template, the next time you try to edit it, you’ll get that error.
If is only for one page or a cloud template (it can be on the header or footer, you can change them for tests and see if the problem persists), this is from some settings/shortcodes set on it and it can be fixed using the page revision https://wordpress.com/support/page-post-revisions/
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
Hi,
To change the word search, you need to edit the homepage, select the search element, and log in to the general tab of the Header live search element for the text field – https://prnt.sc/Han4bJ6GIdC_. Change the text there – https://prnt.sc/_7GjxcuNPOeL
Hi,
What you could check is the theme panel settings for the block headers; those options are on the path Newspaper > Theme panel > Theme colors > General theme color https://prnt.sc/x9vjTpLTPxiw
Thank you!
Hi team,
I wanted your support as my site have automatically changed its loading the divTag composer code on the main page, all logs header abd footer have be updated automatically URL: https://primenewsnest.com/
Hi,
What I can recommend is to check with tagDiv Standard package, as you can see the layout in Wayback Machine is similar to that you have now, only the header style is different.
Hi fwoedit,
Ok, I just checked with the wayback machine and your website layout on the previous theme version was this one https://prnt.sc/eFMOrAHsyMip – https://prnt.sc/ip3lnmJD9zgQ https://web.archive.org/web/20260224133746/https://fashionweekonline.com/ and that one is the header style 10 provided by the tagDiv Standard Pack – https://prnt.sc/G9aCrGK_NycV – https://prnt.sc/7YxPmstztfCk
Fixed admin-ajax and was able to save Settings, even re-uploaded logo, still nothing. TagDiv Standard Pack breaks header worse, and I don’t think I was using that before.
We have sent you an email as well with login details, footer and header not working
Hi we just updated the theme, and now look at the errors: https://aktienjournal.com
On header, footer, and in admin we can press customize or Widgets, it gives all kind of errors, can you troubleshoot please? Thank you so much
After updating certain elements are not displaying correctly for example the header block (which normally has our logo) also the featured image is not appearing
https://fashionweekonline.com/
https://fashionweekonline.com/leo-prothmann-autumn-winter-2026-cabana-all-genders-collection
Hi,
The logo image used in email is the one set in the theme panel > header – https://prnt.sc/86FCUmbWVqhP. What you need to do is to make sure that you select there the logo with the size you want for your email, not too big, also not too small.
If there is no need for any payment, then any text/data can be set and you should also make sure that the option to enabled permants is disabled/unchecked – https://prnt.sc/3OjLxD3FfuCR
Thank you!
Hi jareksz,
The zones refer to the header/content/footer zone.
Most of the time, the problem is from a shortcode that is not compatible with our theme; therefore, after you set it with tagDiv Composer and save the page, the next time you try to edit it, you’ll get that error. The simplest and fastest way to resolve it is to use a page/template revision – https://wordpress.com/support/page-post-revisions/ (in this case will be a post template revision).
I hope this will help you!
also the header disappeared
Hi,
Please check the settings, the new categories are categories or subcategories? If are subcategories are under an existing parent category that is set as a mega menu?
For example: Fashion is my parent category and subcategories are: New Look, Street Fashion, Style Hunter, and Vogue https://prnt.sc/npJ0wbXv9AsM make sure that you have articles in each category/subcategory. After that in Appearance> Menu on my header menu I added the custom link and set the name Fashion and make it a category mega menu https://prnt.sc/mLQLcyrGylnz and now on webiste I have this https://prnt.sc/Q_93EnhPh9ZY
If you want, we can also look at your setup. If you agree with this, you can contact us via email at contact@tagdiv.com and provide temporary wp-admin access and as many details as you can related to the settings you’ve made so far.
Thank you!
Instead of seeing my menus, I see a shortcode text. This happened after updating the theme.
I’ve already updated the theme plugins, switched to another header and it still doesn’t work.
No cache plugin currently being used. Attaching an image of the issue.
He intentado seguir tus consejos, pero no soy capaz de localizar header logo. Llego a esta pantalla (https://opinandosinanestesia.es/wp-content/uploads/2026/02/e0fff827-325a-4de8-ae6d-5e9033770763.jpg) y no soy capaz de localizar la ventana que me dices… incluso he eliminado el logotipo de la web y lo volví a cargar (también en la versión movil), y nada. El problema persiste… ¡Qué lio!
Hi,
Please do not share private information like the license key on the forum, only in private.
Please check if you have created any mobile page for your homepage. If you want to use a mobile page, then you also need to create a mobile header and footer for it, otherwise it will use the default one https://prnt.sc/HaTqg6LP9XsR – https://prnt.sc/JOqzo6H4XAoR or if you do not want a mobile page for your homepge just set it to no mobile page – https://prnt.sc/lfklQSaWiWvD
Thank you!
Hi Marc,
I just checked the website, and this seems to be working ok for visitors. Also, I see that you are now using the LiteSpeed Cache plugin.
Now, related to the page speed results, this depends on factors like page dimensions, images, external resources, and cache…
UNfortubatley becouse the latespeed is not a tested pluginwe can not say for sure what option to enable and what option to disable to get a better performance, but let’s start with general pagespeed settings:
– convert images in webp format (there are cache plugins that can do this, but if the Litespeed is not doing this, the EWWW Image Optimizer can be used https://prnt.sc/DzMY6YynebbI). Make sure that only a lazyload option is enabled (the theme has an option https://prnt.sc/4pqTwHya8Awa and most likely other plugins that optimize the image to have the option)
– enable this theme option – https://prnt.sc/Ir7qNRhstgSA – https://prnt.sc/k2M5pc8odE1D (AGGREGATE INLINE CSS option needs to be tested with teh cache plugin)
– disable the mobile header on desktop and desktop header on mobile (this can be done for the sticky headers, but make sure that the mobile cache option is enabled – https://prnt.sc/r3QB7-vZ4UzH https://prnt.sc/KBdRK8nc90UW
– on mobile simply disable the mobile sticky menu https://prnt.sc/IFe6OfBzige7 and select the regular menu and set it to be sticky, also make sure that you have set a background color for it – https://prnt.sc/I6G0kypEakOM
– use an object cache (Redis or Memcached)
– use a CDN like Cloudflare
I hope those first steps to help you to get a better speed.
Hi,
The mobile logo should be checked using the tagDiv Composer as mentioned above, the theme panel settings will apply only in case that no logo is set using tagDiv Composer, but the header you have in use has the logo set using the tagDiv Composer.
The menu problem is related to the amp plugin, if you’ll disable the mobile redirect to amp or remove teh amp plugin, the problem will be resolved – https://prnt.sc/NibvVYdgSGi3
Thank you!
Hi Calin,
The header is still not correct, how can I provide credential to you?
https://we.tl/t-g4Omn53fcp
Thanks,
Thank you for your email.
In the Newspaper menu (within the WordPress admin panel), under Theme Panel → Header → Mobile Header, the theme logo does not appear; however, it does show up in the mobile version.
Regarding the mobile menu issue, we are not referring to a mega menu. It is something simpler. I mean the home menu, where the pages are not visible in the mobile version.
Hi,
You can use the tagdiv Composer to edit the header and add any element you like, such as a button, an icon, or a link to another page or section.
If you have a website example with a specific call-to-action element in mind, please share it with me, and I’ll guide you on how to set it up.
Thank you!
Hi,
Quick update after upgrading Newspaper to v12.7.5.
The issue still reproduces with the Accessibility module enabled (Template Settings → Accessibility (Keyboard + Skip link + Search dialog)), but the behaviour has slightly changed due to the update.
Before 12.7.5, the focus/ARIA conflict typically involved #maincontent. After 12.7.5 (changelog mentions “Accessibility, improved main content wrapper selector”), the browser warning now consistently shows the ancestor being hidden/inert is #td-outer-wrap:
“Blocked aria-hidden on an element because its descendant retained focus…”
Focused element: #td-header-search-button / #td-header-search-button-mob
Ancestor with aria-hidden/inert: div#td-outer-wrap
So the underlying problem remains the same (ARIA hidden/inert applied to a container that still contains the focused search trigger/input), but the update appears to have changed which wrapper is targeted by the Accessibility logic.
We currently mitigate this with a temporary hotfix on our side that prevents aria-hidden/inert from being applied to the wrapper being targeted. After the update, that mitigation had to be adjusted from #maincontent to also cover #td-outer-wrap, which matches the new runtime behaviour.
In short: 12.7.5 changed the target wrapper, but the focus/aria-hidden timing conflict is still present.
Thank you.
Regards.
Hi,
I see that now teh article templates look ok https://prnt.sc/d3IzVFIdPfM4 maybe before you used a cloud template and it is possible that something was interfering with it.
Regarding the header, please confirm whether you have a single Cloud Header or multiple Cloud Headers. It is possible to have more than one, and they can be assigned to specific pages and Cloud Templates.
Any header assigned to a page or Cloud Template will override the global header for the pages or templates where it is assigned.