PluginTogether should replace the url associated with the Edit page button so that co-editors are automagically offered to go to the session with collaborative edition instead of the warning of edition conflict
- Status
- Closed
- Subject
- PluginTogether should replace the url associated with the Edit page button so that co-editors are automagically offered to go to the session with collaborative edition instead of the warning of edition conflict
- Version
- 18.x
21.x
22.x - Category
- Usability
- Feature request
- Community projects
- Dogfood on a *.tiki.org site
- Less than 30-minutes fix
- Feature
- Edit interface (UI)
- Resolution status
- Fixed or Solved
- Submitted by
- Xavier de Pedro
- Keep informed
- Victor Emanouilov, Marc Laporte
- Lastmod by
- Xavier de Pedro
- Rating
- Related-to
- Description
See first the box saying "Even better" below.
"PluginTogether should replace the url associated with the Edit page button so that co-editors are automagically offered to go to the session with collaborative edition instead of the warning of edition conflict" (was
"Clicking on PluginTogether on a wiki page should provide a CoEdit button next to Edit with the right url for all.")This would be useful for taking meeting minutes collaboratively in the TRM and TAG meetings, both which take precious time from some active tiki community members but with little time to do things properly (wasting precious time in this note-taking task instead of being able to invest it in other areas requiring their help too).
I've been trying to use tiki for many semester with my students at uni but I can't get them to use it with realtime collaboration with ease, so that they move to googledocs.This minor usability change would be probably enough to convince teams to use tiki realtime collaboration feature with plugin togetherjs.
Like ourselves when taking notes on a roundtable meeting, or tiki admin group meeting, etc.Even better
Even easier for the end user would be to just offer a user that sees the concurrent edition warning box, a link to carry on and convert the session into a togetherJS session in which both users continue writing together. In the backend, tiki would probably:- A new general preference should be added for this new behavior to be enabled
- when user A clicks at edit a wiki pageFoo, the url that would be created by PluginTogether is stored in tiki mysql tables somewhere, with a semaphore/flag or similar so that tiki knows that this page has been started edition and the url to allows others to go into the same edition session collaboratively.
- when user B clicks at the Edit button of the same pageFoo, while still being edited by userA, userB sees the warning of edition conflict unless userB accepts to request to userA to enter into the collaborative session.
- If userB accepts to request that coedition to userA, then UserA would see some warning about that request from userB in some popup/modal/or similar, with the option to accept and get his edition saved and restarted as online collaboration among both, or reject the request, and keep writing himself alone in that page.
- therefore, save the edition in place by user A (the one that started editing the page first)
- reopen that page for edition for user A with te url adapted to the togetherjs session, and
- send user B to the edition session with togetherjs (or alternatively, show userB the same link to open the page for edition).
- if userA accepted userB to write together, they both are working with TogetherJS on that page. And in that case, when other users such as userC clicks at edit the wiki pageFoo again, userA gets the same message requesting to confirm to accept new users getting the collaborative session, and when accepted, since the TogetherJS is already on, there wouldn't be any need to restart the edition session with togetherJs since it would be already in that mode.
This is currently partly working in 21.x LTS :
- user is sent automagically to open the session without "Warn on edit conflict"
- ... BUT the together session fails to display the other users being there editing the page concurrently:
- therefore, a new version is saved, without noticing that the versions will not be seen by each other:
Edit Conflict triggered.
- therefore, a new version is saved, without noticing that the versions will not be seen by each other:
To reproduce the updated problem info:
Come here with two different browser engines (or one in provate browsing and hte other in normal, as usual to test this feature):
http://xavi-9794-6160.show2.tikiwiki.org/tiki-index.php?page=HomePage
user1:
u: admin
p: 12345user2:
u: user
p: 54321- Click on button of the side module "Co-Write with TogetherJS"
- Edit homepage as user1 (admin) in browser engine1 (e.g. firefox)
- Edit homepage as user2 (user in browser engine2 (e.g. chromium)
- accept the popup asking to join session
problem triggered: none can see that the other user is editing the page, saving, moving elsewhere, etc.- Solution
- Fixed, while highlighter (codemirror) is disabled in the edit session (because codemirror is ocmpletrely disabled site wide, or because the users willing to co-write with plugin together they all click at "disable highlighter in the wiki page edit session) .
- Importance
- 9
- Easy to solve?
- 6
- Priority
- 54
- Demonstrate Bug (Tiki 19+)
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Accessing the Tiki instance that demonstrates this bugThe URL for the show2.tiki.org instance that demonstrates this bug is at: http://xavi-9794-6160.show2.tiki.org. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http://xavi-9794-6160.show2.tiki.org/info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
SnapshotsSnapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http://xavi-9794-6160.show2.tiki.org/snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Create new snapshot - Ticket ID
- 6160
- Created
- Wednesday 02 November, 2016 18:34:16 GMT-0000
by Xavier de Pedro - LastModif
- Monday 28 September, 2020 12:32:34 GMT-0000
Attachments
| filename | created | hits | comment | version | filetype | ||
|---|---|---|---|---|---|---|---|
| No attachments for this item | |||||||
;){kind=link}
;){kind=link}
- With Codemirror enabled or toggled Admins can't edit text-area field on doc.t.o
- Warning: strpos(): Empty needle in tiki-25.0/lib/cache/memcachelib.php on line 217
- Fatal error Uncaught TypeError in_array Argument #2 $haystack must be of type array, bool given in binderlib.php 49
- Remove version of wiki page fails
- Fatal error: Uncaught TypeError: in_array(): Argument #2 ($haystack)
;){kind=link}
;){kind=link}