I had a post out here with info about this before but it has gone completely missing - I got a response from Tristan about it and then the "read" button in that email response generated a 404 error to go to the page.
The short version is that there are problems with DropEditor and BreezingFroms as well as with JoomlaShine's PageBuilder.
The response from Tristan was (12/9/2015):
Now , the new 1.1 version is out and both problems still remain - the editor doesn't show up right in Page Builder when working with their "elements" and kind of blows out the look of the page on the admin side when trying to use PageBuilder, so what is supposed to make the editing easier looks completely confusing for the user because of display issues.
For BreezingForms, the editor shows up correctly in places where it's needed, but it doesn't save what's put in it. Even if just editing the text, it not only doesn't save it, it completely deletes it on save. Since the editor is used at a "global" level and we use BreezingForms on just about every site we build, it's not like I can just set BreezingForms not to use it - as it uses whatever the default editor is for the site. As a result, we can't use DropEditor at all.
I can't even look past these two issues because they make it completely unusable no mater how great it might be - and this is just on these two components...can't tell about others that might be affected since this is not based on TinyMCE (as JCE is) and really needs to be set as the default for the site to be useful at all.
I know I'm probably coming off as a complainer when this is a free component, but these have been reported and acknowledged, but apparently not having anything done about them at all in coming up on a year. Sad - because I like the simplicity and usefulness of the DropEditor.
Anyone have any thoughts or remedies?
The short version is that there are problems with DropEditor and BreezingFroms as well as with JoomlaShine's PageBuilder.
The response from Tristan was (12/9/2015):
Sorry for the late reply. We'll definitively take a look at that for the 1.1 version that is on the way.
For breezing form I'm pretty confident, for the page builder not sure because sometimes developers have the bad idea of calling in their component only TinyMCE editor based (JCE is based on Tiny MCE).
I let you know and install the latest version that includes the automatic updater so you'll get notified.
Now , the new 1.1 version is out and both problems still remain - the editor doesn't show up right in Page Builder when working with their "elements" and kind of blows out the look of the page on the admin side when trying to use PageBuilder, so what is supposed to make the editing easier looks completely confusing for the user because of display issues.
For BreezingForms, the editor shows up correctly in places where it's needed, but it doesn't save what's put in it. Even if just editing the text, it not only doesn't save it, it completely deletes it on save. Since the editor is used at a "global" level and we use BreezingForms on just about every site we build, it's not like I can just set BreezingForms not to use it - as it uses whatever the default editor is for the site. As a result, we can't use DropEditor at all.
I can't even look past these two issues because they make it completely unusable no mater how great it might be - and this is just on these two components...can't tell about others that might be affected since this is not based on TinyMCE (as JCE is) and really needs to be set as the default for the site to be useful at all.
I know I'm probably coming off as a complainer when this is a free component, but these have been reported and acknowledged, but apparently not having anything done about them at all in coming up on a year. Sad - because I like the simplicity and usefulness of the DropEditor.
Anyone have any thoughts or remedies?
Hi,
We took a look but it seems very complicated to handle as some component (not so much hopefully) are calling TinyMCE only as editors, in the code I mean. This is what we've talked about. And our editor is based on CKEditor. I"m sorry but it would be too hard and long for us to develop that. Of course if you're not happy with DropEditor I guess you find a compatible one
Cheers,
We took a look but it seems very complicated to handle as some component (not so much hopefully) are calling TinyMCE only as editors, in the code I mean. This is what we've talked about. And our editor is based on CKEditor. I"m sorry but it would be too hard and long for us to develop that. Of course if you're not happy with DropEditor I guess you find a compatible one
Cheers,
- Page :
- 1
There are no replies made for this post yet.
