Bug #26899
closed
Normal Users are unable to move content elements from or to DB Mount point
Added by Muriel le Pair over 13 years ago.
Updated almost 10 years ago.
Category:
Backend User Interface
Description
Normal Users are unable to move content elements from or to DB Mount point.
(Works fine for Admin users).
1) attempt to move content element to DB Mount point
- select page where the content element in currently on > List > choose 're-position content element' (3th icon) > under 'Select position of the element' the DB Mount point can't be selected so it's simply not possible to move a content element to the root page.
2) attempt to move content element from DB Mount point to another page
- select the root page > List > choose 're-position content element' (3th icon) > under 'Select position of the element' nothing is shown.
If a user is doing exactly the same at any other page it all works fine.
No errors are displayed at any point.
- Status changed from New to Accepted
- Assignee set to Andreas Wolf
- Complexity set to easy
Would you be able to dig further into that, maybe with help from a Core Team member?
- Status changed from Accepted to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.5)?
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.5)?
I have the same problem in 4.7.18 when trying to move content elements from or to DB Mount point.
The reason is that the mount point page itself doesn't belong to its own root line (t3lib_BEfunc::BEgetRootLine) which is checked in move_el.php:
$GLOBALS['BE_USER']->isInWebMount($pageinfo['pid'],$this->perms_clause)
If you add this to the condition in move_el.php line 324 (TYPO3 4.7.18):
|| in_array($this->page_id, $GLOBALS['BE_USER']->returnWebmounts())
a content for move element is displayed and you can choose the move target. But the page tree displayed in the lower part of the page misleadingly starts on the parent page of the DB mount point.
I don't know if this happens in TYPO3 6.x, too.
I don't like to touch 4.5 and 4.7 as they are in maintenance only mode. So I'd like to close this issue.
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Andreas Wolf)
No feedback within the last 90 days => closing this issue.
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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by