Search Results for 'remove tag from post'

Hello everyone,

I’m having a license activation issue with the Newspaper WordPress Theme by tagDiv and I would like to know if anyone has experienced something similar.

I have an official Envato/ThemeForest Regular License for Newspaper Theme. The purchase is valid and the item still appears in my Envato downloads area. The license certificate confirms the purchase for:

Tema: Newspaper – News & WooCommerce WordPress Theme
Autor: tagDiv
Tipo de licença: Regular License

The theme had been working on this website for years.

The problem started after I reset the license key/domain association inside the Newspaper/tagDiv panel. After the reset, the license seems to have lost its association with the domain, and now I cannot activate it again.

Current behavior:

1. With no HTTP-blocking snippet active, WordPress Site Health does not show any warning about external HTTP requests being blocked.
2. When I try to activate the theme with the official Envato purchase code, the Newspaper activation page shows:
“Your purchase key is not valid.”
3. Earlier, when a performance snippet was active, the activation screen showed:
“Envato API is down, please try again later.”
4. That snippet was related to WP_HTTP_BLOCK_EXTERNAL, but it has already been disabled for testing.
5. With the snippet disabled and server cache cleared, the error is no longer the API error — it is now:
“Your purchase key is not valid.”
6. The key is the official purchase code from Envato, and the product is still listed in my Envato account.

It looks like the reset removed the domain association, and now the tagDiv validation system is rejecting the same official purchase code instead of allowing me to reassign it to the website.

I have already contacted tagDiv support, but I’m posting here in case someone has gone through the same situation and found a faster technical workaround.

Has anyone experienced this after resetting a Newspaper Theme license/domain association?

Is there any safe way to force the theme to re-sync the license with tagDiv/Envato, or does this require tagDiv to manually reassign the domain on their side?

Important: I am not sharing the full purchase code publicly for security reasons, but I have the official Envato license certificate and proof of purchase.

Thank you.

Hello,
I have a critical issue on my news site: I cannot publish new articles. When accessing the editor (Add New Post), the page stays blank.
Technical details:

WordPress: version 7.0 (latest)
Theme: Newspaper, version 12.7.6 (latest)
tagDiv Composer: latest version available
All plugins are up to date

Console error (DevTools):
edit-post.min.js?ver=28ef50b859708963e197:1 Uncaught TypeError: (0 , yt.registerLegacyWidgetBlock) is not a function
at Object.pn (edit-post.min.js?ver=28ef50b859708963e197:1:49057)
at HTMLDocument.<anonymous> (wp-edit-post-js-after:5:25)
There are also deprecation warnings related to your blocks:
Block with API version 2 or lower is deprecated since version 6.9.
Note: The block “tds/partiallocker” is registered with API version 1.
Note: The block “tds/contentlocker” is registered with API version 1.
Plus a 404 error when loading load-scripts.php.
Likely cause: the registerLegacyWidgetBlock function from the @wordpress/widgets package was removed in WP 7.0, while a script injected by your theme/Composer (wp-edit-post-js-after) is still calling it, which completely breaks the Gutenberg editor from loading.
What I’ve tried:

Temporarily deactivating other plugins (issue persists, so it’s isolated to Newspaper/tagDiv Composer)
Clearing cache (LiteSpeed Cache, full purge)
Confirmed all components are on the latest version

Please confirm if this is a known compatibility issue with WP 7.0, and let me know your estimated timeline for a fix/patch. In the meantime I’m using Classic Editor as a workaround, but I need Gutenberg working again as soon as possible since the site is active and requires frequent article publishing.
Thank you

Hello,
I have an Instagram activated and embedded into my page code.
It used to work normally. However, now I noted that when browsing the page in Incognito mode, the photos not showing.
If I am browsing the site from my normal signed in Google Chrome browser, the photos are showing normally.
I removed connection and reactivated it again, but it did not help.
Because in incognito mode it shows 7025 followers, while in normal mode it shows 8690 followers (actual currnt number is 8691 followers), I understand this is a cache issue.
I do have both EWWW and SWIS activated.
When I deactivate SWIS, the incognito page starts to show photos/posts normally and the number of followers raises to 8690.
So clearly SWIS and Instagram feature do not like each other.
Can you advice how can I make Instagram feature and SWIS be friends?
My web site is photography site with heavy pages, so caching is important to me.

Hi tagDiv team,

I have a Flex Block 1 (configured as “Latest news” widget in the homepage left column)
that renders empty in the frontend but displays posts correctly in the Composer editor preview.

DETAILS:
– Theme: Newspaper v12.7.5 (REGISTERED)
– Demo installed: Newsweek PRO
– Site: https://eurowaypoint.com
– WordPress: 6.9.4
– PHP: 8.2.30

THE PROBLEM:
– In Composer editor: the Flex Block 1 shows the latest 5 published posts correctly
– In frontend (incognito browser, logged out): the block container is generated
(div id=”tdi_96″ class=”td_block_inner td-mc1-wrap”) but completely empty —
no child modules are rendered inside
– 24 published posts exist in the database
– Other blocks on the same homepage (Big Grid Flex 1, other Flex Block 1 instances)
work correctly and display posts
– No JavaScript errors in browser Console
– The block has no special filters configured (Category: All, all filter fields empty)

