topic Re: Inline editor error in Alfresco Archive

Inline editor error

lemmy — Mon, 28 Feb 2011 06:51:51 GMT

Hi,I've created an article in Alfresco 3.4.d Community. When using the inline editor to bold some words or to add an http-link it's just saving plain text. When I reenter the inline editor the changes are gone. There are no exceptions thrown.Thanks,Lemmy

Re: Inline editor error

foosetv — Mon, 07 Mar 2011 02:47:14 GMT

I just ran into the same bug, I can't get style changes to save either. The version number does escalate on each save but it doesn't seem to retain the change. I did get it to work if the LAST edit I make before saving is a character entry. So for instance, I'll will bold an existing phrase and then I would backspace out the last character and then re-type it. When I save immediately after that, the style changes seem to take. I haven't tried a change or addition to a hyperlink yet.

Re: Inline editor error

dsaum — Mon, 07 Mar 2011 22:12:58 GMT

I have been experiencing the same problem. Posted about it in the fall and got no meaningful response.

This seems to be a fairly significant issue and the lack of feedback Alfresco provides is worrying..

Re: Inline editor error

bremmington — Tue, 08 Mar 2011 09:59:43 GMT

I've been trying this out on the current code line (which is an Enterprise line), and I cannot reproduce it. After a little digging I've found that it was fixed under issue ALF-6002 which hasn't been merged from the Enterprise stream onto HEAD yet. It will get there…

Re: Inline editor error

foosetv — Tue, 08 Mar 2011 21:50:09 GMT

Glad this has been solved. I'll look forward to seeing it appear in the community version.

Re: Inline editor error

dsaum — Wed, 09 Mar 2011 15:01:37 GMT

Any idea when we can hope to see this show up in Community or in Subversion (or at least get a patch)?

For all intents and purposes this is a blocker issue for adoption of WCMQS (and by extension surf) as no content (minus no-frills text) can be created in the tool.

Re: Inline editor error

bremmington — Thu, 10 Mar 2011 07:32:30 GMT

I'm afraid I don't know exactly when the merge will be done from the enterprise code line onto head. If you are building Alfresco from source, however, the fix is quite simple. In the file "/projects/web-framework-commons/src/web/components/form/rich-text.js" do the following:

In the function "_renderEditor" (near the bottom of the file) subscribe to the "onChange" event in addition to the "onKeyUp" event:


         this.editor.subscribe("onChange", this._handleContentChange, this, true);
‍‍‍

In the "_handleContentChange" function, wrap the logic with a test for whether the editor is dirty so it becomes:


         if (this.editor.isDirty())
         {
            this.editor.save();

            // inform the forms runtime if this field is mandatory
            if (this.options.mandatory)
            {
               YAHOO.Bubbling.fire("mandatoryControlValueUpdated", this);
            }
         }
‍‍‍‍‍‍‍‍‍‍‍‍

Re: Inline editor error

dsaum — Fri, 11 Mar 2011 19:02:25 GMT

Fantastic. Thanks.

Re: Inline editor error

dsaum — Fri, 11 Mar 2011 21:05:12 GMT

I've deployed this patch and confirmed that it works. Thanks again.

Note for those who are stuck using 3.4.d or earlier, the fix that Brian included shows that editing the text in the <textarea/> is the only event that triggers an update of the underlying content model. A quick work around, therefore, is to simply make sure you edit some text after you click one of the TinyMCE buttons. I've confirmed that this works as well.

Re: Inline editor error

kamielvdz — Wed, 15 May 2013 12:36:00 GMT

I have experienced this exact same error in Alfresco Community 4.2.c. When I select a style or click a formatting button and click save, the content is not correct. If I click inside the editor again before I save, the cotent is saved correctly.

Re: Inline editor error

tchoupitoulos — Thu, 15 Aug 2013 03:27:48 GMT

We are actually seeing this on Enterprise 4.1.4 It doesn't sound like it really got fixed.

Re: Inline editor error

benswitzer — Tue, 27 Aug 2013 15:37:00 GMT

THANK YOU!!!

Was struggling with this for some time. Applied part one of this fix and the issue was resolved. It appears the second point has been fixed in the source.

Implementing a solution on 4.1.5.