[TYPO3-dev] Seperate Constant Editor for non-admins.

Stig Nørgaard Færch stig at 8620.dk
Tue Apr 25 16:25:48 CEST 2006


Stig Nørgaard Færch skrev:
> Stig Nørgaard Færch skrev:
>> Tomorrow I will probably release a stand-alone version of the 
>> "WebTemplate, Constant Editor" for non-admins.
> 
> I had some problems uploading the extension:
> Parse error: parse error, unexpected T_STRING in 
> /home/typo3_src/typo3_src-4.0/typo3/mod/tools/em/class.nusoap.php(5924) 
> : eval()'d code on line 1
> Fatal error: Cannot instantiate non-existent class: soap_proxy_206200614 
> in 
> /home/typo3_src/typo3_src-4.0/typo3/mod/tools/em/class.nusoap.php(5926) 
> : eval()'d code on line 1
> 
> Don't know if this is a known bug or not. Haven't had much time to look 
> for it in the bugtracker.
> 
> I run Typo3 4.0. But also tried it on RC2 (i guess) with the same result.

For anyone who might be interested, I got this ConstantEditor extension 
a lot further.
In the extension manager it's now possible to:
Filter access by category. This means that you can deny or allow access 
to different categories. If you deny a category, the rest will be 
accessible. If you allow a category, the rest will not be accessible.
There are two levels where you can filter access. The first one is a 
master settings, which means you cannot change it by user or page tsconfig.
The second one is more like a default or recommended setting, which you 
can override by user or page tsconfig.

The tsconfig is like this:
* mod.web_constanteditor.categories.allow = advanced,content
- this one will allow the advanced and content categories if they are 
not already filtered by the master setting.

* mod.web_constanteditor.constants.content.deny = 
content.defaultHeaderType,styles.content.links.extTarget
- this one disables the two constants content.defaultHeaderType and 
styles.content.links.extTarget from the content category.
If allow was used instead of deny, then only these two constants would 
be displayed.

I haven't had any luck on uploading this extension yet. But if anyone is 
interested, please just answer this thread.

/Stig




More information about the TYPO3-dev mailing list