Search Results for 'child theme'

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,

brixtonblog.com

All the widgets blocks on the site are locked – a small padlock icon appears next to them in the list view
The contents of the blocks can be unlocked, but not the blocks themselves
I have tried various things, including:
switching back to classic widgets
deactivating all plug-ins/all plug-ins except the tag div ones that control the theme, both by deactivating via the theme and by disabling them via SFTP
switching the site to a standard WordPress site temporarily (Twenty Twenty one)
switching from a child theme to the main Newspaper theme
pausing Cloudflare
updated to WordPress 6.9
checking permissions
None of these had any effect
The widget screen also takes a very long time to open – which is why I want to delete most of them … but cannot.

Hello tagDiv Support Team,

I am experiencing a critical error on my website (running the Newspaper theme) specifically when performing a search. The rest of the site functions normally, but submitting a search query results in a “Critical Error” message.

Error Log Details:
I have enabled WP_DEBUG and identified the following fatal error:
Fatal error: Uncaught TypeError: Cannot access offset of type array on array in …/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php:1196

Stack Trace Summary:

#0 td_util::get_template_id(Object(WP_Post)) called at td_util.php(340)
#1 td_util::check_header() called at td_wp_booster_functions.php(513)

The error seems to originate during the wp_enqueue_scripts and wp_head actions when the theme tries to determine the template ID for the search results page.

Environment Information:

Theme: Newspaper (using a child theme)

Plugin: tagDiv Composer

PHP Version: 8.4.13 (The error appeared after upgrading PHP versions)

WordPress Version: 3.9

The error only occurs on the search results page.

Is this a known compatibility issue with PHP 8.x and the current version of the tagDiv Composer? Could you please advise if there is a specific patch for td_util.php or if a plugin update is required to handle the array type-checking more gracefully in PHP 8?

Thank you for your assistance.

Website URL: madtrash.com

Hola, tengo la siguiente categoría: https://dataconurbano.net/category/categoria-prueba/

Quiero que se muestren 6 noticias por página y un paginador normal (numeros en la parte de abajo)

Hay forma de hacerlo desde el theme panel?

—

Buscando en internet encontré este codigo para functions.php del child theme. Me muestra el paginador y la cantidad correcta de noticias, pero en la página 2 me dice “Error 404”

add_action(‘pre_get_posts’, ‘personalizar_cat_544’);
function personalizar_cat_544($query) {

// Solo en el front-end y en el query principal
if (is_admin() || !$query->is_main_query()) {
return;
}

// Aplica SOLO en la categoría 544
if ($query->is_category(544)) {

// Cantidad de posts a mostrar
$query->set(‘posts_per_page’, 6);

// Asegurar que la paginación funcione correctamente
if ( get_query_var(‘paged’) ) {
$query->set(‘paged’, get_query_var(‘paged’));
}
}
}

Esa categoría tiene seteado:
Category template: Style 2
Category top posts style: Grid Full 1 (por css achiqué el tamaño de la imagen para que coincida con el container centrado)
ARTICLE DISPLAY VIEW: M10
Pagination style: Normal Pagination

Agradezco si me pueden ayudar

Muchas gracias

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!

Hi there,

I recently Updated Newspaper theme. After update, i tested – all worked, besides search that gave an empty white screen. Doing some troubleshooting I noticed in console that an error 500 was thrown.

Looking at logs, i see this:

[21-Nov-2025 10:37:05 UTC] PHP Fatal error: Uncaught TypeError: Illegal offset type in /var/www/html/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php:1196
Stack trace:
#0 /var/www/html/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php(340): td_util::get_template_id()
#1 /var/www/html/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php(513): td_util::check_header()
#2 /var/www/html/public_html/wp-includes/class-wp-hook.php(324): td_load_css_fonts()
#3 /var/www/html/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#4 /var/www/html/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#5 /var/www/html/public_html/wp-includes/script-loader.php(2299): do_action()
#6 /var/www/html/public_html/wp-includes/class-wp-hook.php(324): wp_enqueue_scripts()
#7 /var/www/html/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#8 /var/www/html/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#9 /var/www/html/public_html/wp-includes/general-template.php(3192): do_action()
#10 /var/www/html/public_html/wp-content/plugins/td-standard-pack/Newspaper/header.php(11): wp_head()
#11 /var/www/html/public_html/wp-content/plugins/td-composer/td-composer.php(254): require_once(‘/var/www/html/p…’)
#12 /var/www/html/public_html/wp-includes/class-wp-hook.php(324): {closure}()
#13 /var/www/html/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#14 /var/www/html/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#15 /var/www/html/public_html/wp-content/themes/Newspaper/header.php(2): do_action()
#16 /var/www/html/public_html/wp-includes/template.php(810): require_once(‘/var/www/html/p…’)
#17 /var/www/html/public_html/wp-includes/template.php(745): load_template()
#18 /var/www/html/public_html/wp-includes/general-template.php(48): locate_template()
#19 /var/www/html/public_html/wp-content/themes/Newspaper-child/search.php(1): get_header()
#20 /var/www/html/public_html/wp-includes/template-loader.php(106): include(‘/var/www/html/p…’)
#21 /var/www/html/public_html/wp-blog-header.php(19): require_once(‘/var/www/html/p…’)
#22 /var/www/html/public_html/index.php(17): require(‘/var/www/html/p…’)
#23 {main}
thrown in /var/www/html/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1196

Please could you offer me some advice on how to resolve this?

Thanks

Hello Team,

I’m running a local development environment of my production site newspatron.com using Docker.
The site and database were cloned from the live website.
Theme + required plugins are installed and activated:

Newspaper theme 12.7.3 (active)

Newspaper Child theme

td-composer 5.4.2

