Search Results for 'td composer'

Seems I am getting an error on the backend when I attempt to “preview a post”.

I see this above the header. Has anyone else experienced this error? Please note the xxx after home is only to hide the folder site name.

Again this error does not appear on the home page to visitors but we see it at the backend. Please help

wp_booster error:
td_api_base::mark_used_on_page : a component with the ID: single_template_13 is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: file is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
The path of the single_template_13 template not found. Did you disable a tagDiv plugin?
/home/xxxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: bg_use_featured_image_as_background is not set.
/home/xxxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: bg_disable_background is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: bg_box_layout_config is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

Seems I am getting an error on the backend when I attempt to “preview a post”.

I see this above the header. Has anyone else experienced this error? Please note the xxx after home is only to hide the folder site name.

Again this error does not appear on the home page to visitors but we see it at the backend. Please help

wp_booster error:
td_api_base::mark_used_on_page : a component with the ID: single_template_13 is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: file is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
The path of the single_template_13 template not found. Did you disable a tagDiv plugin?
/home/xxxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: bg_use_featured_image_as_background is not set.
/home/xxxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: bg_disable_background is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

wp_booster error:
td_api_base::get_key : a component with the ID: single_template_13 Key: bg_box_layout_config is not set.
/home/xxx/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Display backtrace

After an update to Version: 12.6.5, the website is only showing text where blocks are, i.e. [td_block_11 category_id=”57″]

I deleted and reinstalled the tagDiv Composer and tagDiv Cloud Library, but no change. They are both active in the tagDiv theme plugins.

What am I missing?

https://glasair-owners.com/

Below error occured and afterwords by entire site went down. I had to restore an old backup.

Howdy!

WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, tagDiv Composer.

