- NewspaperHow to update a plugin
- NewspaperHow to update the WPBakery Page Builder plugin
- NewspaperHow to Update the Newspaper Theme
- NewspaperSingle Post Excerpt
- NewspaperWP Rocket and Newspaper Theme: Optimization Guide
- NewspaperCredit System
- NewspaperHow to use the Bing Maps API
- NewspaperModules Builder in Newspaper Theme
- NewspaperCreate a frontend submission form
- NewspaperCustom Fields Support
- NewspaperFlex Block Settings Guide
- NewspapertagDiv Opt-In Builder
- NewspaperHow to use the YouTube API
- NewspaperDefault Category Settings
- NewspapertagDiv Composer Tutorial
- NewspaperHow to Set the Image Avatar
- NewspaperUnique Articles
- NewspaperFacebook Share
- NewspaperCache plugin – install and configure
- NewspaperFeatured Image, Video or Audio
After updating our website from the previous WordPress version to WordPress 7.0.1, we encountered several critical issues with the Newspaper theme.
Environment
Theme: Newspaper
WordPress: 7.0.1
PHP: (please fill in your PHP version)
Website: https://suckhoemoi.com
Issues
Frontend displays raw shortcode/JSON instead of rendering the page properly.
Pages show raw tagDiv content instead of the designed layout.
Gutenberg editor reports:
“This block has encountered an error and cannot be previewed.”
Eventually, the entire WordPress admin became inaccessible with a “There has been a critical error on this website” message.
Troubleshooting
We investigated the issue and found that the problem is caused by td-composer.
Renaming the td-composer plugin folder immediately restored access to the WordPress admin.
After disabling td-composer, the critical error disappeared.
This strongly suggests that the current version of td-composer is not compatible with WordPress 7.0.1.
Expected behavior
The Newspaper theme and td-composer should work correctly with WordPress 7.0.1 without causing:
Critical PHP errors
Gutenberg block errors
Frontend rendering issues
Could you please confirm:
Is WordPress 7.0.1 officially supported?
Is there an updated version of td-composer compatible with WordPress 7.0.1?
If not, when will a compatible update be released?
Thank you for your support.
Best regards.
Hi,
we have Accordion Pro on our site http://www.vpz.hr…the problem is with this site for example…https://www.vpz.hr/zupanijska-uprava/upravni-odjel-za-graditeljstvo-zastitu-okolisa-i-imovinsko-pravne-poslove/
and then tab Oglasna ploča….
on desktop its ok….but on mobile its not…there’s some “custom css” code in front of the actual code that works what I entered in that particular accordion…
that “custom css” code wasnt here before…it just appeared somehow hmm
They said this:
Last wordfence security team alert us to minor security issue for outputting script and style may cause security issue,
we are now using wp_kses function to escape accordion content, which causing strip all style and scripts from 3rd party shortcode,
to solve this issue, third party plugins authors must update their plugin to load style and script to header or footer not via old style via content.
I hope you understand, you may report to plugin author that you are using via accordion plugin content.
WHAT CAN WE DO !??
Hi,
I see there was some work done on the review section a while ago in a previous update. The reason was to fix the case when using the points review type, when users were adding commas instead of periods in the values -> https://prnt.sc/zv18e5RW2iYU This lead to calculation problems for the review.
The fix was to automatically transform the commas to periods, intended just for that points input field specifically. But it seems to apply to all the inputs, including the feature name.
I could provide a quickfix for this issue. Please download this file from here -> https://cdn.tagdiv.com/wp-content/uploads/2026/07/td_set_post_settings.zip
Unzip it and there will be a PHP file. That file must replace the existing file via this path in the composer -> wp-content\plugins\td-composer\legacy\common\wp_booster\wp-admin\content-metaboxes
If you want I can do it on your website, and I’ll also test to see if the issue is solved. You can send us an email at contact@tagdiv.com and provide a link to the website, admin user and pass, also access to cPanel or FTP.
We are very sorry for this inconvenience.
Thank you!
Something got messed-up with the header on my blog using the Journal template.
The logo image no longer displays, just text.
PHP Version: 8.2.31
I tried going back two versions to see if it corrected but no luck.
Hello tagDiv Support,
I found a bug in the Review feature of Newspaper theme.
In the Review section, inside the “Feature Name” field, some commas are automatically replaced with periods after generating the preview.
The issue is not happening with every comma, but only with certain occurrences, and it seems to happen during the preview update.
Example:
Before preview:
“Regia, fotografia e montaggio”
After preview:
“Regia. fotografia e montaggio”
Other punctuation marks like “-” and “:” work correctly, and the “Review Description” field does not show this problem.
I have already updated Newspaper to the latest version available, but the issue is still present.
Could you please investigate this behavior?
Thank you.
Hi,
No problem. I can provide WPBakery 8.7.3 so you don’t have to wait until we include it in the next theme update. It will work fine with the theme. You just have to deactivate and delete the version you are using now, and install the new one.
I can provide the plugin by email, please send us an email at contact@tagdiv.com and include a link to this forum topic in the email, so I know what it’s about.
Thank you!
Hello tagDiv Support,
I recently purchased a new Regular License for Newsmag and downloaded the current full package directly from ThemeForest.
The package is Newsmag 5.4.3.6, and the bundled file:
Newsmag-tf/plugins/js_composer.zip
contains WPBakery Page Builder 8.7.2.
Our website currently uses WPBakery 6.13.0, and the homepage depends directly on WPBakery shortcodes. We need to update it securely without breaking compatibility with Newsmag, tagDiv Composer, or the existing homepage layout.
WPBakery’s official changelog lists version 8.7.3 with an additional security-related fix involving capability and nonce verification for frontend preview requests.
Could you please confirm:
1. Whether you can provide a Newsmag-tested WPBakery 8.7.3 package;
2. Whether WPBakery 8.7.3 is officially compatible with Newsmag 5.4.3.6 and may be installed manually;
3. Or whether you recommend installing the bundled WPBakery 8.7.2 version while waiting for a future Newsmag update.
Please also confirm whether an updated ThemeForest package is planned.
Thank you.
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 Simion,
Thank you again. After your database correction, I was able to activate the Newspaper theme successfully.
The license is now registered and assigned to:
The My License panel shows realnews.com.br as ACTIVE, and the Prebuilt Websites section is loading correctly again.
Just as a technical note: we are using a WordPress snippet to improve wp-admin performance by limiting external HTTP requests, but we added a whitelist for WordPress, Envato, ThemeForest and tagDiv hosts.
This is the current snippet:
`php
add_filter(‘block_local_requests’, ‘__return_false’);
if (!defined(‘WP_HTTP_BLOCK_EXTERNAL’)) {
define(‘WP_HTTP_BLOCK_EXTERNAL’, true);
}
if (!defined(‘WP_ACCESSIBLE_HOSTS’)) {
define(
‘WP_ACCESSIBLE_HOSTS’,
‘api.wordpress.org,downloads.wordpress.org,wordpress.org,*.wordpress.org,api.envato.com,envato.com,*.envato.com,themeforest.net,*.themeforest.net,tagdiv.com,www.tagdiv.com,*.tagdiv.com,cloud.tagdiv.com’
);
}
`
At the moment, the license, My License panel and Prebuilt Websites section are working correctly with this snippet enabled.
Could you please confirm if these tagDiv/Envato hosts are enough for Newspaper license validation, updates and cloud features, or if any additional tagDiv host should be added to the whitelist?
I appreciate your help and the correction on your side.
Regards,
Wagner Andrade
Real News
Hi,
We include the latest version for the Revolution slider when the theme is updated. So when a new theme update is released, we add the latest revolution slider in the package.
I can however provide the revolution slider ahead of time if you require it. Please send us an email at contact@tagdiv.com and include a link to this topic in the email. I will provide the latest version.
Thank you!
Hello again,
When will the Revolution Slider get updated in the Themeforest download pack? There has been an update since 22th june, and when I download the latest pack from Themeforest, the version is still not the updated one.
🙂
Then you could try a code like this one:
add_action( 'add_meta_boxes', 'tu_remove_meta_boxes', 999 );
function tu_remove_meta_boxes() {
if ( ! current_user_can( 'manage_options' ) ) {
remove_meta_box( 'td_post_theme_settings_metabox', 'post', 'normal' );
}
}
It can be loaded as a PHP code snippet with a code plugin like this one https://wordpress.org/plugins/insert-headers-and-footers/
Or it can be loaded in a child theme functions file.
It could be loaded in the main theme functions file as well, but this way it will be lost after a theme update and has to be entered again. The more permanent solutions is with a code plugin or child theme.
The code should remove the theme post settings for everyone but admins. You could test it.
Thank you!
Hi,
No problem, I’ll help with what I can.
1. I’ll need more details about what’s not working exactly.
The account element is for logging in or registering -> https://prnt.sc/CfKMNGhSj7ux Which is required if you offer subscriptions for the website visitors, through the plans page here -> https://product-wiki.com/switching-plans-wizard/
The Subscribe button opens a popup, which contains some text and a leads element -> https://forum.tagdiv.com/leads/
2. That’s the same theme leads element, it’s purpose is to gather emails, which you can then export and use in your newsletter services. It isn’t required to use this leads element. If you are using Mailchimp, you could use the form provided by Mailchimp instead -> https://mailchimp.com/help/add-a-signup-form-to-your-website/ That embed code can be loaded in a Raw HTML element from the composer.
3. The theme already has frontend submission capabilities, we added these features some time ago -> https://tagdiv.com/newspaper-theme-12-update-is-live-explore-the-new-features/
All you have to do is to create a page from where the subscribers can submit content -> https://forum.tagdiv.com/create-frontend-submission-form/ You can also set limits based on the plans the users subscribe to -> https://forum.tagdiv.com/subscriptions/ -> https://prnt.sc/fUyrJR_WCnW9
So if your purpose is to provide subscription plans for the website visitors, and based on the subscription plans the subscribers can submit content on your website, this is possible with the theme features, no extra plugins needed. I’ll help as well. I suggest starting by building the content submission page, the guide I provided should be helpful. Then let me know if you have any questions.
Thank you!
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
I’m joining this discussion from topic https://forum.tagdiv.com/topic/margin-padding-fields-display-incorrectly-after-wordpress-7-0-update/#post-542758
I hope for an update to the thread that takes this issue into account, as it’s very annoying.
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.
I will try to explain more.
There are 2 cases when updating the theme manually:
1. After updating the theme, please ask the siteground tech to check in the theme plugins panel and press the update buttons for the plugins -> https://prnt.sc/qVmiCyNjxXgQ
2. Or, download the full theme package from your themeforest account and the theme plugins will be inside the plugins folder:
-> https://prnt.sc/EOCgMuicSEjt
-> https://prnt.sc/OUAeomuMirjI
-> https://prnt.sc/rjXATJ2Xl2ii
Please ask the siteground tech to install those.
I also provided update guides above, which explain these exact steps in detail. There isn’t much else that I could add unfortunately.
If there are still problems, please let me know what exactly the siteground tech is doing, how are they updating the theme, and why they can’t update the theme plugins using the methods described above.
Thank you!
Siteground tech said this: 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.
Hi,
To clarify, the system is automatic, it detects the websites where the key is used but it doesn’t “know” which one is not used anymore. The key must be manually reassigned to the new staging. You can simply ask us to do it.
I see that besides the main website you have 10 staging websites and a localhost install. Out of the 10 staging websites only two of them still work, staging 13 and staging 14. I assume you are currently using staging 14, so I removed the others and assigned they to that one.
Updating the theme is a very simple process. There is an automatic update method which requires a few clicks to update everything -> https://prnt.sc/n9nttzqjdv0N And there are the manual methods as well.
All the theme plugins are provided in the full theme package, meaning this option when you check in your themeforest account -> https://prnt.sc/47jptx7y-tEo That package is the same for everyone. After extracting it the plugins can clearly be found in a folder called plugins -> https://prnt.sc/F68dem0h66Rb
Even without the theme package from themeforest, the plugins can simply be installed from the theme plugins panel -> https://prnt.sc/C3L-mK8stOvR
So unless there are actual issues during or after updating, a theme update can be performed in a few minutes. I’m not sure why it requires a developer to do it, maybe that’s necessary if there are customizations in the child theme, which is fine. But there are also some guides on how to do it:
https://tagdiv.com/update-newspaper-theme/
https://tagdiv.com/how-to-install-plugins-and-update-plugins/
It looks to me that something that normally takes a few minutes to research and perform, is unnecessarily made complicated.
In case I am misunderstanding something, or if you have more questions, let me know.
Thank you!
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,
From what I see the header template is not set anymore, so the theme uses a simple backup header. Normally the cloud templates should still be set after updating the theme.
Please update again. After updating check in the cloud library dashboard to see if the header and the rest of the cloud templates are still set -> https://prnt.sc/mROMJdzK6-_H
Let me know if that’s the case or if the templates are actually set and it still displays like that.
Thank you!
it doesnt seem to recognize it like this tho it keeps being set to the default woff file but i w8 for the update i guess 😉
Hello folks! Before I updated to 5.4.3.6, I was manually rendering a 970×120 ad spot above the logo and had worked out code to resize to match the logo size. Since updating, that solution isn’t working – every solution I try, the ad won’t render wide enough. Any ideas on how I can resolve this?
Thanks in advance!
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!
I’m checking the posts on mobile, and from what I see the widget sidebar is actually after the featured image and the post content -> https://prnt.sc/72J2qFN98ASg It’s certainly not positioned as in your screenshot -> https://prnt.sc/hBh_5lIjRovc It can’t be there.
In order for the widget sidebar to be after the comments, it means that you were viewing the desktop post template on mobile. Maybe it was a caching issue or the mobile template was not yet set.
I see you disabled the infinite loading for posts. Infinite loading is a feature from the theme -> https://forum.tagdiv.com/infinite-loading-single-posts/
Basically most of the theme users already updated to wordpress 7. There are no major issues. All we plan to do is fix a few minor issues, and add a bit of compatibility with the new wordpress features if possible. You could update wordpress and it should work fine.
Thank you!