td-cloud-library 3.9.2

td-standard-pack 2.7.1

td-social-counter latest

Everything is working except:

❌ “Edit with TagDiv Composer” button is missing
❌ TagDiv frontend editor won’t load
⚠ Editing a page only shows a blank white screen

This happens only on the local site.
The live site works perfectly with the same setup.

Other info:

Local URL: http://newspatron.local

Database cloned from Jetpack backup

wp_debug enabled, no TagDiv-specific errors yet

Capabilities granted using WP-CLI

Request:
👉 Please provide any additional required settings, database flags, or licensing constraints needed to restore the TagDiv Composer button and frontend editor in a local dev environment.

Thanks.

Hello! Greetings
📌 Problem:
There is a huge blank/empty space appearing right after the main homepage blocks.
You can see this in the attached screenshot (marked as “EMPTY”).
This space disrupts the visual flow and makes it harder for users to view the content below.

🧩 What I’ve tried:

I checked all widgets (especially in the homepage builder area)

I reviewed page settings and layout options

No additional widgets, content, or padding seem responsible

❓ Questions:

What is likely causing this large space?

How can I remove or reduce it while keeping the current homepage structure?

If any additional information or admin access is required to help investigate, please let me know — I’d be happy to assist.

Thank you again for your great work. I sincerely appreciate your support.

Kind regards,
Claudio Souza
📌 Problem:
There is a very large blank/empty space appearing right after the main homepage blocks.
You can see this in the attached screenshot (marked as “EMPTY”).
This space disrupts the visual flow and makes it harder for users to view the content below.

🧩 What I’ve Tried:

I checked all widgets (especially in the homepage builder area)

I reviewed page settings and layout options

No additional widgets, content, or padding seem responsible

❓ Questions:

What is likely causing this large empty space?

How can I remove or reduce it while keeping the current homepage structure?

If any additional information or admin access is required to help investigate, please let me know — I’d be happy to assist.

Thank you again for your great work. I really appreciate your support.

Kind regards,
Cláudio Souza
https://soropositivo.orgBlog soropositivo. I have to say. Your theme it’s light years ahead “Soledad” I was a Soledad user and have almost anything good to talk about the experience. However, it looks like yours the comes without child the and that is very precious for me. If I am mistaken, please, show me where I may find it or, otherwise, kindly teach me how to create on.
With my best regards

Hello everyone!
I use mainwp on my sites to update plugins and themes faster, as I have over 20 of them.
Recently, during a mass update of my theme from version 12.7.1 to 12.7.3, errors occurred. I selected 15 of my sites and ran the update through mainwp. The theme updated correctly on five sites, but not on the other ten (an X appeared next to the sites, indicating the update failed). I then selected 10 sites and tried updating again. The second time, three sites updated correctly, but the rest failed. I repeated this process four times. After updating the theme on all my sites, I discovered that the theme was completely broken on ten of my sites (the layout wasn’t working correctly, the settings in the Theme Panel were lost, and the theme couldn’t be activated). After restoring the theme, more problems arose: social media icons disappeared in the news feed, and the code in the Theme Panel that connects the metrics to the site was missing. Please take a look at this plugin, mainwp. This plugin has an administrative section, and sites will then be connected to it via the mainwp child plugin.

I have a very old theme active v8.1
It doesnt have the update button as you show in doc https://forum.tagdiv.com/how-to-update-the-theme-2/
I also have some custom code in my theme child.
When I try to upload the latest theme to the customizer I get an error when my child theme is active.
Please advise

Dear Support Team,

we are using the Newspaper 12.7.3 theme and have noticed a category filtering issue with the Flex Loop Builder module.

The Flex Loop only displays posts if the parent category is explicitly selected on the post – even when the post is correctly assigned to a child category.

In our case, posts that are assigned only to a child category are not shown in the Flex Loop, unless the parent category is also manually selected. This differs from the behavior of standard loops (e.g., Posts Loop), which correctly display posts based on the selected child category, regardless of whether the parent is also assigned.

This behavior is inconsistent and leads to missing posts in the Flex Loop that are correctly categorized under the child category.

Can you confirm whether this is the intended behavior or a bug?

If this is the intended logic, can you please explain why the parent category must be selected explicitly, even when the child category is already assigned?

And is there any way to configure the Flex Loop Builder to behave like the standard loop and include posts assigned only to the selected child category?

Best regards,

How to remove “My Woo Subscriptions and its sub categories” from my woo menu, from my newspaper theme?
Refer the image: https://prnt.sc/5iZy1nLpeFKW
I want to do 2 things, remove the my woo subscription box completely and change the “my woo account” to just “my account”.

I tried some Live CSS, i was able to remove only the subscriptions and and account details section, inside the the whole “my woo subscription section”, but was unable to change “my woo account” to “my account”
Refer to the screenshot : https://prnt.sc/zGtg8FuPscbl

website link: https://jeevahfoods.com/

Here is the CSS:
/*
* — REMOVE THE SUBSCRIPTION SECTION —
* This is the complete, combined code.
*/

/* Hides the “Account details” link */
a[href*=”?account_details”] {
display: none !important;
}

/* Hides the “Subscriptions” link */
a[href*=”?subscriptions”] {
display: none !important;
}

/* * — Hides the “My subscription account” HEADING —
* This is the new set of rules to find the stubborn heading.
*/

/* Rule 1: Target common tagDiv heading classes */
.td-account-links .tds-woo-sub-heading,
.td-woo-acc-menu .tds-woo-sub-heading,
.td-woo-acc-menu .tds-account-sub-header {
display: none !important;
}

/* Rule 2: Target any span that is a direct child of a list item (a common way to make a heading) */
.td-woo-acc-menu li > span {
display: none !important;
}