First, visit your website (https://website.com/) and check for any visible issues. Next, visit the page where the error was caught (https://website.com/wp-login.php) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

https://website.com/wp-login.php?action=enter_recovery_mode&rm_token=55EWVI9HiM0RedsRDTV2NB&rm_key=L14gEdVaN69t7leSM2QCRc

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.5
Active theme: Newspaper (version 12.6.5)
Current plugin: tagDiv Composer (version 4.8 | built on 11.03.2024 11:04)
PHP version 8.1.27

Error Details
=============
An error of type E_ERROR was caused in line 49 of the file /home/u238372/domains/website.com/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php. Error message: Uncaught Error: Failed opening required ‘td_block.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/u238372/domains/website.com/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php:49
Stack trace:
#0 /home/u238372/domains/website.com/public_html/wp-content/plugins/td-composer/legacy/Newspaper/functions.php(21): require_once()
#1 /home/u238372/domains/website.com/public_html/wp-content/plugins/td-composer/td-composer.php(191): require_once(‘/home/u238372…’)
#2 /home/u238372/domains/website.com/public_html/wp-includes/class-wp-hook.php(324): {closure}()
#3 /home/u238372/domains/website.com/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#4 /home/u238372/domains/website.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#5 /home/u238372/domains/website.com/public_html/wp-content/themes/Newspaper/includes/wp-booster/tagdiv-wp-booster-functions.php(3): do_action()
#6 /home/u238372/domains/website.com/public_html/wp-content/themes/Newspaper/functions.php(19): require_once(‘/home/u238372…’)
#7 /home/u238372/domains/website.com/public_html/wp-settings.php(663): include(‘/home/u238372…’)
#8 /home/u238372/domains/website.com/public_html/wp-config.php(104): require_once(‘/home/u238372…’)
#9 /home/u238372/domains/website.com/public_html/wp-load.php(50): require_once(‘/home/u238372…’)
#10 /home/u238372/domains/website.com/public_html/wp-login.php(12): require(‘/home/u238372…’)
#11 {main}
thrown

hi on my category website NewsPoint.bg on the footer i have this error:

`wp_booster error:
td_api_base::get_default_component_id : no component of type td_api_category_template . Wp booster tried to get
the default component (the first registered component) but there are no components registered.
/home/newspoin/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Array
(
[0] => Array
(
[file] => /home/newspoin/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php
[line] => 117
[function] => error
[class] => td_util
[type] => ::
[args] => Array
(
[0] => /home/newspoin/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php
[1] => td_api_base::get_default_component_id : no component of type td_api_category_template . Wp booster tried to get
the default component (the first registered component) but there are no components registered.
)

)

can you help me to solve this
best regards
GEORGI

Hello, for your information there is a Vulnerability in the tagDiv Composer plugin

CSRF to XSS vulnerability discovered by Truoc Phan (Patchstack Alliance) in WordPress Plugin tagDiv Compose

https://patchstack.com/database/vulnerability/td-composer/wordpress-tagdiv-composer-plugin-4-1-csrf-to-xss-vulnerability?_a_id=110
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/td-composer/tagdiv-composer-41-cross-site-request-forgery-to-cross-site-scripting
could you correct ?

Hi,
I am getting nasty errors from td_api.php

You can see both errors here: https://www.languagemagazine.com/job/spanish-and-english-dual-immersion-classroom-teacher-kindergarten-through-8th-grade-spanish-language-classroom-teacher-high-school/#

PHP version is: PHP 8.1.27
Newspaper version is: 12.6.5

In case you can’t click the link above, this are the two errors:

wp_booster error:
td_api_base::mark_used_on_page : a component with the ID: tdb_template_143296 is not set.
/home/language/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

wp_booster error:
td_api_base::get_key : a component with the ID: tdb_template_143296 Key: exclude_ad_content_top is not set.
/home/language/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Warning: Array to string conversion in /wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php on line 675

Line 675 is:
$unique_google_fonts_ids = array_unique( array_merge( $unique_google_fonts_ids, $extra_google_fonts_ids ) );

its called: // remove duplicated font ids

Site is:
https://lchfdieta.pl/

This is getting ridiculous now. We’ve been having this issue update after update and it’s never resolved.

When building a new page, we are getting this error on creating a mobile page.

For desktop, it works okay but we can’t create or edit mobile pages.

We tried:
– Giving your support access to our website and they disabled all plugins on the production website without asking
– Disabling the plugins on our own but the problem persists.
– Creating a new header and footer to ensure they are not the problem. (They are not)
– Changing PHP versions
– Using a Newspaper instead of our child theme.
– Disabling Cloudflare and caching plugins to avoid conflicts.

Nothing works. We are getting error after error after error.

On the mobile page editor, we keep getting Delete text injected on top of the page. I have no idea why and where that is injected.

I’ve found it in obscure, minimized files js_files_for_widgets.min.js and js_files_for_wrapper.min.js

what does it do? Is it possible that is the cause of the problem?

I repeat I’ve gone through your page TD Composer not working and nothing helped.

I have an issue when changing Blog post templates in the Theme Panel as well as on the Edit Blog Artikle Page.
Ican only use “Single Post Template Personal Trainer”. I dont even know where that Template came from, i did not dowload it from the cloud. When i change the template, i get the following error:

Warning: Array to string conversion in td_util.php on line 1711
Line1711: ” $extra_google_fonts_ids = array_unique( array_merge( $extra_google_fonts_ids, $google_fonts_ids ) );”

Warning: Array to string conversion in td_wp_booster_functions.php on line 675
Line 675: ” $unique_google_fonts_ids = array_unique( array_merge( $unique_google_fonts_ids, $extra_google_fonts_ids ) );”

Since it has something to do with google fonts, i disabled all Plugins. I also disabled local google fonts. Then i uninstalled TagDiv Composer und reinstalled it again.

Same error. PHP Version is 8.1.27

Compatibility error with WPRM plugin. Error:

Warning: Array to string conversion in /wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1711

There’s a lots of request made to the SQL Database requested at the same time thus rate limiting issue is happening on the site.

https://downloads.intercomcdn.com/i/o/998988044/d3c2ccb5d4ea63956a683f0c/Screenshot+2024-03-22+at+10_55_47%E2%80%AFAM.png

WordPress database error MySQL server has gone away for query SELECT post_id, meta_value FROM 3cEugTXx_postmeta WHERE meta_key = ‘_wp_attached_file’ AND meta_value = ‘https://noticiasnrt.mystagingwebsite.com/wp-content/uploads/2022/01/BackS-300×169-1.png’ made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, cnfp_template_redirect, include(‘/plugins/colorlib-404-customizer/includes/colorlib-template.php’), get_header, locate_template, load_template, require_once(‘/themes/Newspaper/header.php’), do_action(‘tdc_header’), WP_Hook->do_action, WP_Hook->apply_filters, {closure}, require_once(‘/plugins/td-composer/legacy/Newspaper/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, td_background->wp_head_hook_background_logic, attachment_url_to_postid

WordPress database error MySQL server has gone away for query SELECT post_id, meta_value FROM 3cEugTXx_postmeta WHERE meta_key = ‘_wp_attached_file’ AND meta_value = ‘https://noticiasnrt.mystagingwebsite.com/wp-content/uploads/2022/01/BackS-300×169-1.png’ made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/plugins/td-cloud-library/wp_templates/tdb_view_single.php’), get_header, locate_template, load_template, require_once(‘/themes/Newspaper/header.php’), do_action(‘tdc_header’), WP_Hook->do_action, WP_Hook->apply_filters, {closure}, require_once(‘/plugins/td-composer/legacy/Newspaper/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, td_background->wp_head_hook_background_logic, attachment_url_to_postid

One thing we’ve identified is that the Newspaper theme is making some very lengthy and expensive database queries that slow down page loads and may be contributing to elevated SQL CPU usage.
For example, on the homepage the Newspaper theme runs the following code.
require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/plugins/td-composer/legacy/Newspaper/page.php’), get_header, locate_template, load_template, require_once(‘/themes/Newspaper/header.php’), do_action(‘tdc_header’), WP_Hook->do_action, WP_Hook->apply_filters, {closure}, require_once(‘/plugins/td-composer/legacy/Newspaper/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, td_background->wp_head_hook_background_logic, attachment_url_to_postid
Which also executes the following query.
SELECT post_id, meta_value FROM 3cEugTXx_postmeta WHERE meta_key = ‘_wp_attached_file’ AND meta_value = ‘https://noticiasnrt.com/wp-content/uploads/2022/01/BackS-300×169-1.png’
This is a very expensive and lengthy query, especially on a site of this size.
In some cases, it might take over 2 seconds for that code and query to complete because it is not optimized and likely doesn’t have database indexes that would help speed it up.

it seems that the problem originates from the td-composer plugin. Would it be alright if I deactivate it temporarily?
PHP Fatal error: Uncaught Error: Failed opening required ‘/srv/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_page_views.php’ (include_path=’/:.’) in /wordpress/core/6.4.3/wp-includes/template.php:790 Stack trace: #0 /srv/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_autoload_classes.php(42): load_template(‘/srv/htdocs/wp-…’, true) #1 /srv/htdocs/wp-content/plugins/td-cloud-library/wp_templates/tdb_view_single.php(111): td_autoload_classes->loading_classes(‘td_page_views’) #2 /wordpress/core/6.4.3/wp-includes/template-loader.php(106): include(‘/srv/htdocs/wp-…’) #3 /wordpress/core/6.4.3/wp-blog-header.php(19): require_once(‘/wordpress/core…’) #4 /wordpress/core/6.4.3/index.php(17): require(‘/wordpress/core…’) #5 {main} thrown in /wordpress/core/6.4.3/wp-includes/template.php on line 790

Greetings.
Probing one of our websites, running Newspaper 12.6.5 with WordPress 6.4.3, we have found that there is a security vulnerability related to requests to wp-admin/admin-ajax.php with a td_ajax_loop action in which the property moduleId is altered with malicious content.

This vulnerability has seemingly been reported previously as CVE-2022-2627, but the report mentions that it has been fixed in version 12 of the theme which is not currently true.

Here’s an example on your own demo site:

The request:

curl -i -s -k -X $'POST' -H $'Host: demo.tagdiv.com' -H $'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0' -H $'Content-Length: 119' -H $'Content-Type: application/x-www-form-urlencoded' --data-binary $'action=td_ajax_loop&loopState[moduleId]=--><form><math><img+src=1><mtext></form><!--&loopState[server_reply_html_data]=' $'https://demo.tagdiv.com/newspaper_pro/wp-admin/admin-ajax.php?td_theme_name=Newspaper'

The (truncated) response:

HTTP/2 200
...
content-type: text/html; charset=UTF-8
...

...

Notice how the parameters sent via ajax are returned to the client unescaped, in particular the form with an img tag inside. And because HTML tags are not being properly escaped, combined with the fact that the Content-Type of the response is text/html, this results in the malformed request being reflected towards the client and rendered as HTML, which can be abused by a malicious actor.

Your error message handling attempts to safeguard this by adding comment indicators around the content, but that can be trivially manipulated as per the example above.

A possible solution:

In your td-composer plugin, the function error of the class td_util is responsible for dealing with this content. The following line:

echo '<strong class="td-wp-booster-title">wp_booster error:</strong><br>' . $message;

Can be changed to the following alternative, sidestepping the issue cleanly:

echo '<strong class="td-wp-booster-title">wp_booster error:</strong><br>' . esc_html($message);

Hope to see this resolved in a future update.
Best regards.

Hello,

https://www.lotus-tahiti.com has been compromised due to old version of newspaper theme and its td-composer plugin.

Could you please help me to update the theme (9.7.2) ?

Regards,