[Typo3] Setup admin panel related edit panels

Troels Kjær Rasmussen troelsr at msn.com
Mon Aug 15 10:24:52 CEST 2005


1. First of all to answer your question....

styles.content.editPanelPage = COA
styles.content.editPanelPage {
  10 = EDITPANEL //THIS MUST BE CAPITALIZED
  10 {
# move,new,edit,hide
    allow = toolbar,move,hide
    label = Page: <b>%s</b>
  }

}

page.10 <  styles.content.editPanelPage

This brings up the editpanel for the page.

2. Regarding the lack of answers to your posts. Maybe you should try with 
another attitude. I shall not say wether it´s related to your language 
skills, but your questions and comments often comes across very unclear and 
critical. T3 is open source and you are welcome to modify and improve the 
parts of the code you would like to see work differently. If everyone else 
find your alterations nice, it would of course be incoorpated into the core 
at some point. However T3 is NOT a commercial product, that you´ve paid 
money for and thus can demand support for, so you´ll have to wait for 
someone to make an extension which fits your needs or wait until the core 
team comes around to FE editing as a part of the usability project (after 
v4.0 I think) if you are not able to code the thing itself (...and in that 
regard, modifying the corefiles would be the wrong way - extending the 
sourcecode via ux_classes would be the right way...)

NB:

I´ve worked with several enterprise-level CMS/CMF systems professionally - 
s.a. Vignette, MSCMS and Interwoven - and I can reveal, that they ALL 
require extensive programming skills from the webmasters as well the dev 
department to run in complex enviroments. Typo3 has the ability to become an 
fullbread enterprise-level system. The question is maybe more, wether you 
are able to handle enterprise-level or maybe should go check out systems 
such as webGUI or Mambo which have a less steeper learningcurve and are much 
more accessible for intermediate users/sites?

regards Troels Kjær Rasmussen

"tapio" <tapio.markula at dnainternet.net> wrote in message 
news:mailman.1.1124088247.7422.typo3-english at lists.netfielders.de...
> HI
>
>
> I tried to setup admin panel related edit panels, but I didn't get 
> defitions work. The base problem is what should be outside curly brackets?
> WHAT HERE
> {
> allow=toolbar,edit...
> }
>
> http://typo3.org/documentation/document-library/doc_core_tsref/EDITPANEL/
> doesn't tell it! It expects that the reader knows it without any 
> explanations and examples.
> I have tryed to quess what it might be
>
> #EDITPANEL.allow = toolbar,edit,new,delete,move,hide // didn't work
>
> I have even tried to redefine it on the base of some advice:
>
> editPanel >
> editPanel = COA
> editPanel {
>         10 = EDITPANEL
>         10 {
>                 label = allow = toolbar,edit,new,delete,move,hide
>         }
>
> page.20 < editPanel
>
> Which didn't work either.
>
> either this, which I made on the base of CSS Styled Content setup.txt
>
> styles.content.editPanelPage = COA
> styles.content.editPanelPage {
> #editPanel >
> #editPanel = COA
> #editPanel {
>          10 = EDITPANEL
>          10 {
>                #label.data = 
> LLL:EXT:css_styled_content/pi1/locallang.php:eIcon.page
>                #label.wrap = |&nbsp;<b>%s</b>
>                lable.wrap = |
>                label.data =
>                allow = toolbar,edit,new
>                # onlyCurrentPid = 1
>   }
>
>
> 'toolbar' here is extra six buttons for admin panel related individual 
> edit panels.
> BTW. Edit panel is poorly customizable - should be an option to disable 
> the header text (endeed easy to hide with CSS) and individual buttons in 
> the toolbar should have option in order to enable/disable them (for 
> example 'enable. toolbar.history' etc. - maybe there are such defitions). 
> Also skinning features are missing. I created skin folder edit panels.
> In over all frontend editing features are in Typo3 quite good using the 
> standard page module even if some buttons don't work (move up, move down, 
> hide and delete). Concerning TemplaVoila frontend editing doesn't work the 
> level, which commercial web sites expets. TemplaVoila is not yet ready for 
> really productive usage - it is still a test-level approach. Customizing 
> the standard page module, the layout can be ok for newbees. I have made a 
> request concerning missing skinning features.
>
> I have tried several time a proper answer - too difficult to answer? 





More information about the TYPO3-english mailing list