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.
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 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)
It seems like lots of people are using xdv successfully so this must be something I'm not getting about xdv. I am running 4.0.3 on my local server (Mac). I have a xdv theme running in Plone (diazo.example.com) and I am trying to modify the styles. I can see my changes on apache and DW but they do not appear in Plone. I have debug mode on. I tried deactivating and activating the theme and emptying the cache. No luck, the site does not update. I thought it was 'easy' to make changes on-the-fly with xdv but this has me stumped. I didn't register the stylesheets in CSS registry. Is that a critical step or optional?
On another note, is it worth it to switch to diazo and plone.app.theming? What are the major benefits of doing so?
Thanks!
Elaine
I absolutely recommend that you switch to diazo and plone.app.theming. This is most easily done by starting with Plone 4.1.x instead of Plone 4.0.x. Get a copy at http://plone.org/products/plone/releases/4.1
Then, using buildout, install plone.app.theming. You may have a few issues with lxml, but since you've already done xdv I figure you've conquered that already.
Due to a problem I'm encountering with STS2.3.3.M2 and JUnit tests, I decided to try out the newest STS (v2.5.1RELEASE). I installed AccuBridge since Accurev is our version controller and I was trying to checkout a project from depot... except that my STS hangs when I try to select the depot.
Steps I did:
1. New > Project > Accurev > Checkout from AccuRev
2. Click Next
3. Pick either radio button and STS hangs
Nothing's wrong with any of my paths though. And, when I still try to connect with my older STS2.3.3.M2, I can still connect to Accurev. Btw, we're using Accurev 4.9...
Any ideas?
My assumption is that STS 2.5 is based on a vendor customization of Eclipse Helios 3.6, right? As of the 2010.2 plugin for Eclipse, it is not necessarily compatible with versions other than Classic Eclipse, especially vendor customizations. You may get some functionality, but not all. This is being worked on for the 2010.3 AccuRev plugin, so for now I'd recommend that you stay with the 2.3.3 STS.
Hope this helps!
Cheers,
~James
when i open .mxml flex file in eclipse it gives error
Could not open the editor: Assertion failed:
Does any one know about it
First of all you can give which operating System and version, IDE version, Flex plugin version, detail of error message. You can try ;
Check eclipse and flex plugin version compatibility if you use flex plugin. (If you use Linux operating system flex plugin compatible with eclipse 3.3 ide if not You can try to install flex plugin on eclipse 3.3 if you use 3.4 or 3.5 and so on)
You can download full package of flex ide instead of flex plugin on eclipse
I think its better to stop searching when you are in Flash and Linux. Here in this link its very much transparent. I tried all the fix provided out there, nothing did really worked what new comers are looking for.
Details: http://labs.adobe.com/technologies/flex/flexbuilder_linux/releasenotes.html#sysreq
Note: GUI will never work, which we are thinking and Autocomplete etc will also not work. So Flash and Linux is actually useless and time lose. The best thing is keep reporting Adobe for this. Because they are counting our Linux Vote.
Try changing your current workspace to another one, it helped in my case.
If you have disabled asking for workspace at startup you can change it here:
Window > Preferences > General > Startup and Shutdown
I just got the same error, after moving my project to a new computer. Turns out the build paths needed to be changed in the new computer. After updating those it seemed to fix the problem.
I struggled with this a couple of hours: my own "solution" to this was that I had Eclipse Galilieo / Weblogic 10.3.2 / Windows 7 set up correctly, but was accidently opening an old Eclipse Helios install pointed to the same projects. In other words yes, its likely a slight path difference or a new name for an updated resource along one of your paths. "assertion failed" is such a generic exception that you could get with so many different softwares, that I thought this input wouldnt hurt...