[TYPO3-dev] Disabling Parts Of TYPO3
Benjamin Mack
mack at xnos.org
Fri Aug 17 00:46:17 CEST 2007
Hey,
well... I know that I can disable this for every installation for some
backend users. But what I want to do is:
+ remove a feature for every installation not by configuring at a
dozen of places but rather have one checkbox to get an installation up
faster
+ have it gone completely by just installing an extension, not just
hidden at one place for a specific user.
Tapio Markula wrote:
> Benjamin Mack
>
>> * Only the default language
> if no multiple language there is no language selectors. From normal
> users you take off language related tables out of use
Exactly. But for instance for disabling the languages feature, I'd like
a bit more:
* Translation cfg of pages removed when editing page properties (done
via Page TSConfig)
* Remove "Limit to Languages" feature when editing BE users.
* Hide Web > Info > Translation Overview (maybe that's hidden anyway
when only one language exists)
* No way to add a Language by clicking on Rootpage (ID 0) when adding a
new record.
That's why I want to make an extension that does that, to do all this
configuration for a installation that does not need languages -- I could
do this for every installation that I set up but I often I forget a
thing and with that every installation that does not use this feature is
in the same state.
> not currenlty possible, but is that so big task from admin to select
> just desired tables etc?
Of course it's not a big task for an admin --- but the "Access Lists" is
waaay too much and too detailed to get this up as an admin.
And:
* If you need to do this for a couple of installations, it IS a big,
always similar and recurring, annoying task.
* You mix up stuff (activate this field in that installation, forget
this field there etc. etc.).
I think this is absolutely not usable for a non-TYPO3-guru who just
wants to set some basic permissions for Backend users. I know you can do
it and I can do it, but it just came to our mind a couple of days ago
where I explained the Backend groups and the guy I explained TYPO3 said:
"Ok, this is the part where it just goes way too deep". Of course, it's
great to have everything configured but for most of my installations I
need a basic configuration setup. This is why I want an easy way to
disable / enable features.
greetings,
benni.
-SDG-
More information about the TYPO3-dev
mailing list