Project

General

Profile

Actions

Feature #54867

open

pagetype shortcut check for internal loop

Added by Philip Gutzeit almost 11 years ago. Updated over 4 years ago.

Status:
Accepted
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Start date:
2014-01-09
Due date:
% Done:

0%

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

Description

Would be nice to prevent an internal error when setting up an shortcut-page that points to itself. This might avoid some ugly error throwout and make it more obvious for normal editors. Simple solution/suggestion: make it impossible to select the page you are currently working on.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #86412: pages.shortcut suggest wizard should not suggest itselfClosedJosef Glatz2018-09-28

Actions
Related to TYPO3 Core - Bug #86600: pages.content_from_pid should not suggest itselfClosedJosef Glatz2018-10-09

Actions
Actions #1

Updated by Benni Mack about 8 years ago

  • Project changed from 78 to TYPO3 Core
  • Category deleted (Usability)
Actions #2

Updated by Riccardo De Contardi over 7 years ago

  • Target version deleted (TYPO3 6.2 LTS)
Actions #3

Updated by Josef Glatz about 6 years ago

  • Related to Bug #86412: pages.shortcut suggest wizard should not suggest itself added
Actions #4

Updated by Riccardo De Contardi about 6 years ago

Partially solved with #86412 - the suggest wizard skips the page itself; but it is still possible to select the same shortcut page as shortcut and save the record without errors or warnings.

Actions #5

Updated by Josef Glatz about 6 years ago

I could imagine:

A) Show an error via MessageQueue if the actual edited page record links to it self. This informs an editor

B) what about extending the Record Browser with an additional argument where the value could be N tablename_<uid> like pages_42? Those ids are then disabled in the record browser (greyed out for example with a nice title attribute)

Actions #6

Updated by Josef Glatz about 6 years ago

  • Assignee deleted (Philip Gutzeit)
  • Target version set to Candidate for patchlevel
Actions #7

Updated by Josef Glatz about 6 years ago

  • Status changed from New to Accepted
Actions #8

Updated by Josef Glatz about 6 years ago

  • Related to Bug #86600: pages.content_from_pid should not suggest itself added
Actions #9

Updated by Markus Klein about 6 years ago

I'd go with b)

Actions #10

Updated by Riccardo De Contardi over 4 years ago

I put here another idea: how about handling this with the link validator? Would it be a good idea or better not?

Actions #11

Updated by Susanne Moog over 4 years ago

  • Category set to Backend User Interface
Actions

Also available in: Atom PDF