Search Results for 'remove tag from post'

We have issues with saving the main category (when more than one are selected) for the posts.
It lets you chose the main category but it doesn’t save it.

Wordpress v6.9
Newspaper v12.7.3

Some AI debugging info:

TagDiv themes (Newspaper/Newsmag) implement their own “Primary Category” logic using td_primary_cat meta.
When WP versions change (especially 6.7+ → 6.8+ / 6.9), the taxonomy metabox structure changed, breaking older JS that TagDiv uses to capture the radio button selection.

Common causes:

1. JavaScript conflict or deprecation
The TagDiv metabox JS that listens for the “Make Term Primary” click fails to run.
WP changed DOM structure inside the metabox.

2. Theme or plugin outdated
Version 12.7.3 of Newspaper is known to have primary category issues with newer WP versions.

3. Autosave overwriting meta
If Gutenberg autosave is active, it can remove td_primary_cat before final save.

4. REST API conflicts
Security plugins or caching layers (Cloudflare, LiteSpeed, WP Rocket) may block the POST request saving meta.

Can I get some help with it?

It started last week. Let me know if you need more info or details.
thx for your fast reply since this is an urgent matter for our website.

Hello,

I know that removing author from posts inside the post or in the homepage is doable through the editwithtagdiv composer.
the problem is i am talking about this ( td-post-author-name )

html code :

<div class=”td-editor-date”>

<span class=”td-post-author-name”>…<span>

</span> </span> <span class=”td-post-date”</span> </div>

it is in the features section , or below in the middle of the page where it is 1 complete element which holds the article title and image and some text.

if i click on editwith tagdiv composer and try to edit these elements, it is not doable, since all of the things inside that element is 1 row and 1 columun . means i can’t chose to remove the author , or the date, or the image or the title..

I hope you understand where is the problem.

Do you have a solution for that, or I need to edit the html / php ?

Thank you

I am experiencing a critical issue with the Featured Image display on our Single Post Template.

The image is being cropped at the top and bottom with the Single Post Bg Featured Image, (e.g., faces are cut off) because the container height is fixed and incompatible with the image’s aspect ratio.

Also using Single Post Featured Image with custom CSS (see below) does not contain the image but cuts off below half of image:
.tdb_single_featured_image img.entry-thumb {
object-fit: contain !important;
width: 100% !important;
height: auto !important;
max-width: 100% !important;
}
.tdb_single_featured_image {
max-height: 500px !important;
overflow: hidden;
}

Good to understand that all images are served through the plugin WP Media Folder Cloud add-on from Google Drive, all images are resized offline with XN-Resize, before uploaded in media library folder in WPMF Google Drive, to be constrained to max 1400x600px size. So images have no seperate thumbnails created in Google Drive. The are coded as thumbnails automaticly inside Big Grid and Flex blocks.

Technical Cause and Conflict

Fixed Height Conflict: The core problem lies in the theme block used to display the header image. Specifically, the tdb_single_bg_featured_image block (which was previously used, or its properties are still inherited) has a hard-coded default height value (600px) that cannot be removed or set to ‘auto’ in the TagDiv Composer settings. This fixed height creates an inflexible CSS container.

Rendering Override: The theme’s rendering engine (or the WP Media Folder Cloud Add-on) applies a height constraint via an inline style or theme JavaScript (JS) that executes with the highest priority, forcing the image to fit the limited height while applying overflow: hidden.

CSS Failure: All attempts to override this constraint using standard CSS (Child Theme, Customizer, and direct Block CSS injection) fail to work against the theme’s rendering logic.

Desired Outcome and Required Solution

The required behavior is the precise inverse of the current rendering. The image must behave exactly like the CSS rule object-fit: contain.

Goal: The image must scale down proportionally based on the available width of the column, ensuring the entire image (full height and width) is visible within the container without any cropping. The container’s height must then dynamically adjust (height: auto) to accommodate the image’s resulting proportional height.

I require assistance in disabling the internal hard-coded height constraint (600px) on the Featured Image block within the TagDiv Composer’s source files, as external CSS solutions are being ignored, or have a workaround presented with custom code that can do the job.

Since Single Post Bg Featured Image is a background image this is difficult. The element is placed inside Single Post Featured Image, to be able to show caption. In the Extra Class of CSS of Single Post Featured Image we no have placed remove-image. When showing the image in this element it only shows with setting 485×360 but then doubles in height strangly.

Any help and solution in this would be much appreciated!

Hello tagDiv Support Team,

I need to restrict access to Cloud Templates for users with the Editor role on my Newspaper theme website. Currently, editors can still see and edit Cloud Templates in the backend, which I need to prevent.

