[TYPO3-dev] Disabling Parts Of TYPO3

Tapio Markula tapio.markula at xetpoint.fi
Fri Aug 17 09:07:40 CEST 2007


Benjamin Mack kirjoitti:
>>>  * 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.
needs to change TCA
> * Hide Web > Info > Translation Overview (maybe that's hidden anyway 
> when only one language exists)

Is there a way to disable default features? If not you must XCLASS,
where you add some configuration in order to disable default items.
BTW. I have tried to change this module but succeed just partial.
The most annoying feature in this module is that there is no way to 
configure, what information has been shown for example in 'Page tree 
overview > Basic settings.
The only thing, which I have succeed to change is list in page info box.
I have put possibility to change this list
$dfields = 
explode(',','alias,target,hidden,starttime,endtime,fe_group,no_cache,cach...

I just hate these kinds of hardcoded list - it is not a big task to 
allow configuration. If configuration is missing, then hardcoded list is 
used.


> * No way to add a Language by clicking on Rootpage (ID 0) when adding a 
> new record.
no idea how to disable but imo that is not important, because you don't 
need to do anything if you don't use several languages

> 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.
In fact I have the same problem

> 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.

I take generally be_users table from another installation and modify it,
when not so much task

>  * You mix up stuff (activate this field in that installation, forget 
> this field there etc. etc.).

agreed

> 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.

Well make an extension, which use condition in
ext_localconf.php and ext_tables.php (conditions defined in 
ext_cont_template.txt)

in ext_localconf.php

conditional XCLASSes/hooks to simply things

into ext_tables.php conditional sections to disable some fields

TS config for pages and ts config for users/user groups can be get from 
files.
You can define conditions, which files to use.

The problem is that some other extension might reset ext_tables.php. Put
'priority' => 'bottom' and install your extension last.




More information about the TYPO3-dev mailing list