Editing a WYSIWYG section in a page may leave the semaphore on the page after saving or cancelling the edit, due to a session bug exposed. This can be worked around by waiting the lock's expiration, or by editing the full page and using Cancel Edit.
The bug seems to occur only when session_storage is set to Database. File-based storage apparently does not trigger. When 2 concurrent AJAX requests are processed, changes to the session made by the first can be lost by the second request. Presumably, this is only true because the first request completes after the second one starts but before it ends.
The scenario where the WYSIWYG plugin exposes is that initiating an edit causes 3 AJAX calls to SemaphoreController:
Request 2 modifies $_SESSION to add a key storing a UNIX timestamp (on the pre-last line of action_set()). On a wiki page named "TestWYSIWYGPluginNoHTML", that key would be 'semaphore_TestWYSIWYGPluginNoHTML_ wiki_page'.
When cancelling (for instance), 2 requests are made. The problematic one is the call to unset. The call to $this->table->delete() in unset() fails because $lock is empty. $lock is empty because $_SESSION[$this->getSessionId($input)] evaluates to null.
This affects revision 65380 of trunk.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tikiwiki.org instance. To start, simply select a version and click on "Create show2.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tikiwiki.org.
The URL for the show2.tikiwiki.org instance that demonstrates this bug is at: http://. 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:///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.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tikiwiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|