- TutorialsFrom WPBakery to tagDiv Composer
- TutorialsDefault Block Settings Guide
- TutorialsHow to Update the WPBakery Page Builder plugin
Hi,
Probably that happens because you have updated the Visual composer to the latest version. This is strongly not recommended, and it can cause problems like this
– https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
When an update for this plugin is released, we will first test it and then include it in the theme package when ready. Once provided in the package and officially supported, it will surely work as intended.
Try installing the Visual composer version that is currently bundled with the theme, and use it.
Thanks
Let me ask it another way. The ‘tech demo’ version of Newsmag brings ‘Newsmag default’ sidebar. I’ve placed 3x ‘[tagDiv] Block 15’ + 1x ‘[TagDiv] Ad blox’ in it. These widgets have no way of using custom added CSS classes.
On the other hand, on the right column of the frontpage (which is made with Visual Composer), I’ve placed a ‘Social Counter’, an ‘Add Box’ and a ‘Block 7’. If I edit these from within the Visual Composer page, it gives an option to add an ‘Extra Class’, in which I place the class which executes the following code, added in the Custom CSS section of the Newsmag panel:
@media only screen and (max-width: 768px) {
.only_desktop { display: none !important; }}
Since the default sidebar doesn’t give me the option to add CSS classes to widgets (for example, I also want to hide certain widgets that are placed in the footer section), they are viewable on phones and tablets.
If you would like to see the page, I’m gonna have to give you a username and password since the website is still in development and hidden behind a htaccess-login. Could you send me a mail at j.vanleeuwen@torasko.com if you would like this?
Thanks in advance for your feedback. I’m looking forward to hear from you!
Was hoping that you guys found already time to make it better.
Anyway I was thinking to change it, but same time it may make problems to me in the future. If something changes…
So maybe you guys can add some option or something where people can request something and then pay for that requested feature? 😉 I would happily pay for better review system, because it needs to be changed, to be more user (visual) friendly.
At the moment I add extra line where I write game name add again score there, because without that line it does not show review at all. And then add manually pros and cons, and also include <br> end of every line.
https://mkuubis.net/2017/crash-bandicoot-n-sane-trilogy-puuviljad-tervisele-kasulikud/
Hello
5 days ago i updated VC and Grid block disappeared. (I used the VC download file from VC owner’s site, not from Newspaper dir)
So, my blocks disappeared, then i get VC from newspaper dir and uploaded to VC dir in my plugins dir.
Now blocks are OK.
But i received a message to upgrade VC, can i upgrade? or if i upgrade my blocks will disappear again?
http://s26.postimg.org/mlfzfu3xl/screenshot_7317.jpg
Thanks
I use Newspaper theme. I’ve got a problem with „date” on start page. I heve build static page using Visual Composer and I set it as a start page. I arranged start page using block. In wordpress I’ve installed plug „Meks Time Ago” which automatically should change my post date display to “time ago” format like “1 hour ago”, “3 weeks ago”, “2 months ago” etc. However when I use it on my start page, plug doesn’t work properly – in block is a date when static page was created than the date when news item was added.
I already updated Visual Composer and now I’m having trouble recreating homepage with Tagdiv Composer, because I only see code and nothing Visual anymore (td_block codes). When trying to open it with Tagdiv Composer I get “Errors happened during _initStructureData() -> _getData()!”
How can I read the code to recreate the homepage (as advised in another topic of Radu) with Tagdiv Composer. It’s not that easy as told. And will I need to recreate all other pages too I made with Visual Composer?
The Tag Div composer has broken all of the blocks that were added in the Visual Composer.
All I see in the Visual Composer are a bunch of [td_block] shortcodes.
Is there a way around this to keep using the Visual Composer and NOT have to switch all content over to use the Tag Div Composer? I have downgraded the Visual Composer to 5.1.1 that was included in your last theme package.
Hi,
The Visual composer (included in the theme package) and tagDiv composer are tested properly with the theme, so they surely are compatible. Please elaborate on this problem so we can understand better.
Check the theme system status and make modifications to the parameters mentioned in this guide, if necessary
– https://forum.tagdiv.com/system-status-parameters-guide/
You can ask your hosting to make them if needed, as they might have their recommended method.
Then test to see if the composers are working as intended. The tagDiv composer is a front-end editor that can be used for pages
– https://forum.tagdiv.com/tagdiv-composer-tutorial/
– https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
Please consider that in future updates more options and features will be available for the tagDiv composer exclusively, as it is under continuous development.
Thanks
Hi,
Try to think of recent changes you might have made, that could have caused this issue. It couldn’t have happened all of a sudden. Maybe you have updated your version of Visual composer as there have been other similar issues. This should not be done, you should only update this plugin after it is officially released in the theme package.
Once an included plugin receives an update, we will test it and include it in the theme package
– https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
Thanks
Hi, i try to use it on pages and posts yet it doesnt work …not has usual before i update to newspape 8..please assist me..tq
http://umnosubang.com.my/wp-content/uploads/2017/07/sssaqq.jpg
Hi, we try to use VC on pages and posts yet it doesnt work. 🙁
Hello nitrofox,
You should not update the Visual Composer because this latest plugin’s version was not yet tested with our theme and that’s why you can get some errors in the theme, sorry! Notice that we will update the theme with this VC version as soon as possible.
Thanks for your understanding!
Hello smga,
You should not update the Visual Composer because this latest plugin’s version was not yet tested with our theme and that’s why you can get some errors in the theme, sorry! Notice that we will update the theme with this VC version as soon as possible.
Thanks for your understanding!
Hello Easely,
You should provide your website URL so I can take a closer look at it. Also, notice that if your page was made via Visual Composer, this page cannot be edited with TD Composer which is our new page builder. -> https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/ -> https://forum.tagdiv.com/tagdiv-composer-tutorial/
If is not what you mean, provide more details about your problem and provide some useful screenshots so I can identify the problem.
Thanks for the message!
The mention in the documentation was always there, but how can we know what each user does? It is up to each individual to read the theme documentation before using it and use the theme in the intended way or face the consequences of your actions. We cannot be held responsible for that.
Thank you for your understanding.
We cannot inform all users via a general email to not update the visual composer plugin as it is already mentioned in the documentation.
Thanks
Category codes and exclusions are showing in the Home Page blocks in Classic Mode. According to your colleagues at Visual Composer (WP Bakery), it’s your fault. What’s happening and how/when will it be restored to normal. /Users/Easely/Desktop/Screen Shot 2017-07-12 at 15.50.01.png
Hello,
Posts cannot be edited with the page builder. It is only destined for pages. Posts were never intended to be edited with any page builder in our theme.
We specified this in our documentation: https://forum.tagdiv.com/how-to-use-visual-composer/
Now the new page builder does not have an option to be activated on posts as it was never it’s purpose. You an create beautiful posts in our theme without the use of any page builder:
https://forum.tagdiv.com/post-templates-2/
https://forum.tagdiv.com/post-formats-for-tinymce/
As for the td composer error, please contact us via email at contact@tagdiv.com and provide a link to your site and wp-admin so we can login and investigate the issue.
Thank you!
“Big Grid Shortcodes” in the editor (WPBakery Visual Composer) are stopped to showing. Previously created entries in the classic editing mode shows shortcodes in the text, but the visual appearance shows blank lines. Previously published posts are displayed correctly, but something new Big Grid Blocks can not be created, because they are not in the visual editor.
It would be useful (for example) to build a page with several lines (sections) with a first line with theme blocks and in the bottom section (row) two columns with text or other content (or shortcode), and still below (other row) other blocks or other.
This can now be done with Visual Composer, with no problem and all responsive.
This is just an example, and it must also be possible with tdComposer, to increase its great integrated system value, and the efficiency it has demonstrated.
Fabio Duranti
Radio Radio Network – CEO
We are using TD Composer on numerous high traffic news portals, and have been since it was in BETA. It works beautifully for us, once you wrangle the normal ajax usability stuff in browser. It allows us to make complex home page layouts quickly, simply, and make multiple draft layouts for testing/review, then go live with the version we choose — with low overhead, higher page speed (95 with no caching plugin), and much lower CPU/RAM use or system crashes from pokey Visual Composer.
For those of us who need lean “main features” and speed, it’s superbly awesome.
Thanks again, TagDiv team! Love it 🙂
Your native composer is a nice idea, but not yet ready for use. Most importantly: it strips Visual Composer layout elements, but then is not sufficiently customizable (e.g. has no 1/6 columns, only 1/3). Furthermore, I activated Visual composer for WP posts as well – now my posts layout is messed up, and td-composer doesn´t work with posts. Sorry guys, but had to go back to version 7.8.1.
Hi,
Thank you for your appreciation of the theme. The developer team try their best to implement new features and options with every update.
Please note that the tagDiv composer is yet from being complete, or in a final stage. In coming updates more elements will be added to this builder exclusively. The elements you mention or similar ones may be added in these updates.
A two column layout is not possible with the tagDiv composer. I believe nothing will change in this regard, in the theme. This kind of layout is possible with Visual composer, but it was never recommended. Using the suggested row layouts ensures that your blocks will look and work perfectly.
The tagDiv composer is a front-end composer, a back-end view of the website structure is not possible. The editor is not meant to be a copy of Visual composer, try to think of it objectively.
You can still use Visual composer, if for the moment the tagDiv composer does not have the options you require for your website. You can make the transition at a later time, when you consider the time is right for you.
Thanks
Hello to all,
only a report and short considerations.
We are making our new site with your theme and much personalized code for our needs; everything works well and optimization makes great results on speed and usability.
You can see the development at http://deb.radioradio.it (the content is real but test). The layout has yet to be decided, next week will be published at the definitive address radioradio.it.
We loved your work with the latest release (8) to create a native composer; In fact it’s even better than optimization and it seems to work fine.
Despite this, your composer is still missing some features, options, and widgets, very important for a modern and flexible layout.
For example, there are missing boxes, spoilers, accordion, tabs, icons, and other small items that sometimes seem useless, but contribute to the site’s appeal.
Then, very important, it is not possible to make (for example) a two-column (obviously responsive) page layout, or divide the contents of a column or row into n-columns; These are all things that can now be done with Visual Composer.
Still, you can not insert third-party shortcuts that are available in the text editor (probably depends on some incompatibility with the frontend editor).
Sometimes for a more general view, it is better to see the backend scheme (such as VC), which can not be done with td Composer.
We understand that in most cases you do not need to use these options / features, and may be harmful if someone is using them badly, but there are layout circumstances that need them.
For this reason, although we really enjoy your work, we prefer to stay in Visual Composer, hoping that in the forthcoming release, you can implement those features that are missing from your tdComposer today.
Thanks for your great work.
Fabio Duranti
Radio Radio Network – CEO
Hello barnisayz,
Please check our documentation for more references about how you should correctly use our page builder, like this -> https://forum.tagdiv.com/tagdiv-composer-tutorial/ -> https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
Thanks for your understanding!
Hello,
I have tested the font on my end but could not recreate the issue. The block title font on every template worked as expected.
Please try to disable all plugins except visual composer, clear cache and reset cdn files if you use it. Then test again.
Thanks.
