I installed the extension on most recent version of MediaWiki 1.19.2 and Etherpad Lite 1.1.4. The pad loads successfully into the wiki page. But the content and user info is not synced between the pad in the wiki and other regular Etherpad Lite sessions. Text I enter into the wiki pad does not appear in the other sessions. After reload the wiki page, all content changed in the wiki pad disappears, the content others have added in the meantime is loaded. However, chat works and is synced. Is this extension tested with Etherpad Lite 1.1.4? Any hint? --Ralfk (talk) 14:52, 26 October 2012 (UTC)
[SOLVED] Pad not synced
Problem solved by installation of recent EPL develop version.
What browser are you using?
Thanks for your response. I have used Firefox 16 for the wiki session (using Etherpad Lite extension) and Chrome 22 and/or konqueror for the 2nd session for testing. All under Linux. I have tested two different MediaWiki installation, both with same software level.
Oh, just tested it in opposite way: When using Chrome for the wiki session and Firefox for the 2nd "direct" session it works! The pad content is synced in both ways. So, why should Firefox behave different? However, Firefox is a must since this browser is used on most clients.
Konqueror from KDE 4.9.2 also works (within the wiki session). But Opera 12.02 does not work. Strange...
? Chrome works.
- clear all your caches (Ctrl F5)
- try Etherpad lite develop branch
Please can you
- try Etherpad lite branch develop ?
- try Firefox and Firefox browser combination
Firefox / Firefox combination does not work. The Firefox wiki session is always unsynced. Only chat and user list works.
I will try tomorrow to test with the development branch. Coming back later ...
the EPL extension only adds an iframe in the Wiki, so you can tra to extract this from the page source code and to try outside the wiki.
Firefox works now within iframe (wiki session) after checking out develop branch of Etherpad Lite, fix described at https://github.com/Pita/etherpad-lite/issues/1032. Thanks for your help!
Info: The actual master - corresponding to version 1.1.5 - contains the fix now.