Feature #20556

Add TypoScript properties to enable the admin panel only on specific pages/typeNums

Added by Oliver Hader over 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Communication
Target version:
-
Start date:
2009-06-03
Due date:
% Done:

0%

PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:

Description

If in TypoScript the setting "config.admPanel = 1" is set, the admin panel will show on all pages in the frontend. If a specific page or typeNum is used to return XML or JSON data (e.g. for AJAX disposal), the admin panel would mix up these responses.

Of course it's possible to define conditions to avoid this - however it's a common task that should be solved without TypoScript conditions by new properties, e.g:

config.admPanel {
deny {
pages = 1,2,3
types = 100,101
}
// allow takes precedence:
allow {
pages = 10,11,12
types = 0
}
}

(issue imported from #M11254)

History

#1 Updated by Benni Mack over 10 years ago

Hey Olly,

why not just do TS conditions?

#2 Updated by Philipp Gampe over 10 years ago

because the you have do not have a clear setting...

it would just be more consistent

#3 Updated by Georg Ringer about 10 years ago

what is wrong with
config.admPanel = 0
page= PAGE
page {
config.admPanel= 1
}

or
config.admPanel = 1
xmlFeed = PAGE
xmlFeed {
typeNum = 1234
config.admPanel = 0
}

as said in http://typo3.org/documentation/document-library/references/doc_core_tsref/4.2.1/view/1/7/#id4354902
CONFIG > configuration for the page. Any entries override the same entries in the toplevel-object "config".

#4 Updated by Oliver Hader almost 10 years ago

Dropped

Also available in: Atom PDF