it has and is enabled
it stopped working
it started again (not sure when)
no changes were made

i don’t use your internal tools because they don’t work with the rest of wordpress so none of your extras besides the theme

why would i do this if i’ve always had a sticky sidebar that worked fine and stopped working for no reason?
https://forum.tagdiv.com/smart-sidebar-2/

But for now it doesn’t matter because the tagdiv editor is broken and no one will help me fix it anyway. Probably easier if I just start using that CSS and work from there. At least it won’t take a week – and it won’t break every time something gets updated.

something like this:
https://stackoverflow.com/questions/24470877/how-to-create-a-box-with-rounded-corners-at-the-top-but-normal-corners-at-the-b

which one of those has a border around the entire text and title? so it looks like one box.
I’m not seeing it.

Where on that page does it discuss the Text with Title element – which is clearly what I asked about. I did a search and don’t see it.

Oh – and for the record, the entire page is in column text elements. Like I said, I only need a few buttons and maybe one other section. Can’t you just make the elements work? I spent an hour copying and pasting this page into your elements so I could use 1-2 elements of yours and now it’s not even working. Waste of my time and I’d like you to fix it.

Without bothering with the rest of it, this is likely the issue:
5) The model does not match the content
tagDiv Composer not working: The model doesn’t match the content

This error appears in the tagDiv Composer page builder screen when you are trying to edit a page that contains unsupported shortcodes. The most frequent cases are: the page was modified in the backend by adding code or scripts directly through the TinyMCE editor or if you’ve inserted HTML code with missing tags. This error is also be caused by specific plugins that insert code into pages. You should not use such plugins.

Solution:
You can fix this in two different way:

Clean the code. Recreate the element with the tagDiv Composer. If you need to add other items that are not present in the tagDiv Composer elements list, please use a “Column text” element.
If you already added custom HTML code inside a “description” section inside a tagDiv Composer item, make sure it’s clean and correct (no missing tags). Also, please consider removing it. We recommend you to do not insert HTML code in the page builder as it may cause issues and affect the way tagDiv Composer is functioning.

But these are shortcodes I use on my entire site and I need to keep them. The page builder is useless if I have to update it manually every time I make a site wide change. The composer should work like the rest of the site – I make a change in one place to a shortcode and it changes sitewide. This worked when I bought the theme when you used VC and it doesn’t work for my business model to change it now.

Please make the tagdiv composer work with other shortcodes. I need the composer for just a few elements, like buttons. I shouldn’t have to change my entire business model to use a few buttons. They should just work.

All resolved. Thank you so much!

Hi- i don’t post links to my sites in public forums. Where can I email you? I’ll manually change one post to template 8 so you can see. Same for the footer – I’ve removed the link for now but I can email you what I want the code to be. Thanks.

Hi – I have the same question as Jeanne. Would you please answer it?

“I want to create one type of header for my homepage and another type of header for all my posts.” either through the new Header manager or the old theme options.

And a second question, how do you use the new Header Manager on posts?

Thanks.

And I don’t see a choice for “column content”

I asked for directions. You did not provide any. But I’m glad you’re able to do it on your computer. Maybe you could fix the page builder rather than say it works when it doesn’t and you can’t even explain how to work it.

Don’t blame the page builder? You JUST said the only way to do in YOUR Page Builder what was easily done in VC one was to use CSS? And you STILL didn’t explain how to do it.

How is that not knowing how to use your page builder? That’s wanting an actual page builder INSTEAD of having to do everything CSS. That’s the point of a page builder.

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.

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.

OK. I’ve deactivated every plugin. Now the page builder doesn’t work. Now what? I still can’t hover over a link on the front end of hte page builder or click a link.

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.

None of that answers any of my questions. What parts don’t you understand? VC was removed from my site (which is why I have BROKEN stuff EVERYWHERE!!!!). Now, go back and please try and help me. This has been hours and hours of my time. The front end thing is broken, the elements are missing, you didn’t lay out ANY TYPE of transition guide at all! You didn’t tell us the TD composer doesn’t have even HALF of what VC offers. You didn’t map out how to change the code. All you did in your fancy useless video was market to NEW customers. Ignoring your old ones.

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.

it was a new page.
I’m not disabling plugins. That’s always the worst and most lazy answer you give. Not happening. Try again.
I can hover over linsk on any page/post on the entire site. I can do it in preview mode.

Now make it work on the front end of your composer. Simple – just make it work like it should.

It’s near impossible to use that front end thing – so I still don’t understand your answer. What does, “The equivalent is the same with this” mean? Nothing but errors, back and forth from front end to back end, copying code and pasting it to other elements.

Has anyone who constantly builds/updates/writes sites actually used this thing? Themes are not just for designers who build a structure and pass it off to the client. They are also for people who write websites and need to update them daily. This is not a tool for that. VC was much easier to use.

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?

OK – I figured out what was causing my errors. But it’s something that needs to be fixed.

I use a lot of separators on my site. I also use a lot of shortcodes around the site. When using these codes on the site, here are the statuses:
[vc_separator] – fine
[vc_separator color="#5aa1e3" style="dashed" border_width="4"] – fine

However, I put the above code (the second line) in a shortcode called, “[contentblock id=separator-blue-dashed]”

And that’s when it breaks the front end. The blue line shows fine on the site but it breaks the whole front of composer and I can’t change anything else.

I use these shortcodes everywhere on the site – they’ve never been an issue anywhere else or with any other theme. Nor did they cause errors with VC. So it’s strictly limited to TDC.

If we can’t use simple shortcodes (which is necessary), how can we change, for example, the color of a line sitewide when we want to? I don’t want to format 1000 separators on the site individually – I want one place where I can edit and update them in a few seconds without breaking everything else. Thanks.

same here – was editing a page (for hours). Worked about 50 times saved. Then all of a sudden it didn’t work. Changed a few words in a Title with Text block – that’s it. Now I can’t edit anything on the page from the TagDiv composer.

Errors happened during tdcIframeData.init() -> bindViewsModelsWrappers()!

Must be a better fix to this error. I see it has happened a lot – and doesn’t appear to be related to Yoast, SSL or other suggestions.

Can you just give me the shortcode that is the equivalent of [vc_column_text]

This is what is in my config file: define(‘WP_MEMORY_LIMIT’, ‘6000M’);

Can you just give me the shortcode that is the equivalent of [vc_column_text]