What I’ve tried:
– Installed “User Role Editor” plugin and adjusted capabilities
– Added custom code to functions.php to remove menu items and capabilities
– None of these solutions have successfully hidden or blocked access to Cloud Templates

What I need:
– Only Administrators should be able to access, view, and edit Cloud Templates
– Editors should be completely blocked from accessing Cloud Templates (both in the admin menu and via direct URL access)
– Editors should still be able to create and edit regular posts and pages

Questions:
1. Is there a built-in setting in Newspaper theme to restrict Cloud Templates access by user role?
2. What is the correct capability or hook to use to prevent editors from accessing the Cloud Templates custom post type (tdb_templates)?
3. Can you provide the recommended code solution to implement this restriction?

Theme Details:
– Theme: Newspaper
– Plugins: tagDiv Composer, tagDiv Cloud Library (both active)
– WordPress Version: 6.8.3
– Theme Version: 12.7.3

Thank you for your assistance!

Best regards

Hi I’m using the Urban Observer demo from the Newspaper (tagDiv) theme on my site. Everything was working perfectly until I renamed the “Featured” category to “Education” — and that’s when my entire top section broke.

After renaming (and later deleting) the “Featured” category, the website title and top menu (About, Contact, My Account, etc.) disappeared, leaving only my ad banner visible. The homepage layout also changed, and the header template stopped displaying correctly.

I’ve since restored the site from a backup to an earlier version but the issue persists and I can’t seem to be able to get the old header which contains the website name and other information.

It seems that the Featured category was tied to a specific internal post or placeholder that powered the homepage grid and header layout. When I renamed or removed it, the theme lost its reference point.

Can anyone confirm if:
1. The “Featured” category is hard-coded into Urban Observer’s layout?
2. There’s a proper way to rename or replace it without breaking the site?
3. Creating a placeholder post under a new category can fix the issue without a full restore?

Thanks in advance — I love this theme, but this caught me off guard and I’d appreciate some insight before I touch anything again.

Hi TagDiv Team,

Like some other users, I’m consistently getting the following error when editing new pages or the homepage (but not posts): Error at zones: 6(models): 0(dom) “The model does not match the content. Current state has involved an issue.”

This even happens immediately after I download one of your pre-built templates—even before adding any shortcodes.

What I discovered:

After some testing, I found that if I use the “Post Type Switcher” plugin to change the page type (in the Classic Editor) from Page → Cloud Template, the error in Composer disappears completely!

Once I do that:

I can edit the page in Composer without any errors.

The layout works as expected.

However:

The page is then removed from the Cloud Template list, since it’s technically no longer a “Page” it is a Cloud Template type.

It only displays properly if I access it through a URL like
https://example.com/tdb_templates/news
If I try to access it normally at https://example.com/news, I either get a blank page or a critical error.

My theory

It seems that posts don’t trigger this error because the Theme Panel → Templates section includes a redirect or link definition for posts and single templates. That likely ensures TagDiv Composer initializes the correct “zone” mapping.

For pages and the homepage, there’s no equivalent setting in the Theme Panel, so Composer may be loading the wrong internal model—hence the zone mismatch.

The problem

At the moment, I can’t create or edit any new pages or homepage layouts without this error.
Only posts work normally.

Possible solution idea

If my guess is right, perhaps the Composer needs a way to assign a Cloud Template mapping (like the Post templates) for Pages and Homepage in the Theme Panel. That might resolve the zone mismatch entirely.

Do you have any other workaround or insight on this?
It’s currently blocking all new page and homepage creation.

Thanks for your help!

Subject: Excerpt Formatting Issue: Paragraph Breaks <p> tags are being stripped – Newspaper Theme
​Dear tagDiv Support Team,
​I am experiencing a persistent issue with my post excerpts (teasers) when they are displayed on my homepage and archive pages using your theme.
​The Problem:
​The theme is stripping out paragraph breaks (the <p> HTML tag) from the post excerpts, causing the text to be displayed as one single, dense block. This happens regardless of whether the excerpt is:
​Automatically Generated from the post content.
​Manually Entered in the “Excerpt” meta box.
​What I Have Tried (and failed with):
​Custom Excerpt: Writing manual excerpts with HTML tags (e.g., <p>Text</p>). The tags are still removed.
​Advanced Excerpt Plugin: I installed and configured the Advanced Excerpt plugin, ensuring the option to allow HTML tags was active. The theme seems to override the plugin’s functionality, and the paragraph breaks are still removed.
​My Question:
​Is there a specific setting within the Theme Panel, a tagDiv Composer Block setting, or a PHP filter that I can use in a Child Theme’s functions.php file to specifically allow the <p> tag (paragraph breaks) in the post excerpts displayed in your post listing blocks (like Flex Blocks)?
​I only need the paragraph formatting (<p>) to remain intact to improve readability.
​Thank you for your assistance.