[Hoang DParticipant]

Hi I updated to 1.8.3 using wordpress version 3.8.3 and I am stills seeing this http://imgur.com/lc7yqLl . Even after I clicked update the message still shows up after i save. Please help

Thanks!

[Hoang DParticipant]

This reply has been marked as private.

[KoryKeymaster]

Hey Hoang,

Thanks for writing in and we’re sorry that you seem to be experiencing some issues with Visual Composer. The particular issue you’re running into has nothing to do with any particular version of Visual Composer, it is merely a nuance of working with the plugin itself. Allow me to explain why this happens.

Unfortunately, Visual Composer is particularly finicky about how shortcodes must be structured on the page in order for the plugin to work correctly. For example, when you add a Row to your page using Visual Composer, it actually outputs the following code in your Classic Mode editor:

[vc_row][vc_column width="1/1"][/vc_column][/vc_row]

As you can see, adding a Row means that all of your content is placed within at least the [vc_row] and [vc_column] shortcode. This is not readily apparent as using the Visual Mode editor does not show this as it covers up the Classic Mode editor, but this is how things work on the backend.

The warning you’re seeing (as mentioned in your thread) displays if you have tried to start editing a page in Classic Mode and then switched to Visual Mode, or if you have started editing a page in Visual Mode then switched to Classic Mode to make some changes and then switched back. Essentially, if you make edits to the output of Visual Composer in Classic Mode, it is very likely that you will not implement your changes appropriately with how Visual Composer requires things to be structured. It is for this reason that we always tell our users if you start using Visual Composer, you must keep using that, you cannot switch back and forth between Visual Composer and the standard editor due to the nuances of the plugin.

Likewise, if you start out in the standard editor, you cannot just switch to Visual Composer all of the sudden without experiencing this issue. One of the biggest problems with this is the fact that Visual Composer’s API does not provide us with any way of changing out their [vc_row] and [vc_column] shortcodes to the X theme equivalent (i.e. [content_band] and [column]). This is why we provide “Visual Composer Compatible Page Layouts” in the Demo Content section. They are the exact same page layouts as the non-Visual Composer compatible ones, but they use [vc_row] and [vc_column] instead, and also restructure some other shortcodes as necessary as you cannot edit things as freely with Visual Composer as you can with the classic editor.

Hopefully this helps to provide some insight as to why this message appears and what it truly means. Unfortunately, selecting the Convert to new version button in this message does not really fix anything, and can ultimately make your layout have bigger problems. Our recommendation is that if you have started in one “mode,” to always stick with that mode unless you are starting completely from scratch (i.e. deleting all page content).

Thanks!

[Joerg SParticipant]

Hi Hoang,

what I did to solve the same problem on my wp:

• create a new empty page
• put two browser windows on your screen
• open both pages in classic text mode
• copy the content block by block from your original page to the empty page
• proof after every block yout transferred if you can switch the new page to Visual Composer without trouble
• if not – delete the last block on your new page
• change to Visual Composer and create what you need for the block
• change back to classic text mode and copy the text or block content within the format codes to into your new created block

[AlexanderKeymaster]

Hi Joerg,

Thanks for sharing your experience here! Glad to hear you were able to get it working on your site.

[Author]

Posts