Version and installation profile numbering for Plone add-ons has been changing and this is very confusing. What worked in one version of Plone will not necessarily work in other places.
Gaer Baekholt pointed me to this page: http://plone.org/documentation/how-to/version-numbers-in-cmfquickinstaller
Related
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
I am trying to incorporate the add-on "ftw.blog" into my fresh 4.3.2 plone installation (on linux). As per the instructions, I have added "ftw.blog" to the eggs section of buildout.cfg. Then I ran /bin/buildout. This seemed to complete OK. Now. as per the instructions, I am to "install ftw.blog in portal_setup". But it is not obvious how to do so. Can anyone instruct me as to how to install ftw,blog in portal_setup? Thanks...
Most likely a typo, not 'portal_setup', but 'portal_quickinstaller', is the usual way to activate an add-on.
Go to http://somedomain.org:8080/yourPloneSiteId/portal_quickinstaller (via ZMI) or http://somedomain.org:8080/yourPloneSiteId//prefs_install_products_form (via Plonesite-UI), to activate the add-on.
You might want to inform the authors about it. If you do so, please leave a note about it here in a comment.
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.
We are running an old version of plone (Version 2.0.5). (We will migrate next year to plone 4)
I was trying to install the Plone Hotfix 20121106, but (as mentionened in the installing description), the hotfix will not apply to the version 2.0.5 of plone.
Questions:
Are the security vulnerabilites also relevant for the plone version 2.0.5?
Is there another way to install the hot fix on that old version of plone?
Some of the security vulnerabilities do apply to 2.0.5, yes.
However, there are other unpatched vulnerabilities in 2.0.5 not addressed by this hotfix, and you want to move away from this old a version as soon as possible. The Plone security team does not provide official support for Plone versions this old; currently 3.x and 4.x releases are supported.
You can unzip the hotfix into your Products folder, and it should just work. I believe people have tested it on 2.0.x installations already; the test coverage certainly was run on 2.1. You'll have to run your own tests though to make sure nothing (important) breaks for you when the fix is installed.
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.