Search Results for 'composer'

Hi,
Edit the homepage using tagDiv Composer https://i.imgur.com/LqZci0B.png, select the mobile viewport – https://i.imgur.com/irzI2i7.png ,then the menu and change the title – https://i.imgur.com/EQOebz7.png
Thank you!

Hi,
That’s correct. This is code that will be rendered by tagDiv Composer and the Cloud Library, so it won’t appear in the WordPress editor as it does on the frontend and theme builder when you edit it.

Hi, Yes, this can be done for each viewport in part using the tagDiv Composer
– https://tagdiv.com/tagdiv-composer-page-builder-basics/ – https://i.imgur.com/uhPYeAZ.png – https://i.imgur.com/dpbDfIK.png

Hi,

Yes, a page made with tagDiv Composer allows you to copy elements from one page to another. To do this, in Composer, right-click on the element and select Copy. On the new page, select an element that will be above or below where you want to paste it, then right-click and choose where to paste the copied element.

You can also save the element in tagDiv Composer and then drag it as a new element on any page.
https://tagdiv.com/right-click-menu-tagdiv-composer/
https://tagdiv.com/how-to-use-the-new-copy-paste-tools-for-elements/
https://tagdiv.com/copy-paste-style-feature/

Hi EDMSU,
Edit the homepage using tagDig Composer, then go down to the section with the review: https://i.imgur.com/D2zQkFF.png
– You will see a Raw HTML element—select it: https://i.imgur.com/Ekft2Zf.png
– Expand the editor and comment out that code.
After that, the images in the first view will appear one above the other. Then select the crown image element and delete it. After that, go back to the review section and uncomment the code.

Hi,
If you have the latest version and you face a critical error when using the search, it will be need to replace the current theme plugin tagDiv Composer with the one from here – https://cdn.tagdiv.com/wp-content/uploads/2025/11/td-composerfix.zip
Thank you!

Hi,

1. I believe there has been a misunderstanding regarding the cloud templates.

In the General tab, you will find the standard cloud templates for a blog. These include templates for the header, footer, single post, category, tag, author, date, 404, attachment, and search pages.

The template that can be used for a single doctor is available under the Single Article cloud templates (see: https://i.imgur.com/xNZUSoK.png). However, the template you are trying to use is a Custom Post Type (CPT) template. CPT templates cannot be applied to regular single posts; they can only be used for their respective CPTs. Additionally, this CPT template is not part of the cloud templates—it was provided in my previous reply—and, as mentioned, it works only for CPTs, not for standard posts or articles.

If you want your regular posts to have a layout similar to the CPT layout, you will need to recreate it manually using the Theme Builder in tagDiv Composer. If custom fields are required, you can use the ACF plugin to achieve this.

To copy and paste the CPT template I provided, please edit a single under the Custom post type – https://i.imgur.com/ZvgMAhV.png hover over the 3 dots and click on “edit” https://imgur.com/NlMnH9L. After that, replace the code with the one from here https://cdn.tagdiv.com/wp-content/uploads/2026/01/Custom-Post-Type-CPT-Doctors-PRO.txt

2. As mentioned above, there is a misunderstanding. I believe this comes from trying to combine multiple prebuilt templates without fully understanding how the theme works. It seems there may be some confusion about core concepts such as what a post is, what a CPT (Custom Post Type) is, and the difference between categories and taxonomies, including how they are configured and how they are meant to function.
The section you are referring to (https://i.imgur.com/UrNPZOE.png) is displaying the Doctors CPT, and its layout is provided by the Doctors PRO Plugin. This plugin can be installed from Newspaper > Plugins > Dedicated Plugins for Prebuilt Websites (https://i.imgur.com/6eVC20P.png). Once the plugin is installed, you can use Flex Block X to select and display that module (https://i.imgur.com/nZpalQh.png). However, since the plugin creates the module using predefined code, we recommend creating your own custom module using the Module Builder, and then displaying it via the Flex Block Builder.
By doing this, you gain full control over the module’s layout and settings. For example, if you want to add an “Age” field, you can create a custom field using a plugin such as ACF, and then display it in your custom module using the Custom Field element.

Thank you!

Hi,
When you remove elements from tagDiv Composer but they are not reflected on the frontend, it may be due to the cache or object cache. Make sure that after you make the changes in tagDiv Composer, you also clear all the cache.
I hope this will help you!

Hi,

This situation is related to an ad blocker. Please try using a different browser and make sure that no ad-blocking extensions are enabled. Normally, the frontend and the Composer view should look the same.

Also, after making all changes, please ensure that the cache is cleared.
If you’d like, I can remove the ad banners for you. To proceed, please contact us via email at contact@tagdiv.com and provide temporary wp-admin access.

Hi,
You can edit the theme files, the problem is that you need to do this after each theme update because the code from that file can not be set in a child theme.
The file that should be edited is wp-content/plugins/td-composer/legacy/common/wp_booster/td_data_source.php and the code is around lines 519-525 – https://i.imgur.com/dOIfAbv.png is starts with case ‘random_7_day’:
Thank you!

Hi,

In most cases, this issue is caused by a shortcode that is not compatible with our theme or by a plugin conflict. As a result, after configuring the page or Cloud Template with tagDiv Composer and saving it, you may encounter this error the next time you attempt to edit it.

If the issue occurs only on a specific page or Cloud Template (including the header or footer), it is likely related to certain settings or shortcodes used there. You can test this by temporarily changing the header or footer to see if the problem persists. In many cases, the issue can be resolved by restoring a previous version using page revisions: https://wordpress.com/support/page-post-revisions/

Thank you!

Hi,

Most of the time, the problem is from a shortcode that is not compatible with our theme or a plugin conflict; therefore, after you set it with tagDiv Composer and save the page/cloud template, the next time you try to edit it, you’ll get that error.
If is only for one page or a cloud template (it can be on the header or footer, you can change them for tests and see if the problem persists), this is from some settings/shortcodes set on it and it can be fixed using the page revision https://wordpress.com/support/page-post-revisions/

Thank you!

Please provide some screenshots from tagDiv Composer, it should be something like this – https://i.imgur.com/uqbhTKH.png https://i.imgur.com/HKEPdek.png or just select the block and delete it (use the right click on it and select the delete option from the right menu). You can add the ad box element later, where you want on your website.

Hi,

In most cases, this issue is caused by a shortcode that is not compatible with our theme or by a plugin conflict. As a result, after setting the page or Cloud Template with tagDiv Composer and saving it, you may encounter this error the next time you try to edit it.

If the problem occurs only on a specific page or Cloud Template (including the header or footer), it is likely related to settings or shortcodes used there. You can test this by temporarily changing the header or footer to see if the issue persists. In many cases, it can be resolved by restoring a previous version using page revisions: https://wordpress.com/support/page-post-revisions/

Thank you!