Visual Composer Missing WYSIWYG editor in Text Block
This is my first time using BeTheme because a client liked one of the designs. It looked like it had decent documentation and was supported. There are a few themes I have used for clients that have Visual Composer included and they all look and function differently based on the theme.
When I insert a text box into a row the text box is not functional and is missing the WYSIWYG editor.
Notice the lack of WYSIWYG on the Visual tab? I mean there's text there, I even took another screenshot to show you. That's another problem - the text always shows up white! I almost get the feeling that Muffin Group is forcing customers to adopt their tools and not tools like Visual Composer. Which brings up another issue I'm having with the Visual Composer/Muffin Builder debacle. There should be a way of disabling Muffin Builder so it doesn't conflict with Visual Composer. It took hours to figure out all the settings in both Muffin Builder and Muffin Options menus to finally get VC working the way I wanted it to. There should be one button. Do you want to use Visual Composer or Muffin Builder?
Back to the problem at hand...
Are there any known issues with the BeTheme stripping out functionality from Visual Composer or similar problem? If so how can I overcome the obstacle?
The [XXX] theme that I typically use (not affiliated BTW) works great with Visual Composer and has a nice skin and predictable functionality.
The themes with the most notable problems, I've noticed, are the ones that try and make their customers use their own custom builders that emulate Visual Composer.
Would really appreciate if someone knew a way around this issue, I want to like this theme but it's tough when I'm feeling so limited.
Thanks all!
Comments
there is no known issues and the Text Block VC item works fine what you can see yourself on http://pasteboard.co/n4YVcA8mT.png (we did this screenshot especially for you to show that it's fine). We are pretty sure the problem is on your end only and might be related with other 3rd party plugins. We suggest to switch to default WP theme and you will see there wouldn't be WYSIWYG editor as well.
I didn’t even bother responding to their last reply because unlike most theme support, these guys don’t want to offer a real solution to fix bugs in their code or resolve conflicts that impact customers.
Taking their advice, I removed WordPress, the BeTheme and all its related plugins. After that everything worked perfectly.
Their proposed solution is not a solution at all. It’s a gamble and it takes up an enormous amount of time. I ended up nuking BeTheme after this because there was no way my I would hand off a product that my client couldnt edit. Building a custom theme using ACF made more sense. I still have one last client running BeTheme and I’ll phase out support for the theme eventually. How can I support something that doesn’t support me?
I feel for you. Impreza is a good theme. Great support too.
Good luck!
please understand that the theme itself has nothing to do with the defaul wordpress editor, we do not use it at all. Only VC plugin uses it to display their content.
Most times those support requests are not theme related and the main cause is either third party plugins or corrupted wordpress/theme files. This is why reinstalling wordpress and betheme is the best sollution, as well as disablin all plugins.
thanks