Migration From Visual Composer X Integrated to Original Vision Composer

[sappoutsource]

Hello.

What’s the best way to migrate from Visual Composer X Integrated to Original Vision Composer? I did try changing the setting of Visual Composer from X theme integrated to the original Visual Composer. To my surprise, even the elements I used from VC were completely messed up. So it seems moving to the original VC means rebuilding every page in the website with the original VC. This is OK for a small website, but for a big website this is really a big problem. Do you have any suggestions about migrating pages built in X theme with X integrated VC to the original VC without not having to rebuild every page?

Thanks!

[basanta]

Hi There,

Thanks for writing in!

There is a Little confusion in the question. You mean you are using visual composer for your pages and wanted to migrate those pages to X Cornerstone.
If so, you have to understand one thing that Visual composer and Cornerstone works completely different. Any page built using Visual . composer can’t be edited with Cornerstone builder. if you will do so you will loose the content.

Unfortunately there is no other way to migrate the content from Visual composer to Cornerstone except rebuilding the content. There is no issue using Both the builder in a single site. If you have pages with Visual Composer you can keep it as it is and for the new pages you can choose cornerstone builder.

Thanks

[sappoutsource]

Hi @basanta Thanks for the support. However, you have missed my point. Let me try to explain again:

The website’s content was built with Visual Composer, which is the X Integrated version; meaning before Cornerstone was even released, the X team somehow tweaked the original version of Visual Composer and integrated it to X theme. So the content was built with that X theme tweaked Visual Composer. Now, with time, the X team added a setting in Visual Composer setting which allows users to be able to use either the original Visual Composer or the X team tweaked Visual Composer. Please check screenshot here to see the setting in X theme: http://prntscr.com/kb92kh

The problem is this, when you switch to the original Visual Composer (meaning not the X theme integrated Visual Composer), all the contents, even the one built with Visual Composer (Not Cornerstone) are mess up and one has to completely rebuild every content. This might not be a big problem for smaller sites. But for a big site which used this X theme integrated Visual Composer to build so many pages before the release of the feature/setting to be able to use the original Visual Composer in X theme, is a huge problem. The reality is that there are some features one would like to use from the original Visual Composer that are not in the X theme integrated Visual Composer, so there is a need to switch to the original Visual Composer in order to be able to use some of the features of the original Visual Composer.

Thanks!

[paul.r]

Hi,

With X integration enabled on my test sites I tried creating a new page and added a bunch of vc elements on the page. Then I tried to disable X integration and check the page, the page looks the same and didn’t have any issues.

Can you try updating to latest version and see if that fixes the issue.

X 6.2.5
Cornerstone 3.2.5
Visual Composer:: 5.5.2

If that doesn’t help please provide us the exact url of the page where we can see the issue.
Then also provide the following information in Secure Note(key icon) so we can take a closer look.

• wordpress login url
• wordpress username
• wordpress password

Don’t forget to backup your site before updating.

UpdraftPlus WordPress Backup Plugin

Thanks