I just upgraded from 7.5 – 8.7 – It went amazingly smoothly – Thanks!
I now really want to move away from the old composer and on to tagdiv composer, although I have one small problem
When I activate TagDiv Composer it affects the layout of my post pages that all use the following shortcode:
[vc_row][vc_column width="1/2"]
[/vc_column][vc_column width="1/2"]
[/vc_column][/vc_row]
Without – https://imgur.com/xxIXxQp
With TagDiv on – https://imgur.com/CONhpJi
Is there a solution to this?
Kind Regards
Simon
Ok, changed style as follows:
This:
.td-pb-span6 {
width: 50%;
}
Became This:
.td-pb-span6 {
width: 34%;
}
Please let me know if you think this will cause issues?
Regards
Simon
Hello,
Using visual composer on posts was never supported in our theme. We always advised against it. If you want to move over to the tagdiv composer, you will have to remove any vc code from your post. The width change you made in css will impact other parts of the site as well. It is not a solution. The only proper solution is to remove VC elements from your posts.
Thank you!
I didn’t use VC on my posts, just the shortcode (manually) what would be the best method for replacing the [vc_column width="1/2"] shortcode to achieve the same effect of splitting the themes main coloumn in two halves that will remain responsive?
Thanks
On pages there is now an option to split the content in two equal columns, in the tagDiv composer
– https://www.screencast.com/t/UsRnz9aaeSXF
The multi-purpose plugin adds more functionality to the composer, meaning row layouts and many elements that can be used on pages. The recommended method of switching to the tagDiv composer is to recreate the pages entirely with it if possible. Then there will be no more problems.
On posts for the moment the tagDiv composer cannot be used, this may change in a future update.
The tagDiv composer uses the same row/column shortcode as Visual composer, there is a level of compatibility between the two page builders
– https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/
All of my posts have the [vc_row] shortcode to create a 50/50 split. Even though I had VC disabled for posts, I manually used the shortcode which I’m guessing means I sort of did use it, even though it was not active on the backend.
After I updated to 8.7 everything worked except for these areas of the post. When I changed the span6 CSS in my child theme from 50% width to 34% it restored the appearance. I’ve since deactivated VC and I’m now using TagDiv composer on pages which I think is absolutely awesome.
I think what I need to do now is find a suitable solution to replace the VC shortcode on posts so that I can restore the span6 style back to 50%.
I’m not sure where else this span6 style is used, but the site seems to appear ok with it set to 34%
Maybe I can use .CSS to create 2 floating div’s that have min-widths to cause them to fall beneath one another when viewed on a mobile.
Ok,
I think I’ve come up with a simple div class to replace the 2 column VC_ROW shortcode.
The CSS
/* VC_ROW REPLACE */
.section {clear: both; padding: 0px; margin: 0px;}
.vcrow { display: block; float:left; margin: 1% 0 1% 1.6%;}
.vcrow:first-child { margin-left: 0; }
.group:before,
.group:after { content:""; display:table; }
.group:after { clear:both;}
.group { zoom:1; /* For IE 6/7 */ }
.twocols { width: 49.2%;}
@media only screen and (max-width: 480px) {
.vcrow{ margin: 1% 0 1% 0%;}
}
@media only screen and (max-width: 480px) {
.twocols { width: 100%; }
}The HTML
<div class="section group">
<div class="vcrow twocols"> CONTENT </div>
<div class="vcrow twocols"> CONTENT </div>
</div>
Indeed the posts seem to be displaying fine at the moment from what I can see. As long as it works there is no problem, would be the bottom line.
This link https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/ doesn’t work
This link https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/ doesn’t work
This link https://forum.tagdiv.com/visual-composer-tagdiv-composer-transition/ doesn’t work
From WPBakery to tagDiv Composer
tagDiv Composer is the first-page builder ever created for blogs, news and magazine websites. Designed to help you be more creative and more efficient, tagDiv Composer allows you to build, edit and shape your pages right on the front end, easier than ever.
We developed it from scratch to give you the best performance while making the transition from WPBakery Page Builder plugin as smooth as possible.
How to move your pages to tagDiv Composer:
Step 1 – Install both the WPBakery Page Builder and tagDiv Composer plugins.
Step 2 – The page has to be recreated using the new page builder. You will have to build a new page and edit it with the tagDiv Composer replicating your original page (made with WPBakery Page Builder).
Step 3 – Save the page. Replace your homepage with the newly created one. You can always revert to the original page if you encounter any problems.
Step 4 – Disable WPBakery Page Builder as it is not recommended to keep both plugins active.
Important Note: Do not use both page builders on the same page!
Why should you use tagDiv Composer?
We strongly recommend you to use tagDiv Composer with Newspaper. Why? First of all because it is developed especially for this theme. For us, this is the only way to provide you and your audience with an amazing experience.
Most multipurpose page builders are very hard to optimize for a niche website like a blog or a news magazine. However, these plugins will bring needless components and compromise the performance of your website. To save you from the hassle, we have a built tagDiv Composer, an excellent tool designed to make your life easier!
Our team is constantly searching for a new way to make online publishing on WordPress even easier. The new features, innovations, and improvements will be implemented exclusively on tagDiv Composer. We believe this will become an essential instrument for any kind of website.
What’s different?
The most obvious difference is that tagDiv Composer runs integrally on the front end. We opted to develop and implement our own frontend page editor. This allowed us to optimize the speed, the user interface and the features to work seamlessly with the Newspaper theme.
To make the transition easier for you, we built our shortcode parser, and we use the same shortcodes as WPBakery Page Builder for all the custom blocks, big grids, rows, and columns. The differences come from the shortcode attributes. For example, we have implemented an easier and totally different way to use the CSS box than in WPBakery Page Builder.
We advise you to use only one of the page builders to create a page. If you try to use the two builders on the same page, this is what may happen:
Any shortcode attributes that are different will be lost when the page is saved (for example row background, CSS box style, and others)
tagDiv Composer will strip all WPBakery Page Builder specific shortcodes like the buttons, media grid, and tabs.
WPBakery Page Builder cannot load our custom attributes like the CSS box and backgrounds. -> https://i.imgur.com/nV1XK36.png
What’s improved?
All the blocks are mapped the same way in both plugins. This means that custom components have the same shortcodes regardless of the builder you are using.
We have spent a considerable amount of time designing the user interface for tagDiv Composer. We refined every detail to create an intuitive interface. With this builder, a new user can create a page in minutes without reading the documentation or tutorials. -> https://i.imgur.com/iwDK1uP.png
Thank you!
