Feature #18239
closed
I uploaded a Test-Plugin, that checks the patch:
T3X_sgtest_syslockedrecords_fe-0_1_0-z-200801181401.t3x
Place this plugin on a page and you can lock / unlock / test records.
Notes:
- Naturally it only works, if your are logged in to the FE !
- Open some content-elements in the BE (!) and let them open (!!)
- In FE: Enter tt_content and the UID of the content-elements that you just opend in the BE and click on 'check if record is locked' and see the ruslts
- In FE: Enter tt_content and the UID of a content-element and click on 'lock record' and check in the BE, if exclamation-mark ist set on these records.
- In FE: log in as ANOTHER user and check the same record: should be locked (if you check as the SAME FeUser, then you will not get a 'locked'-Message)
Uploaded new Version of Patch and Testing-Plugin after annotations of Oliver Hader.
Locking is now done with $TSFE->setRecordEditLock($table,$uid)
Unlocking is now done with $TSFE->removeRecordEditLocks($table,$uid)
Checking is now done with $TSFE->getRecordEditLockState($table,$uid,$information)
- this returns 1 if the mentioned record is locked only by the active feuser himself
this returns +1 if the mentioned record is locked by another fe/beuser
- this returns 0 if record is not locked at all
$information can be an array (then full information about all lock-records will be returned) or a string (then only a message-string is returned)
Prerequisite is always a logged in fe-user.
The patch is not yet in trunk.
- Category deleted (
Communication)
- Status changed from Accepted to New
- Assignee deleted (
Oliver Hader)
- Target version changed from 4.6.0 to 4.6.0-beta1
- Target version deleted (
4.6.0-beta1)
- Status changed from New to Closed
I consider this resolved?
In case I misunderstood the issue, please re-open it.
Also available in: Atom
PDF