Hi,
unlike previous composer version, the new tagdiv composer does not feature adding a button. Is there a way to create it, please?
Hi,
At the moment a particular button element is not available in the tagDiv composer. Buttons will be added in the coming theme update, along many other features.
You could create a button in a text element if you wish so, by selecting the text and making it a button, add a link if necessary as well
– https://www.screencast.com/t/nfGSxIp68Vh
Thanks
Thanks Simon
I need buttons as well. I’m actually losing money not having Buy Now buttons – mine also had font awesome icons associated with them so I need those as well. The VC doesn’t work with only the Tag Div composer and I don’t have that second line of the toolbar in your screencast. I need to go look for an html/css version I can use ASAP.
What is your date of offering buttons? Or making VC work WITH your composer? Or something other than…too bad we deleted it?
Hi,
I cannot specify an exact date, the theme update should be available as early as next week. There will be buttons available in the tagDiv composer with a considerable amount of customization options. Sorry if the present situation is creating an inconvenience.
You could try creating a button on pages if it is absolutely required at the moment, using the method mentioned above.
Thanks
It should have been all laid out for us – instead of a fancy sales video for new customers – you could have laid out for all of us current and paid customers what would crossover and what wouldn’t and if you were adding on something like “buttons” later – just tell us!!!!!! I just spent 6 HOURS on recreating buttons so no I’m not doing it again next week. You definitely should have made your composer work WITH VC – not against it.
And I wouldn’t have chosen today at all to make the switch if I’d known you were missing so many VC elements and were working on them.
You give us NO usable information for us to decide what to do with our businesses, time, customers – nothing. Seems like you could have handled this much better and actually considered your customer base.
Hello,
No one is forcing you to move over to the new page builder. You can use vc just as before and disable the tagdiv composer.
Sorry you feel this way about our product and marketing. As well as our support. If you feel the theme is not to your liking, you can request a refund here: https://themeforest.net/refund_requests/new and we will provide it
Thank you!
Stop activating the TD composer every time the theme updates. You made it so the VC composer has to be manually updated every time. The same should be said for the new (not yet even close to done) TD composer. You activate it automatically every time the theme updates and then it screws up our sites. Since your TD composer is still in Beta, don’t make it automatically active.
The theme was fine until you messed it up with a not even half done product you insist on activating. I’ve put HOURS (like WEEKS) into troubleshooting your theme and plugins. Are you going to refund me that???? If not, then please just fix what doesn’t work.
Please tell me the new code for each of these elements:
This One:
vc_row][vc_column][vc_text_separator title="" i_icon_fontawesome="fa fa-ticket" i_color="custom" color="custom" style="double" border_width="2" add_icon="true" i_custom_color="#e59773" accent_color="#e59773"][/vc_column][/vc_row]
This One:
[vc_row][vc_column][vc_message color="info" message_box_style="solid-icon"]
- bullet one
[/vc_message][/vc_column][/vc_row]
And:
[vc_row][vc_column width="1/3"][vc_btn title="Title" style="3d" color="info" align="center" i_icon_fontawesome="fa fa-book" link="url:link||" add_icon="true" button_block="true"][/vc_column][vc_column width="1/3"][vc_btn title="Title" style="3d" color="info" align="center" i_icon_fontawesome="fa fa-commenting" link="url:link||target:%20_blank" add_icon="true" button_block="true"][/vc_column][vc_column width="1/3"][vc_btn title="Title" style="3d" color="info" align="center" i_icon_fontawesome="fa fa-map" link="url:link||" add_icon="true" button_block="true"][/vc_column][/vc_row]
You claim to have directions for moving from VC to TD – I don’t see anything that will help me convert the above code.
Sorry but the tagdiv composer does not have shortcode equivalent for those elements.
Why do you insist on using the tagdiv composer when you are clearly in need of the old VC elements and do not want to create new pages? Simply use VC just as before. We are not forcing anyone to use the new page builder. Simply disable the plugin and install vc found in the main theme package and all the work is done. Do not use both cs and tagdiv composer at the same time though.
Thanks.
I didn’t insist on it. YOU activate it every time we update the theme. You are the ones insisting on it. And you claimed it was ready for primetime -and you claimed you had an easy transition guide – and that it is a new substitute for VC. It’s neither of those things – yet you force it to be active every time we update the theme. And you claim to have a guide to convert – which you don’t. Why didn’t you just TELL US what the TDC does NOT have before wasting our time? Why do you automatically install and activate a half finished plugin? Why not give us the option of activating it?
If you were me – wouldn’t you think based on your 1) automatically installing and activiting it, 2) saying it was the new plugin you were planning on using and 3) that you had an “easy to convert” guide –
If you were me – wouldn’t you think any/all of the above were true? There was no need for me to go down a rabbit hole when you already KNEW your plugin wasn’t ready to use as a substitute for current theme customers. It would go a long way if you showed a little respect for your customers time and money instead of making VERY COSTLY false claims.
Hi,
Sorry for the inconveniences you are facing using the theme and theme plugins. It is not our intention to cause such issues. The tagDiv composer is in continuous development, it’s functionality and features may change in the future. Currently this composer will be activated automatically the moment the theme is updated or installed. So if Visual composer is preferred and used instead, it will have to be deactivated in these cases.
The transition basically means that pages have to be recreated with the tagDiv composer. There is a level of compatibility between the two composers, elements like blocks and grids share the same shortcodes.
Thanks
HERE HERE… nycinsider… tagdiv composer has many great elements, but it sadly fails to deliver on some of the most simple of things which should really be a basic function to any page builder platform, such as adding text and being able to simply make some simple customization to that text.
I regret the day I moved away from VC to td composer.
