-
Posts
-
Hello,
If I create a new Page in WP, then the VC backend editor is immediately available.
If I try to create a new Post or Portfolio Item, I have to switch to the VC Backend Editor every time.
Yes, I have of course enabled it from the VC settings.
The only way to force it is to disable the WP Editor completely.
This is a bug in old VC, but of course I have no way to update the VC.
Also, for posts and portfolio items, if I click on the Icon in the VC top row of the backend editor to add a new template, it does not work.
Works fine in Pages.
It works in the posts if I click the Add Template button at the bottom of blank editor screen.
See attached screenshots
Hi there,
Thanks for posting in.
I just tried on my installation on post or page, but I don’t have this issue. Would you mind providing your admin login credentials in private reply?
Thanks!
Hey there,
Thanks for reading. The server is running in Vagrant on a localhost VM, so unfortunately can’t be accessed from outside.
That said, I have narrowed down the problem to the Templatera plugin..
I can send you a copy of that to test for yourself if you want?
And I know I’m beating a dead donkey, but this is exactly the reason I feel so frustrated with the way in which the VC has been mangled into X.
You will probably tell me that you don’t support 3rd party plugins like Templatera, but WP Bakery will tell me that since I am using a bundled version of the VC, I need to speak to the Theme Author.
However, since X is not really using the standard version of the VC, I am stuck between a rock and a hard place.
I can’t install my own licenced copy of the VC, because it breaks X.
Anyway, I guess I can moan until the cows come home, it wont help me solve the problem.
Any other ideas? Can I send you the (official WP Bakery) Templatera addon to test in your own environment?
Hello There,
Sorry for the inconvenience. If you want to the vanilla version of VC, you can simply disable X integration by going to Visual Composer > X Integration. You need to disable all the options on this tab to able to restore VC to its vanilla version. You may also need a license so that you can use the Templatera addon. To know more how we utilize VC in X, please check out our knowledge base here: https://community.theme.co/kb/integrated-plugins-visual-composer/
Hope this helps.
Hi
No problem.. Not sure why I thought this wasn’t a possibility.. Seems things have changed since I last tried to install my own VC, so that’s good, thank you.
On a similar note though, it appears to be impossible from within the Cornerstone setting (Admin side), to deselect all post types.
I did try Cornerstone, but don’t like it at all.
So I went to the settings and tried to untick all the boxes for the various post types. It can’t be done. Cornerstone forces you to select at least one post type.
My solution to this was to create a custom post type with no UI and no front end query, no admin menu, no archives, no walker registration etc (basically a shell), in order to assign that as the only post type the Cornerstone is activated on. I called it “none”, so there is now an option to select post type: “none”.
Nobody can use Cornerstone by accident now, which is what I wanted (also to stop it from injecting bloat, although not sure if this has been achieved or not).
We should be able to deselect all post types from the settings if we choose not to use Cornerstone, surely?
I’m sure the way I have done it is not a good method, but I don’t have the time or the patience to understand this “bug” properly.
Hello There,
This isn’t a bug. In our test server, you can deselect all the post type to disable Cornerstone.
Please be advised that to run X smoothly, you need to install and acyivate Cornerstone plugin. All the shortcodes and X functionalities has been integrated in this plugin. Even if you will not use Cornerstone as your page builder, we highly recommend that you left it active.
Hope this helps.
Nope, can’t do that.
If I deselect all, then it defaults to the last one that was active. I can untick all except one.
Also, Cornerstone cannot be deactivated, so no worries there. I don’t mind leaving it activated, but it is impossible to deactivate it. If I try that, then it automatically reactivates itself.
The only way to deactivate it is to switch to a different theme.
Like I said, I don’t mind leaving it activated, but I can’t deselect all post types.
I know you want access to the server to help more, but I can’t provide that information right now.
Ok, since you say it should be possible, there must be another cause. Will try to find it..
Tell me this though.. can I overwrite the installed core X Theme entirely to see if I can flush out some of these bugs?
I mean, can I download a fresh copy of the Theme to my pc, then overwrite the installed copy on the server without losing data?
(deactivate the theme, overwrite with fresh version via sftp)?
Hello There,
You can download a fresh copy from your Themeforest account’s downloads section or in your dashboard (https://community.theme.co/dashboard/). You san simply overwrite all the Xfiles by uploading those files in your ftp. You won’t lose any data. You could also try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.
Please let us know how it goes.
Hi, the cornerstone “bug” wasn’t a plugin conflict (that is usually the first thing I check). Overwriting the Theme files seemed to have solved it.. I guess there must have been some old code hanging around that wasn’t being flushed out for some reason (there have been quite a few big changes to X since the original installation).
Odd, but there we go..
Regarding the templates button issue, that is definitely a conflict between the Templatera plugin and X.
Templatera works fine on other themes I use, but I don’t really use it very much so will just delete the thing and replace the few instances with Advanced Custom Fields, (am not willing to be playing intermediary between the Theme Devs and the Plugin devs).
Thanks for your input, and for keeping me company while I worked through this particular niggle.
Glad it’s working for you after replacing the theme files!
Let us know if we can help you with anything else.
Cheers!
