let me know if anyone else, also having the same issue. it is working fine with older version but I just installed the latest version and now it's not working.
I have faced the same problem today in morning when I have updated WordPress to latest version 5.
But I have fixed the Problem by updating the Visual-composer back end-editor to latest version.
Check this link. You can see Release Notes there that says VER 5.6 - Update: Compatibility with WordPress 5.0.
So just update your plugin & sure that will fix your problem.
Try it & let me know if you have any issues.
Use the plugin call classic editor. It uses the old editor. Do not use classic editor addon. Just the standard classic editor plugin.
You can use Wordpress Version 4.9.9
It is working for me.
Download link
I can’t find Backend Editor, where is it?
The WordPress admin panel is a very unpredictable environment for such a complex product like Visual Composer. Because of that, we decided to remove Backend Editor in 2.0 version and focus our development on Frontend Editor. As a result, you as a user are getting a more stable and faster editor. Release cycles will become shorter and new features will be delivered to you faster.
To justify the “loss” we will introduce new “structured view” mode in Frontend Editor (similar how it was in the Backend Editor) and there is always Tree View mode available (a layer style representer and editor of your layout).
official website
Related
After upgrading Visual Composer from 4.1.3 to 4.7.4 (security update for the new XSS vulnerability) I see numerous shortcodes in "Backend-Editor"-Mode (the graphical/visual part). The shortcodes are editable when opening the container, they render fine in front end, so they should be a functional block in the backend; not a texted shortcode.
Among others, these are the most frequent: [text_output], [/text_output], [gap …], [vc_row_inner ..]
Any suggestions of what went wrong? I can reproduce this with around 5 installations, the themes author blames the deprecated theme version - but I don't see why: [vc_row_inner ..] was in 4.1.x and is in 4.7.x a valid shortcode for native VC..
I upgrade a Plone site from 4.2 to 4.3. The upgrade steps are basically:
running install.sh to have a 4.3 environment
copy Data.fs to var/filestorage and custom dexterity package to src
running upgrade in ZMI
Everything seems fine. But when I add/edit Page items, TinyMCE toolbar is missing for the body field. Only showing a Text Format dropdown. Note: I do see the toolbar trying to render (first 2 icons appear), but fail and disappear.
What am I missing? Any hints?
No definitive answers, but a few suggestions. I have 9 plone sites all running the same version of Plone (4.2) and have some where TinyMCE works flawlessly, and others where I can't make it work at all.
Check /portal_javascripts and make sure that you have ++resource++plone.app.jquery.js (I think you also need jquery-integration.js and ++resource++plone.app.jquerytools.js, but I may be wrong about those), as well as tiny_mce.js and tiny_mce_init.js).
check /portal_kss and ensure you have ++resource++tinymce.kss/tinymce.kss
check /portal_css for ++resource++tinymce.stylesheets/tinymce.css
I saw your edit about the toolbar beginning to display after I posted this response. You really need to use the development tools for your browser-of-choice (e.g. Firebug) and look at the console. If it starts to display and then fails to finish, there's sure to be an error in the console log.
Check to see whether you have outstanding upgrades to the Products.TinyMCE:TinyMCE profile in Upgrades in portal_setup via the ZMI. If there are any, run them and restart your Plone instance.
I had the same issue with the same version upgrades and there were outstanding upgrades. They must have been missed somehow, presumably a bug in the Plone upgrade process from 4.2.5 to 4.3.4.
FWIW, I just ran into this issue in an upgrade from 4.1 to 4.3.14.
In my case, the problem was that the site uses the Plone Classic skin instead of Sunburst. The Classic skin for some reason did not have the tinymce layer registered. The giveaway was that jquery.tinymce.js was registered in portal_javascripts, but marked in orange as (resource not found or not accessible). I grepped the buildout eggs and realized that jquery.tinymce.js lives in a skin layer of Products.TinyMCE-1.3.26. From there it was easy to figure out why it was not found.
I have a site running in DNN 6.0 . I upgrade the DNN verion 7. After Upgrade the Design the site is totally messup can any one give me the idea how to Update the DNN to verion 7.
Thanks
It's not necessary that the upgrade went wrong.
Maybe some of the modules you are using are incompatible with DNN7 or you have changed some of the core pages or styles.
It's hard to give a more precise answer since 'totally messed up' doesn't really say what's the problem
Posting the stack trace or error message would help a lot if you want a useful answer.
Often 'totally messed up' is due to a dll version issue.
On a side note, I hope that you have backed up both the database and website files before you upgraded the site. If you have added 3rd party modules, check their compatibility with DNN 7.
I had this problem too, you need to basically update the skins to use Gravity (or some other half-decent skin besides DarkKnight) - right now, it is probably using the old DarkKnight skin (I would guess) and I've seen a lot of issues trying to use DarkKnight in DNN 7.x.x.
Try this:
1.) Admin\Site Settings\Basic Settings\Appearance
2.) Set Site Theme\Container and Edit Theme\Container to Gravity (anything but DarkKnight)
3.) Host\Host Settings\Basic Settings\Appearnace
4.) Set Host Theme\Container and Edit Theme Container to Gravity (anything but DarkKnight)
I developed a website in wordpress and used several plugins. One of the plugin was http://wordpress.org/extend/plugins/background-manager/
Every thing was working fine on my machine. But as i get uploaded it to client server. the whole site stuck due to lower version of PHP. This plugin requires PHP 5.3 and on server we have PHP 5.2. Since its a shared server, we can't upgrade its PHP.
Then i look into the code of this plugin it was using PHP 5.3 feature namespaces. Is there any way to downgrade this plugin that it will work with PHP 5.2?
This is a really tricky problem, and of course, it's really, really bad practice to use old code for plugins as they may have fixed security vulnerabilities or other serious problems. It would be better for you to move the site to a server with more up to date PHP.
Having given that important warning, you can, however, browse to the tags directory in the plugin repository and extract the files you want for the previous version. Plugin history is public and always maintained.
For instance, for the plugin you mentioned, you can visit the SVN part of the plugin repository at:
http://plugins.svn.wordpress.org/background-manager/
You'll find the previous versions there under the "tags" folder, named after their versions.
Over the last year or so I tried using WP-CodeBox for a syntax highlighting tool. I downloaded a couple of versions and tried them with a few versions of WordPress. I have never been able to get CodeBox to work. Anyone suggestions? Anyone using this combination or have a similiar story? What did you do?
I like the features it offers like links to download files, line numbering, copy to clipboard, and expand/collapse of the code box. If there is another tool that offers these features, let me know.
WP-CodeBox - http://www.ericbess.com/ericblog/2008/03/03/wp-codebox/
I'd prefer to use CodeBox but if I can't make it work, I need to use something else. I cannot change the version of WordPress.
I've been using it successfully on my blog. I just upgraded to 1.4 which appears to have broken a few things so I downgraded back to 1.3.3. I'm currently using 1.3.3 with WP 2.8.6 & just upgraded to 2.9. Haven't had any problems with the 1.3.3 version. Just noticed on Eric's site that he recently released 1.4.1. Haven't tried it yet though.
lamolabs blog is my blog. I use the WP-Codebox all over the site without any issues.
I use it with WP 2.8.4 in production site and 2.8.6 at home, both working fine.
I've just installed on the same version and it's not working properly. It displays the code, but the collpase bar, images and line numbers don't appear. I'm going to have to hunt around for something else.