WHAT I’VE ALREADY TRIED:
– Cleared all caches (SiteGround, WP Super Cache disabled, browser hard reload)
– Restored Homepage from a 3-day-old revision (no improvement)
– Disabled all third-party plugins one by one (Wordfence, SG Optimizer, etc.)
– Verified block configuration in Composer (Filter tab, Layout tab — all default/empty)
– Forced re-save of the block (changed limit number and saved)
– Removed custom CSS that contained :has() selectors

WHAT I NOTICED:
The block was working until I made some modifications today (changed page slug from
/plans/ to /newsletter/, edited some HTML custom blocks for Subscribe links).
The Latest block stopped rendering at some point during these changes.
Restoring an older Homepage revision did NOT fix it.

Could this be a corrupted block state in the database? Is there a way to reset
the block’s internal cache or regenerate its configuration?

Thank you for your help.

Just a heads up; Google has become even more aggressive in their effort to stop barrage of junk news networks doing nothing but parroting other news sites, press release newswires, etc. Over 10,000 popped up starting in 2023-2025. In Q4/25 Google started removing low quality sites from Google News, then moved on to the main search (!).

Sites with too much “non origin” content, may be hidden, even using “show duplicate” quoted search for “headline” and/or site:yoursite.ooo.

This means it’s now critical to be a “first origin” content creator, and not repost other site content, even if linking to them; avoid AI junk content farms and remove stuff like tags with only one item attached to it, redundant content (e.g., black friday deals from 2023 not relevant in 2026).

Couple of my sites that pre-date Google News got caught in this. Two have recovered. The two that got whacked rank highly in the Bing/Yahoo/DuckDuckGo streams, luckily.

One of my blogs (all original content), had 1200 pages deindexed last year, and just got email from Google saying “eror has bee fixed- error 1200 pages scraped but not indexed” (or something like that). On my music blog, I deleted a rogue redirect plugin, removed old tags from decade ago, and cleaned things up.

This is a real issue with Google now “censoring” the internet if they don’t like how you roll, which is part of their new focus on being an ad platform and answer engine, and *NOT* a search engine.

Also, make sure you add the IndexNow plugin and configure it. Better to use the plugin directly than use something like Yoast.

Just food for thought. On our big site, I have deleted about 6,000 stories which were old, stale, and sourced from other sources as part of the site news “syndication” for national news.

As the old TV show* used to say, “Be careful out there.”

(*Hill Street Blues) 🙂

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 TagDiv Support,

I am using the Newspaper Theme (latest version) with TD Composer.

I am experiencing a template-level issue in the Single Post Template – Free News.

Issue Description:

A block titled “আরও দেখুন” (More Stories / Category tag list) is automatically appearing at the top of all single post pages.

This block:

• Appears in two different layouts across different posts
• Is not selectable inside TD Composer
• Clicking on it opens a sliding overlay panel instead of selecting a Row/Element
• Does not appear properly inside the Manager structure
• Cannot be removed from the template

What I Already Tried:

Disabled Articles Auto Loading

Checked Single Template Settings

Checked Category Template

Disabled Related Articles

Disabled More Articles Box

Cleared Cache (LiteSpeed)

Edited the template from Cloud Templates

Tried deleting the Row via Backend & Frontend editor

Still, the block persists.

Observation:

It seems like the block is injected dynamically (possibly via auto-loading, category module, or internal tdb_single_content hook).

When clicking the block, only the gear (⚙️) icon works, and the rest of the area is not selectable — which suggests a layer or JS overlay conflict.

Request:

Please clarify:

From which template hook or module is this block generated?

Is it part of tdb_single_content?

Is it controlled by a hidden “Tags” module?

How can I permanently remove it from the Single Post template?

This is affecting layout consistency and UX.

Website: https://newsbazar24.com

Theme: Newspaper
Template: Single Post Template – Free News

Screenshots attached for reference.

Thank you.

Best regards,
Sankar Chakraborty

Hello,

I’m looking for clarification on the following tag page on our site:

https://www.macworks.com/blog/tag/apple-support-ct/

I’m unclear on a few points and would appreciate guidance:
1. Where this page is being generated from
I’m not seeing an obvious location in the CMS where this tag page itself is managed or configured.
2. Why the entries appear to be very old
The posts associated with this tag seem outdated, and I’m unsure whether:
• the tag is no longer being applied to newer posts, or
• the page is pulling from a legacy or deprecated content source.
3. How to modify or curate this page
Specifically:
• How do I update which posts appear under this tag?
• Can older posts be removed from this tag without deleting the posts themselves?
• Is it possible to control the visibility or ordering of content on this tag page?

My goal is to ensure this tag page accurately reflects current content and doesn’t surface outdated material unintentionally.

Any clarification on where this is managed and the recommended way to update it would be very helpful.

Thank you in advance for your assistance.

— Jerry