Hello!
Please note that a lot has changed since version 7, Nowadays the Newspaper theme is fully built using tagDiv Composer. Editing cloud library templates / demos with Visual composer it is not possible.
Our recommendation is to take a look at some of our video guides and design your website using tagDiv Composer: https://www.youtube.com/user/tagdiv
Thank you!
hi—I’m looking for a way to allow our advertisers to buy space on single post pages, reatricted by category.
we’re self-hosting ads, not using adsense at all (this is a small, local community of galleries, so the focus is really tight).
I have a solid single post format put together, but I’m looking for a way to allow image ad code in tagdiv composer to see what the post’s category is and serve the correct ad in response. is that a thing?
here’s how this is going so far:
I am trying to run update from my admin end. The update is failing with error:
The update process is starting. This process may take a while on some hosts, so please be patient.
Enabling Maintenance mode…
Updating Theme Newspaper (1/1)
Downloading update from https://cloud.tagdiv.com/wp-content/uploads/2021/03/Newspaper.zip…
Unpacking the update…
Installing the latest version…
Removing the old version of the theme…
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Warning: chmod(): Operation not permitted in /usr/share/nginx/html/wp-admin/includes/class-wp-filesystem-direct.php on line 173
Theme update failed.
An error occurred while updating Newspaper: The update cannot be installed because we will be unable to copy some files. This is usually due to inconsistent file permissions. 404.php, images/icons/newspaper.eot, images/icons/newspaper.ttf, images/icons/newspaper.svg, images/icons/newspaper.woff, images/admin-panel/logo-panel.png, images/no-thumb/medium_large.png, images/editor-style/grid-sidebar-desktop.gif, images/editor-style/grid-no-sidebar-desktop.gif, loop-single.php, loop-archive.php, comments.php, search.php, bbpress.php, tag.php, tagdiv-deploy-mode.php, font-newspaper.css, archive.php, attachment.php, sidebar.php, functions.php, author.php, searchform.php, style-woocommerce.css, translation/pt_PT.po, translation/fi.po, translation/tr_TR.mo, translation/nl_NL.mo, translation/el.mo, translation/pt_PT.mo, translation/pl_PL.mo, translation/hi_IN.po, translation/id_ID.mo, translation/ur_IN.po, translation/ru_RU.po, translation/es_ES.mo, translation/el.po, translation/es_ES.po, translation/de_DE.mo, translation/ja.mo, translation/de_DE.po, translation/tr_TR.po, translation/ro_RO.po, translation/th.mo, translation/id_ID.po, translation/ur_IN.mo, translation/th.po, translation/ro_RO.mo, translation/hi_IN.mo, translation/pl_PL.po, translation/mr_IN.mo, translation/default.po, translation/ja.po, translation/default.mo, translation/ta_LK.mo, translation/ta_LK.po, translation/nl_NL.po, translation/ru_RU.mo, translation/mr_IN.po, translation/fi.mo, gutenberg-editor.css, style-bbpress.css, style-buddypress.css, header.php, category.php, woocommerce/archive-product.php, woocommerce/single-product.php, index.php, editor-style.css, loop.php, page.php, footer.php, screenshot.png, includes/tagdiv-page-generator.php, includes/wp-booster/wp-admin/images/font/tagDiv.woff, includes/wp-booster/wp-admin/images/font/tagDiv.ttf, includes/wp-booster/wp-admin/images/font/tagDiv.svg, includes/wp-booster/wp-admin/images/font/tagDiv.eot, includes/wp-booster/wp-admin/images/plugins/tagdiv-amp.png, includes/wp-booster/wp-admin/images/plugins/cloud-templates.jpg, includes/wp-booster/wp-admin/images/plugins/invoice.png, includes/wp-booster/wp-admin/images/plugins/plugins-installed-success.gif, includes/wp-booster/wp-admin/images/plugins/social.png, includes/wp-booster/wp-admin/images/plugins/td-composer.png, includes/wp-booster/wp-admin/images/plugins/tagdiv-newsletter.png, includes/wp-booster/wp-admin/images/plugins/label.png, includes/wp-booster/wp-admin/images/plugins/visual-composer.png, includes/wp-booster/wp-admin/images/plugins/rev-slider.png, includes/wp-booster/wp-admin/images/plugins/mobile.png, includes/wp-booster/wp-admin/images/plugins/standard-pack.jpg, includes/wp-booster/wp-admin/images/plugins/success.jpg, includes/wp-booster/wp-admin/tagdiv-view-welcome.php, includes/wp-booster/wp-admin/css/plugins.less, includes/wp-booster/wp-admin/css/wp-admin.css, includes/wp-booster/wp-admin/css/general.less, includes/wp-booster/wp-admin/css/wp-admin.less, includes/wp-booster/wp-admin/css/welcome.less, includes/wp-booster/wp-admin/plugins/class-tagdiv-current-plugins-deactivation.php, includes/wp-booster/wp-admin/plugins/class-tagdiv-theme-plugins-setup.php, includes/wp-booster/wp-admin/plugins/class-tgm-plugin-activation.php, includes/wp-booster/wp-admin/plugins/class-tagdiv-old-plugins-deactivation.php, includes/wp-booster/wp-admin/tagdiv-view-support.php, includes/wp-booster/wp-admin/js/tagdiv-theme-plugins-setup.js, includes/wp-booster/wp-admin/tagdiv-view-header.php, includes/wp-booster/wp-admin/tagdiv-view-theme-plugins.php, includes/wp-booster/tagdiv-remote-http.php, includes/wp-booster/tagdiv-options.php, includes/wp-booster/tagdiv-admin-notices.php, includes/wp-booster/tagdiv-log.php, includes/wp-booster/tagdiv-util.php, includes/wp-booster/tagdiv-global.php, includes/wp-booster/tagdiv-wp-booster-functions.php, includes/tagdiv-panel-docs.php, includes/js/tagdiv-theme.js, includes/js/tagdiv-theme.min.js, includes/tagdiv-config.php, style.css, single.php
I even tried to chmod entire wp-content directory and its ALL subdirectories to 777 but still the error. Can anyone please help me sort this issue out???
Hi Daniel,
Thank you for reaching out. Can you please be more specific about the empty columns between the blocks? Do you refer to the usage of columns while using the tagDiv Composer page builder? If this is the case, the empty columns appear only in the editing mode and are displayed only if you have a row divided in multiple columns and you don’t add any elements in some of the columns. This will leave the columns empty and the message “empty column” will be displayed. However, this can only be seen in the editing mode. If you need help with this, please let us know and we will guide you through.
The WPBackery page builder cannot be used along with the tagDiv Composer. They are not compatible. I’m sorry for this inconvenience! You can use the WPBackery plugin if you want. But you cannot use the tagDiv Cloud Library nor the PRO demos, as well as other tools that include the Header Builder, Footer Manager, and more, because the functionality is given by the tagDiv Composer page builder. We’ve specifically created this custom page builder so you can easily edit pages and posts on the frontend using adaptive elements and amazing visuals. Unfortunately, there’s no possible way to make two different page builders work at the same time. They have distinct functionality and coding specifications.
Thank you for understanding!
I really liked the tagdiv, but I have noticed that when creating elements, there are often several empty columns between the blocks. There is no easy way to eliminate this in tagdiv. Then I use WPbackery Visual Composer, but it is causing conflicts. Didn’t you find a way to allow the use of both composer?
Hello!
Do not use both page builders on the same page.
For the moment, the only solution is to shift from WPBakery to Composer.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
Thank you!
Hello,
The problem is caused if you use WP Bakery for posts, unfortunately, we recommend using WP Bakery only for pages and not for posts => https://forum.tagdiv.com/how-to-use-visual-composer/
Also, if you use the WPBakery for pages, we strongly recommend using only one of those plugins with our theme (WP Bakery or tagDiv Cloud Library, but not both).
Please deactivated the WP Bakery and see if the problem persists.
Thank you for your understanding!
Hello,
The problem is caused if you use WP Bakery for posts, unfortunately, we recommend using WP Bakery only for pages and not for posts => https://forum.tagdiv.com/how-to-use-visual-composer/
Also, if you use the WPBakery for pages, we strongly recommend using only one of those plugins with our theme (WP Bakery or tagDiv Cloud Library, but not both).
Please deactivated the WP Bakery and see if the problem persists.
Thank you for your understanding!
Try as a might i cant seem to get newspaper to display a full width video on a single blog post no matter what template i use, it allways comes up as a square and does not look visually appealing. my site is make-money-online.biz i want the video to look like the one on my home page, but if you check any post page its just a square. any help would be greatly appreciated.
Hello!
Do not use both page builders on the same time.
For the moment, the only solution is to shift from WPBakery to Composer.
So, I gladly recommend you to shift from WPBakery to Composer, because WPBakery is an old builder plugin.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
If you will use a cloud template, then you can edit the template and find in Composer an element called ” Team Member ” and some settings for that. For more information about TagDiv Composer plugin, check our documentation here: https://forum.tagdiv.com/tagdiv-composer-tutorial/
Unfortunately, there is no such element(https://test.circulaireconsumptiegoederen.nl/doe-mee-test/) in TagDiv Composer to be able to build exactly the same feature.
You can not edit a default template/CPT with TagDiv Composer plugin.
Check the differences here:
– https://forum.tagdiv.com/design-post-pages-using-cloud-library-templates/
– https://forum.tagdiv.com/design-post-pages-using-default-templates/
If you want to try CPT, then you can take a look here:
https://forum.tagdiv.com/custom-post-type-support/
Hope that helps you!
Thank you!
Hi! Is there any way i can use elements made in visual composer on a page build with TagDiv composer?
I have a team members grid set up now in Visual Composer however the styling of this page is different from the other pages because they were made with TagDiv composer. I can’t use any templates because these two modeling tools can’t seem to work together on a single page. Please help!
Hello,
Unfortunately, we recommend using WPBakery only for pages and not for posts => https://forum.tagdiv.com/how-to-use-visual-composer/
Also, if you use the WPBakery for pages, we strongly recommend using only one of those plugins with our theme (WP Bakery or tagDiv Cloud Library, but not both).
Thank you!
I am already using a child theme, and I use wp-bakery as a visual editor.
Thanks in advance
Question 1. Why can’t I use Tagdiv composer to write/edit/design Blog Posts if I choose DEFAULT POST TYPE to “DEFAULT”.
Question 2. However, if I use a template from the cloud library for the post then it shows Edit with Tagdiv Composer.
So now, in this case, I am on my post and click on Edit With tagDiv Composer, then is it going to edit the template of the post itself. If I edit here Is it going to affect the template itself.
In this post link above, I have applied 2 categories and now it seems like they are one, not Two.
1.PHOTOGRAPHY > 2.REVIEWS. There is no difference between them. I want that them to look different.
for example:- Main category with Bold font then secondary with normal font. So that there is a difference in them visually.
Question 4:- Every time I refresh the Page, Then looks like the website first displays few pixels on the right side in the browser and then comes to its actual place means exactly in the center.
I tried this on Your official Demo and seems there is the same issue.
Question 5:- Currently I haven’t enabled the tagDiv Mobile Theme and AMP plugin.
So, What you recommend in 2021. Like is it mandatory to use these plugins.
What will be the difference and benefits if I use these plugins.
If all go well, I will be using Google Adsense in the future. So what would be your recommendations about these plugins.
Thank You in Advance!
Hello,
Unfortunately, we recommend using WPBakery only for pages and not for posts => https://forum.tagdiv.com/how-to-use-visual-composer/
Also, if you use the WPBakery for pages, we strongly recommend using only one of those plugins with our theme (WP Bakery or tagDiv Cloud Library, but not both).
Thank you!
Hello,
This doesn’t work for me if I use TagDiv composer. It is possible that this css that they indicate works only in the template without TagDiv visual layout and for the composition with the visual editor you need a different CSS.
Also, Here is a list of current plugins:
All-in-One WP Migration
Anti-Malware Security and Brute-Force Firewall
Antispam Bee
Classic Editor
Elfsight Instagram Feed CC
Gravity Forms
Visual Composer Add-on Image Hotspot with Tooltip
Image Hover Effects Ultimate
Image Hover Effects Visual Composer Extension
Saragna – Instagram Social Streams Grid With Carousel
ShortPixel Image Optimizer
Unlimited Addons for WPBakery Page Builder
WPBakery Page Builder
Tasty Recipes
WooCommerce
Yoast SEO
After update, my custom template has some errors like:
wp_booster error:
Internal error: The system tried to use an att that does not exists! class_name: td_res_context Att name: “f_auth_nme_font_family</strong>" as "<strong>f_auth_nme_font_family”
…/wordpress/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_css_res_compiler.php
Where f_auth_n(code ascii 96)me_font_family maybe is f_auth_name_font_family
I try downladed others templates from the cloud templates and i have the same error (in my custom template and the downloaded template) in the tag div editor:
Error at zones: 6(models) : 5(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)
and in the visual editor the error described at the beginning shows again (the wp_booster error)
Hello,
I do see the theme allows for custom fonts in the theme panel. I know the custom font I want to use. It’s called Cambridge. However I don’t know how to get the font file in order to convert it or upload it. Can you please provide a visual example of how to obtain a font file and how to upload it. Thank you for your assistance in helping me to customize my website.
Yes I understand this “At the moment there is no option to edit a sidebar content from a post content. Anything you edit on your post template sidebar will appear on all of them.”
I asking is there any way to add the same info to all pages where are placed some element.
AS example: if I will add ad block to all pages or sitebars …any where in the page
And will change content in admin panet, that info will apier in all boxes.
I need this but for html, I tryed use in ads box but it change visual look and make spaces between text. what else can be used as ads box which does not change wisual look of the html code
Hello!
Do not use both page builders on the same time.
For the moment, the only solution is to shift from WPBakery to Composer.
So, I gladly recommend you to shift from WPBakery to Composer, because WPBakery is an old builder plugin.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
1. TagDiv Composer contains a lot of functions and features, please check our tutorial here: https://forum.tagdiv.com/tagdiv-composer-tutorial/
2. Unfortunately, you need to rebuild the design when you do the transition presented above.
3. Yes, you can use it with TagDiv Composer only.
Thank you!
Hello!
Do not use both page builders on the same time.
For the moment, the only solution is to shift from WPBakery to Composer.
So, I gladly recommend you to shift from WPBakery to Composer, because WPBakery is an old builder plugin.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
Please first verify this element with TagDiv Composer plugin and check if the article image size is correct or not, then set it correctly.
If the article image size is correct and also you didn’t solved the issue, then you can upload again the images in full size and set it again.
Yes, you can. If you use for example Video Embed element edited with TagDiv Composer, then you can turn off Autoplay setting which means the video won’t run automatically with the page only if you press the button play. Also, you can check our guides here:
https://forum.tagdiv.com/video-playlist-2/
https://forum.tagdiv.com/featured-image-or-video/
Please note that you need to set up the API key like this: https://forum.tagdiv.com/youtube-api-key/
Hope that helps you!
Thank you!
I want to sell memberships (subscriptions with restricted content), get donations and physical products. Right now I have WooCommerce and WooCommerce Memberships installed.
1. Setup the “My Account” page:
Do not be fooled about the “Woo Shortcodes” block in TagDiv composer. You cannot add shortcodes here (only the ones in the drop down menu).
Instead you have to use “Column text” and then open the WP Editor. Only as raw text (not visual tab) can you add the shortcodes, for example [woocommerce_my_account].
If you add [woocommerce_my_account] in the “Woo Shortcodes” block it will not display correctly (at least it displays differently for me).
I use the [woocommerce_my_account] shortcode on two pages (it is the default on my account page as mandated by Woocommerce), but it is also my main login shortcode.
2. Do the same for mandatory pages:
Create a new page (or edit old one). Add “Column text” and add shortcodes with WP Editor (Edit Content):
[woocommerce_checkout] (check out page)
[woocommerce_cart] (cart page)
(also make a Terms and conditions page)
3. Under the Woocommerce setting (advanced) assign the 3 pages you made (or edited). Cart, Checkout and My Account.
Here comes the problems:
4. The shop page I cannot edit at all. The content is somehow forced with a really ugly layout. I cannot make my own shop page as it is hard-coded from “My Account”.
5. The shop page only covers 2/3 of the page, leaving a 1/3 empty side bar. The checkout, cart and my account pages do not have this problem.
6. The final payment button is PINK. How to change this?
Hello!
Do not use both page builders on the same time.
For the moment, the only solution is to shift from WPBakery to Composer.
So, I gladly recommend you to shift from WPBakery to Composer, because WPBakery is an old builder plugin.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
Thank you!
Hello!
I gladly recommend you to shift from WPBakery to Composer, because WPBakery is an old builder plugin.
Please check our guide to know how to shift from WPBakery to Composer: https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
Thank you!