Search Results for 'composer'

Hi,
how can remove “/* custom css – generated by TagDiv Composer */” from HTML code?

Hello
I have created a custom post type and created a specific header and footer for single posts, taxonomy term and archive templates for this cpt in tagdiv composer. Whilst I am able to change the footer and headers for all of these in Website Manager, when I view the archive page it is using the global header and footer. The category term and single post pages are okay and display the specific headers and footers I set up for them.

How do I override the global header and footer for archive templates?

Hi there,

after yeras of using TagDiv I want to change to Elementor. After I deactivated the plugins:

– tagDiv Cloud Library
– tagDiv Composer
– tagDiv Social Counter
– tagDiv Standard Pack

I still see a “Newspaper” menu item on the left admin bar?!

Where does his come form, how can I make sure that no “TagDiv Newspaper” is running anymore? And is there a good way to delete database data that is form tagdiv left in the database?

Kind regards, Martin

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.