Project

General

Profile

Actions

Feature #18239

closed

FeUsers in table sys_lockedrecords - TSFE-Part

Added by Stefan Geith almost 17 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2008-02-18
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

This patch-request contains 3 functions for $TSFE to lock, unlock and check for isRecordLocked also in FE.

This BT-Entry replaces Issue 4655 (http://bugs.typo3.org/view.php?id=4655)
and extends Issue 7571 (http://bugs.typo3.org/view.php?id=7571).

The appended Patch adds 3 function to class.tslib_fe.php that enable lock, unlock and check for isRecordLocked also in FE via $TSFE.
(issue imported from #M7572)


Files


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #16786: FeUsers in table sys_lockedrecordsClosed2006-12-14

Actions
Related to TYPO3 Core - Feature #18238: FeUsers in table sys_lockedrecordsClosedOliver Hader2008-02-18

Actions
Actions #1

Updated by Stefan Geith almost 17 years ago

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)

Actions #2

Updated by Stefan Geith about 16 years ago

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.

Actions #3

Updated by Chris topher over 14 years ago

The patch is not yet in trunk.

Actions #4

Updated by Xavier Perseguers over 13 years ago

  • 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
Actions #5

Updated by Xavier Perseguers over 13 years ago

  • Target version deleted (4.6.0-beta1)
Actions #6

Updated by Mathias Schreiber almost 10 years ago

  • Status changed from New to Closed

I consider this resolved?
In case I misunderstood the issue, please re-open it.

Actions

Also available in: Atom PDF