| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Plugins may want to add further fields to be present when saving drafts.
Plugins may want to execute some js functionality that should be timed to
the saved draft/refreshed lock.
If a plugin does another init() to attach the dw_locktimer to its own editor,
then the default callback would be added a second time, causing unexpected
and undesired behavior.
This includes the changes from the following commits:
6ef45cc1c69591eb7facf381ef4bcf88e3aaa1c0
6ca947f3ad455df4fca1a3076b174b7b2688bd89
0fff419cc95b9783dd33ab02ffb3bd7806d5fcde
87bed8b672a166d073948bcb4ca49aaa81dc880c
|
| | |
|
| | |
|
| |
|
|
|
| |
Since 80997d21e0aee9b8f27153000742ecd781f429f8 the date passed to the
draft save backend is indeed the page id, not the date.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
lib/scripts/edit.js
lib/scripts/locktimer.js
Some whitespace (at end of line) cleanup
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
The security token here doesn't improve the security as the other
requests that allow you to do the same thing aren't protected and I
don't see why locking or draft creation should be subject of XSRF
attacks.
|
| | |
| |
| |
| |
| |
| |
| | |
This disables lock and draft creation for pages the user can't edit. It
additionally adds a security token to the draft creation and deletion
request so - at least for logged in users - drafts can't be created,
modified or deleted so easily anymore.
|
| |/
|
|
|
| |
If no HTML element with the id wiki__text exists, locktimer.init led to a
JavaScript error.
|
| | |
|
| | |
|
|
|
I also adjusted the coding style to match our other JS classes
|
