Autosave doesn't seem to happen if the user keeps typing in a single text box.
For our customers this could be a problem as they may spend many minutes (10's of minutes) entering text into a large text or rich text area and they don't get any autosaving of that text. Is this expected behaviour or is it something to do with my configuration? I'm running version 2016.3 and my autosave configuration is <property as="xs:boolean" name="oxf.fr.persistence.cpf.autosave" value="true" /> <property as="xs:integer" name="oxf.fr.detail.autosave-delay.CPF.*" value="4000" />which should do a save every 4 seconds while changes are being made. I get the autosaves if I move between fields or out of the browser window and back in but not if I just keep typing into the text or rich text field. thanks. |
A little more info.
The rich text field does do the autosave after you type enter for a new line, then an autosave happens after the configured period (4 seconds in my case). The text field does not. You can type for a long time with newlines as well and there are no autosaves performed. |
Administrator
|
Hi Brian,
I suspect this is happening specifically with the Formatted Text Area, because it uses the TinyMCE, on which we register a `onchange` handler, and TinyMCE only calls the handler when you press enter, but not when you add characters to the current line. The solution here would be to use some other JavaScript handler, so we can know when the value changed. Conversely, if/when doing this, we'll need to make sure that we don't send the value to the server every time that event fires, as we don't want that control to be "incremental" by default. https://github.com/orbeon/orbeon-forms/issues/3179 Alex
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex,
Re-opening an old discussion... This problem has cropped up again for us. We are using the javascriptspellcheck (https://www.javascriptspellcheck.com/) as our spell checker for all text areas in a form. It links very neatly and easily into tinymce as well as the text and textarea elements in the form and gives us server side control over the dictionaries which is important for our application. The problem that we are seeing, and I think is related to this discussion, is that when the spell checker updates the text in the rich text editor, you can see the changes but when you save the form the changes are not saved. If you type an carriage return in the text editor then the changes are saved. Is there any way we can force the changes in the rich text editor to be saved on completion of the spell checking? thanks, brian... -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Hi Brian,
As you know, we've upgraded to TinyMCE 4. Orbeon Forms still uses the `onchange` handler, and ideally I'd expect that handler to be called "on change", whether the change originated from users typing in the field, or from the spell checker, and this might been fixed in TinyMCE 4. Did you get a chance to try this with a build of Orbeon Forms that uses TinyMCE 4? If not, I can certainly share one with you for that purpose. Alex ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex,
I can try this. TinyMCE 4 is in 2018.1? I would just need a build or are you releasing this soon? thanks brian... -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Brian, here is a nightly build from the CE branch, for you to test this.
You'll let us know if the new TinyMCE 4 helps (or on contrary creates new issues!). https://s3.amazonaws.com/orbeon-builds/orbeon/orbeon-forms/4350/4350.2/build/distrib/orbeon-2018.1-SNAPSHOT.201805230007-CE.zip Alex ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex,
I'm afraid I can't get the richtext area to work at all in this version. I tried an out of the box install of the orbeon war file in Wildfly 11 (after applying the fix noted in https://github.com/orbeon/orbeon-forms/issues/2798) and everything works except the rich text area. If I visit a form with an existing richtext control in it (say the orbeon/controls form) then the richtext editor in there seems to work OK. If i create a new form and insert a rich text control it looks OK in the builder but in test it doesn't show (its label does) and if saved and used it also doesn't show. If I edit the existing form (orbeon/controls) then the rich text editor doesn't show. Something in my environment? We are running java 8 and Wildfly 11 which works well with version 2017.* -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Hi Alex,
re my last message, anything I can try? I cannot get the rich text editor to work in the 2018.1 build you sent to the link for. thanks brian... -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Hi Brian,
Indeed… it looks like something we should take care of :). Sorry about that. I'll follow-up here once it is fixed. http://discuss.orbeon.com/No-autosave-when-focus-stays-in-the-one-text-field-td4662387.html Alex ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Administrator
|
For reference, this is tracked by:
https://github.com/orbeon/orbeon-forms/issues/3612 ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Administrator
|
Hi Brian,
Here we go: that issue is fixed, and the TinyMCE is now showing! Sorry for the trouble. You can download a new test build using the link below, and you'll let me know how it works for you. https://s3.amazonaws.com/orbeon-builds/orbeon/orbeon-forms/4366/4366.2/build/distrib/orbeon-2018.1-SNAPSHOT.201806112339-CE.war Alex ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Administrator
|
Brian, did you get a chance to try the new test build? If so, is everything
working for you with the TinyMCE? -Alex ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex, Not as yet. I've been fighting other issues with wildfly and domain
mode. Just got back to looking at this issue last night. WIll hopefully get somewhere with it today. thanks, brian... -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
In reply to this post by Alessandro Vernet
OK, Got to it this morning.
Now the changes made by our spellchecker are saved with the form. Updating with the new TinyMCE was a bit of work. First issue I found is to do with our custom configuration. The skin "thebigreason" is missing. I've updated our configuration to use "lightgray" for now, seems to be the default one that is included. The documentation at https://doc.orbeon.com/form-runner/components/rich-text-editor is out of date for this new version. I also had to make quite a few changes to our custom settings in TINYMCE_CUSTOM_CONFIG to get it to work and look as it did before. TinyMCE seem to have changed quite a bit in the configuration area. I had to add a few more plugins to get some of the toolbar functionality to work (plugins paste, lists and textcolor). What used to configure the toolbar, theme_advanced_buttons1, is now called just "toolbar1" and you need a space separated list of items in it (was comma separated). thanks, brian... -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. |
Administrator
|
Hi Brian,
Yes, the config changed quite a bit in TinyMCE 4 (as well as their JavaScript API). And i'm glad you managed to make everything work again, and that it fixes your problem. Alex ----- -- Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet -- Sent from: http://discuss.orbeon.com/ -- You received this message because you are subscribed to the Google Groups "Orbeon Forms" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email].
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Free forum by Nabble | Edit this page |