I am new to this theme and I installed the CityNews demo to get started. This was 3-4 weeks ago but I haven’t had time to work with it until now.
When trying to edit the start page it shows a warning that this wasn’t built with the tagDiv Composer and I see VC tags in the page editor.
In this post from April 2 Calin wrote:
“Please note that our demos are build with tagDiv Composer, also …”
Has the CityNews demo been rebuilt since I first installed Newspaper, or was I just unlycky to chose and old demo? How do I know which demo I can use? I dont want to start out with old stuff.
Hello,
Please ignore that warning as it will not influence the proper functionality of the theme. Nothing has changed. A simple save in the WP back-end will cause the notice to come up as it detects that the composer was not the page builder that saved the content to your page. Edit the page with the tagdiv composer and press save. The notice will be gone.
Thanks
Thanks, I tried that and it worked but I’m bothered by the vc tags like this:
[tdc_zone type=”tdc_content”][vc_row][vc_column][td_block_ad_box block_template_id= …
Is that normal?
Are there no backend editor? I see the code in WordPress editor and the page in tagDiv frontend editor. Is there nothing in between like VC Comp. or Avada?
Hi,
The tagDiv composer doesn’t have a backend version, it is a front end composer only. In the backend of the page there will be shortcodes – http://prntscr.com/n9gdu5 this is normal. Those shortcodes are the page content.
WPBakery does have a backend editor. If you want to create pages with it, it is provided in the theme package. Note that there may be problems if you edit pages created in one page builder, with the other.
The theme demos are all created with the tagDiv composer. If you have more questions let us know.
Thanks
I am still puzzled when you say all demos are created with tagDiv composer. Why do I get a warning saying this page was created with something else? Seems very strange to me. And why do the page have vc-tags?
I dont demand a backend editor. I just want to know how this works.
Nothing to worry about in most cases when that message is displayed. That message appear when making changes in the backend of pages, for example like saving it as draft, changing the page template and updating the page etc.
The tagDiv composer was built by us, it uses similar shortcodes as WPBakery to provide an easier transition between the two if needed. So for example a page that is built with either, containing theme provided blocks, grids etc will work with each of them.
If on the other hand a page contains specific elements from WPBakery it should be edited only with WPBakery, or if it contains tagDiv composer specific elements it should be edited only with the tagDiv composer.
Please let me know if you have further questions or you need help.
The message appeared when using the tagDiv frontend editor. No message in the backend. The page is imported from the CityNews demo.
How is a new user supposed to understand that this is a message he can ignore? It’s the absolute first thing that happens “you can’t do that?”
And how is it that you claim to build your demos with your own tools and still generate errors for the first time user.
I will use most of my time the next 6 months moving a big site over to WP. Right now I’m looking around for a new theme. It must be robust without strangeness.
I get WTF as my first reaction trying to use it. If there is something wrong with the demo just say so. Right now I don’t understand how your own tool can throw errors like this.
“In most cases you can ignore it”
Please give me a list of the cases when I shouldn’t ignore this. I need to post it for my colleagues. When the site tells you the page will break ignore it unless …
This is not how a site with 100k visits should work.
I’ve ignored the message shown on the frontend and saved the page. So now the frontend warning is gone.
Instead I have this backend warning.
The content is compatible – ah good!
But modify it carefully – eh… why?
I understand what you mean. There are plans to modify the actions or circumstances in which the messages (not errors) appear, currently this has not been modified since the introduction of the composer a while back. I’m sorry for the confusion this may create.
If the pages/cloud templates have been built entirely with composer elements or simply imported, the message can be ignored at all times when it appears.
Errors are in most cases caused by various codes entered in the page content by some means, or plugins, mostly the error mentioned in this guide at point 5
– https://forum.tagdiv.com/tagdiv-composer-not-working/
Thanks
About the backend warning. Modify it carefully implies “here in the backend editor” – i get that now. As a fresh user I didn’t understand that or read it like that. It just says “modify carefully” which looks like a joke at first.
This plane was built by Boing! Are you sure you want to fly with it?
I would rewrite that message so it’s super clear what you mean:
Content made with TagDiv Composer. Use the tagDiv Composer to edit the content (not the backend editor).
Anyone using the backend editor would then be at their own peril.
Sorry again about that, as I said there will be modifications to that message and some other notifications. Let me know if you have more questions.
