Hi Abtv,
Thanks for your help in debugging, I just wanted to remind you that this
is still very experimental code, hence the warning on the extensions page.

When you install either RTWiki or RTWysiwyg, it will install a websocket
component and realtime backend which require a wiki restart in order
to start working for the first time.

Please see this page for more information about the Websocket:
http://extensions.xwiki.org/xwiki/bin/view/Extension/WebSocket

Thanks,
Caleb


On 30/03/16 17:49, abtv wrote:
Unfortunately, I have the same problem with 1.7 under xwiki 7.4.2 (Jetty +
hsqldb):

CKEditor detected, loading realtime WYSIWYG code...
realtime-wysiwyg.js?cb=1459352454915:72 Creating realtime toggle
realtime-cleartext.js?cb=1459352454915:40 started
chainpad.js?cb=1459352454914:569
[xwiki:XWiki.Admin-Administrator%2d9873211570186842]  registered
realtime-wysiwyg.js?cb=1459352454915:183 Realtime is ready!
realtime-wysiwyg.js?cb=1459352454915:195 Readying new document
cursor.js?cb=1459352454915:10 [cursor.update] no ranges found
VM3618:1 Uncaught SyntaxError: Unexpected end of input

Maybe problem not in RTWysiwyg, but in its dependencies?

By the way, I'm understand it's bug in opensource project, but when I can
expect rtwysiwyg developer fix the problem? I use xwiki and I need to
provide some solution for collaboration or make some estimations. I checked
the link http://realtime.webviewers.org/xwiki/bin/view/Demos/RTSimpleWysiwyg
and these versions works pretty stable. It was almost 2 years ago, maybe I
can use old versions? With old editor/dependencies?





--
View this message in context: 
http://xwiki.475771.n2.nabble.com/How-to-run-RTWysiwyg-extension-not-in-demo-mode-tp7598488p7598738.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to