Project

General

Profile

Actions

Bug #22271

closed

Editors don't delete items with sysext Recycler

Added by Mario Ramalho over 14 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Recycler
Target version:
-
Start date:
2010-03-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hello,

If an backend user delete an element with Recycler. The button delete is ok (I've added the tsconfig allowDelete=1).

After the click on the link, a popup appear => click yes

The result : The item isnt' deleted.

With admin account => all rights

Bests regards

(issue imported from #M13803)

Actions #1

Updated by Tommy Mhle over 13 years ago

no solution but a workaround.

change in file "class.tx_recycler_model_deletedRecords.php" on line 336

$tce->deleteEl($record0, $record1, true, true);

in

$GLOBALS['TYPO3_DB']->sql_query('DELETE FROM ' . $record0 . ' WHERE uid = ' . $record1);

Bests regards

Actions #2

Updated by Alexander Opitz over 11 years ago

  • Category set to Recycler
  • Status changed from New to Needs Feedback
  • Target version deleted (0)

The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #3

Updated by Andreas Siegel over 11 years ago

The issue still exists in version 6.1.1. An admin user is able to delete records from the recycler, but an editor backend user is not.

Actions #4

Updated by Alexander Opitz over 11 years ago

  • Status changed from Needs Feedback to New
Actions #5

Updated by Wouter Wolters over 11 years ago

  • Status changed from New to Needs Feedback

This looks like a duplicate of #34156 which is resolved now in 6.1.2, can you try if that works out for you?

Actions #6

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF