Added one option to get both the standard pages module and TemplaVoila working in the same installation.
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
mod.SHARED.new_content_wizard | string | Makes possible to use two different content element wizard, another for the standard page module and another for TemplaVoila. Possible values: standard and TemplaVoila. If invalid value has been set, the definition has been ignored. In order to work need 'enable.febeuserauthentication' and 'enable.list' enabled. Normally TemplaVoila overrides the standard content element wizard, when in practice the standard page module can't anymore used. This TS allows to use in one branch full working standard page module and in another branch TemplaVoila, when it is easy to test alternatives. |
In the first screenshot the following features has been disabled with this default TS Config:
mod.web_layout {
disableSearchBox=1
disableAdvanced=1
disableBigButtons=1
noCreateRecordsLink=1
}
options.shortcutFrame=0
options.mayNotCreateEditShortcuts=1
Everything disabled/changed in the screenshot can be set with extended TS Config for users/users groups.
Added generic module configuration features:
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
options.disableHelpModule | boolean | Disables the help module (works if [enable.allow_disable_helpmenu] has been enabled). | 0 |
setup.override.allowAdminFunctions | boolean | Allows for non-admin users admin functions to clear BE and FE cache (works if [enable.allow_disable_helpmenu] has been enabled). | 0 |
For the admin panel has been added following options:
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
disableToolbarButtons | string | Like disabling buttons from the toolbar in frontend editing in mod.FE_BE but this options disables entire sections; comma separated list and possible values are: page_section, content_section, media_section, advanced_section and miscellaneous_section. | |
disableFlexformEditIcon | boolean | If the plugin ''templavoila' has been installed, this option makes possible to disable edit icon from the top left corner of the page, when edit icons in the frontend editing has been enabled (this edit icon relates with flexform fields of TemplaVoila). | 0 |
disableEditIcons_tt_content | boolean | A shortcut to disable edit icons from tt_content records but leave them for other records. | 0 |
hideEnableAdmPanel | boolean | The new edit menu needs the functionalities of admin panel and 'hide=0' should not be used. In order to visually hide the admin panel, a new option has been added to hide the normal admin panel, when only admin panel related menu is visible. | 0 |
disableUserSetup | boolean | At this moment it is possible to control usage of pop-up windows in front end editing with an option in User > Setup. This option disables this possibility. | 0 |
showFeEditingWithTabs | boolean | If extra tab bar has been used, normal frontend editing icons are visible | 0 |
module.edit.reloadOnEdit | boolean | That is for editing individual content-related records. When the save button has been pressed, the open window will be reloaded. Then it is possible to see changes immediately. You may need to press the save button twice. This has effect, when in the TS Config for users/user groups has been set 'module.edit.forceNoPopup = 0'. Note that also extra toolbar buttons to open pop-up windows. | 0 |
Notes:
Admin panel must be enabled in your TS template. Put 'config.admPanel=1' to any TS Template in the setup field.
In the '/res/' folder is 'close.html', which can be put into the '/typo3/' folder. When using the Save and close or 'Close' button the opener window will be reloaded. When you have edited a content in pop-up-window, you can see changes, when you close the pop-up-window.
Mod.SHARED has also some following user/user group related options:
Property: | Datatype: | Description: | Default |
|---|---|---|---|
extraTabBar | boolean | Adds additional tab bar for page module and for frontend editing editing for editing page, page overlay and content records. Adds the tab set (main tabs are Contents, Properties and Preview) into backend for Web > Page and Web > View modules. Enables switching between seeing content elements in the page, page properties and preview of pages. When individual content element has been edited, this set is visible. Supports both the classic page module and TemplaVoila. Below screen capture, if used with skin_grey_2 and extra tabs.
| 0 |
allowShowTabBarInWebView | boolean | Adds tab bar also for Web > View module | 0 |
Note. Look at also manual for tm_shared_lib, which explains some extra shared option.
'Mod.web_layout' has been extended with the following new options (note that some of them relate with 'skin_grey_2'):
Property: | Data type: | Description: | Default: |
|---|---|---|---|
Common for all modes | |||
disableUserSetup | boolean | Controlling from User > Setup disabled | 0 |
disableTopEditIcon | boolean | Disables the icon 'Edit Page Header' on the top-right corner of the view | 0 |
disableFuncMenu | boolean | Disables the function menu on top (see below mod.web.layout.menu.function). | 0 |
textTopFuncMenu | boolean | Instead of SELECT-menu top menu on the right use text buttons. This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | 0 |
disableLangMenu | boolean | Disables the language menu on top left. | 0 |
For 'Columns' , 'Languages' and 'Page information' modes | |||
disablePathInfo | boolean | Disables the path info. This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | 0 |
For 'Column' mode only | |||
disableToolbar | boolean | Disables the whole toolbar , which is below the path info. | |
disableAJAX | boolean | If AJAX for backend has been allowed it can be disabled from some users/ user groups. | 0 |
disableToolbarButtonsColView | string | Disables buttons from the toolbar; comma separated list and possible values are: history, new_contentelement, move_page, new_page, edit. | |
disableEditWholeColumn | boolean | Disables the 'Edit this column' button for editing all content elements of the column. | 0 |
toolbarIconMode | integer | Alternative style for toolbar icons (look at styles from topNewIconMode). This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | 0 |
topNewIconMode | integer | Alternative style for icon to create a new content element to the top of columns (0 = icon only; 1 = text only; 2 = icon left text right; 3 = text left icon right; 4 = icon left text right and they can be set with CSS to look like a button (like in the screen capture below). This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. If used personal setup all action links has the same style. | 0 |
editColumnIconMode | integer | Alternative style for possible edit whole column link on the top of columns (look at styles from topNewIconMode). This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. If used personal setup all action links has the same style. | 0 |
topPasteIconMode | integer | Alternative style for possible paste link on the top of columns (look at styles from topNewIconMode). This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. If used personal setup all action links has the same style. | 0 |
totalWidth | integer | Sets mimimum width for each columns | 153 |
disableBigbuttonSet | string | Disables individual buttons if the option showBigButtons is enabled (added because the option showBigButtons is too rough); comma separated list and possible values are: edit_page, edit_pageoverlay, move_page,new_page,new_content,edit_rte,new_if_nocontent. | |
disableColViewEditingButtons | string | Disables editing buttons; comma separated list and possible values are: move, new, hide, delete, copy, cut, paste, clear_clipboar (edit is not possible to disable because it is not reasonable to hide). Note. The value 'clear_clipboard' relates with an extra button, which clears the clipboard and takes of paste links, because it is not obvious how to take them off. Paste links can be taken off also clicking the same copy link twice and if that is known the extra button is not necessarily needed. Pasting after cutting operation, paste links dissappear automatic. | |
editIconMode | integer | Alternative style for edit icons inside each columns (look at styles from topNewIconMode). This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. If used personal setup all action links has the same style. | 0 |
disableInfo | string | Makes possible to define, what extra information will be hided; comma separated list and possible values(field names) are: sys_language_uid, ctype, date, hidden, starttime, endtime, fe_group, spacebefore, spaceafter, section_frame, sectionindex, linktotop (note that field names are in lowercase'). | |
combineInfo | boolean | Extra information has been put into the same row if possible without extra line breaks. This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | |
infoBelowElement | boolean | Puts some content element related information after the sample text of the content element (for example date, index and hidden). This can be controlled also from personal setup if not explicitly disabled with the option disableInfoBelowElement or disableUserSetup. If personal setup is allowed it takes precedence over this value. | 0 |
disableInfoBelowElement | boolean | Disables the possible info below content elements (meaningful only with the above option – 'disableInfo' is not needed). | 0 |
TemplaVoilaStyle | boolean | Makes individual content elements in the Columns view resemble as much as possible TemplaVoila. Ctype information is among the sample text. Button creating new content elements after existing content elements is after the sample text. This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | 0 |
extraHeaderInfo | boolean | If the previous option has been enabled makes possible to add some extra infromation, if the header is empty or it is hidden. | 0 |
headerLenght | integer | Maximum width for the header, when TemplaVoilaStyle has been set (prevents headers wrapping into several lines. | |
For 'Quick Edit' mode only | |||
ElementSelectorRight | boolean | Positions the element selector on the right side of buttons. This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | 0 |
disableElementSelector | boolean | Disables the element selector. | 0 |
disableToolbarButtonsQuickEdit | string | Disables buttons from the toolbar; comma separated list and possible values are: save, save_close,delete, undo, edit, history, new_contentelement, move_page, new_page, edit. | |
toolbarQEIconMode | integer | Alternative style for toolbar icons (0 = icon only; 1 = text only; 2 = icon left text right; 3 = text left icon right; 4 = icon left text right and they can be set with CSS to look like a button. This can be controlled also from personal setup. If personal setup is allowed it takes precedence over this value. | 0 |
disableRTEcheckbox | boolean | Disables the checkbox to select if RTE can be disabled. | 0 |
disableLinkQEMoveRecord | boolean | Disables the link (on the bottom of the view) 'Move Content Element'. | 0 |
disableLinkQENewRecord | boolean | Disables the link Create New Content Element''. | 0 |
Notes.
I have added possibility to enable/disable big buttons in columns view using personal user setup. That overrides 'disableBigButtons' if 'disableUserSetup' is not '1'. By defining disableBigButtons can set the default value before any personal user setup has been saved.The same concerns also other options, which can control by personal user setup. Even if they normally override TS Config for users/user groups it might however be reasonable to define default values using TS config for users/user groups.
The following setting doesn't disable the Quick Edit mode:
mod.web_layout.menu.function {
0 = 0
}
It must be set:
mod.web_layout.menu.function.0 = 0
I have extended TS Config 'mod.xMOD_alt_doc' with the following new options:
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
newContentAsDefault | boolean | If new page has been created, also new content element for the pages has been created. Supports 'TCAdefaults.tt_content...' for header, CType (content type) and colPos using either in TS Config for pages or users/user groups. For TemplaVoila there is also a pseudo-field 'field_index', which is important, because without setting proper value, new element would be put into unused element. The value is the same as found in template, for example: <field index="field_maincontent">. The correct setting for this is: TCAdefaults.tt_content.field_index=field_maincontent | 0 |
usePageTitleForHeader | boolean | If new content element has been created automatic, the header for the new content element is the same as the title of the page. This setting overrides 'TCADefaults.tt_content.header' | 0 |
disablePathInfo | boolean | Disables the path information | 0 |
disableLangSelector | boolean | Disables the language selector for Typo3 4..x | |
disableAlt_docBEButtons | string | Disables buttons from the toolbar in frontend editing; comma separated list and possible values are: save, save_view, save_new, save_close, delete, undo, edit, history. | |
disableAlt_docFEButtons | string | Disables buttons from the toolbar in backend editing; comma separated list and possible values are: save, save_view, save_new, save_close, delete, undo, edit, history, full_form. | |
disableRTEcheckbox | boolean | Disables the checkbox to select if RTE can be disabled | 0 |
disableDescriptioncheckbox | boolean | Disables the checkbox to select if descriptions has been shown. | 0 |
toolbarItemType | boolean | Type, which kind of icons has been used as task links. If the type is '1', the name of icons must have language code, for example '_de' before the '.gif' file extension. Look at from '/gfx' folder, what images are needed. | 0 |
ownToolbarButtonMainPath | string | Main path for own taks icons, if they have been used. Note that images must put sub-folder '/gfx'. |
If the property 'disableAlt_docFEButtons' has the value 'full_form' instead of icons there is a text link on the bottom of the view – see the screen capture below:
Note. In the screen capture you see limited set of fields – I have redefined 'css_styled_content' in a TypoScript template. If you want to create Typo3 Lite you must also check which fields you can drop, when editing records by opening them using edit icons. Below is an example script:
# *****************
# CType: header
# *****************
lib.stdheader.stdWrap.editIcons = tt_content : header, [header_layout]
In my mind TemplaVoila has some confusing icons and sidebar items for newbies. That's why I added for module 'mod.web_txtemplavoilaM1' new properties, which give possibility to customize editing icons. Also some other options added (many options comes from a customer project and I have not listed some options):
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
disableEditViewEditingButtons | string | Disables buttons from the TemplaVoila's editing view; comma separated list and possible values are: copy, cut, ref, paste,unlink. Note. If 'unlink' has been put to the list also 'Non-unused elements' have been take off from the editing view. | |
enableEditViewEditingButtons | string | Enables some special buttons; comma separated list and possible values are: new_page. | |
disableSidebarItems | string | Disables sidebar items; comma separated list and possible values are: versioning, localization, headerFields, nonUsedElements, advancedFunctions (supports automatic new options). | |
editIconModeTemplaVoila | integer | Link mode for content element related links. Normally 0-4. They are primary the same values as for the 'Columns' view of the classic page module – look at that list. In addition as a new option possibility to use SELECT-menus. | 0 |
newTarget | boolean | New target, if content element wizard points to IFRAME in the same page instead of going to a completely new page. | 0 |
allowContentForShortcut | boolean | Allows puts content elements for page type 'shortcut'. | 0 |
limitToRootlines | string | Allows limit the previous option to some brances. Comma separated list of pages. | |
oneContentEl | boolean | Doesn't adds new record link to a content area, which already has at least one content element. | 0 |
disableCSH | boolean | Disables text 'What is TemplaVoila module?' + related icon. | 0 |
TemplaVoila doesn't offer very good front end editing features, but tm_contentaccess improves them. Tm_contentaccess offers well working frontend editing, when the standard page module has been used and TemplaVoila has not been installed.
TS Config has been extended creating a new pseudo module name 'mod.FE_BE', which relate to frontend editing. The module is pseudo because this plugin doesn't install any real BE module. It relates closest with 'Web > View' module, which has the module configuration 'mod.web_view' - in fact the another alternative was just add new options to the mod.web_view module configuration because definition, which have been done in mod.FE_BE affects to that module. But because frontend editing is its own kind of view and mod.FE_BE affect to that too, I made a new pseudo module configuration. Mod.FE_BE give user/user group level access control for edit panels for frontend editing and in the Web > View module.
With extra TS Config for users/user groups you can disable individual buttons from edit panels. You can also set some working modes.
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
Extra toolbar buttons | |||
disableToolbarButtons | string | Disables buttons in extra edit panel or edit menu in frontend editing; comma separated list and possible values are: history, edit, new_page, move_page, history, new_contentelement, list, dam_file, dam_upload, dam_index, media_file, imagelist, help_about, open_backend, logout These settings don't concern the possibile admin panel on the bottom of the page (they concern only extra toobars for edit panels). Note. Made a change. In older versions 'new_record' meaned content elements. Note. Either 'dam' or the default file manager can be active. | |
enableSpecialToolbarButtons | string | Enables some as default hidden option.; comma separated list and possible values are: web_info, access, functions, column_overview, tv_page_module, new_record, user_setup Note: 'access' works only for administrators and ' tv_page_module' needs plugin 'templavoila' installed. | |
disableNavFrame | boolean | Media folders and list module use normally navigation frame on the left, but this can be disabled. | 0 |
uploadFolder | string | If navigation frames has been used for normal media folders can set folder name, which is relative to the 'fileadmin/' folder. | |
imageFolder | string | If navigation frames has been used for normal image folders can set folder name, which is relative to the 'fileadmin/' folder. | |
toolbarMode | integer | Alternative style for toolbar icons (0 = icon only; 1 = text only; 2 = icon left text right; 3 = text left icon right ; 4 = icon left text right + possible to format like a button (see 'topNewIconMode'); this setting doesn't concern the possibile admin panel on the bottom of the page (concerns only extra toobars for edit panels). | 2 |
toolbarModeAdmPanel | integer | Alternative style for toolbar icons for admin panel on the bottom of the page (look at possible options above). | 0 |
Edit panel buttons/options | |||
panelToolbarDisabled | boolean | Disables the entire toolbar. | 0 |
disablePanelButtons | string | Disables buttons from the edit panel in frontend editing; comma separated list and possible values are: edit, move, hide, new, delete. | |
panelLabelLeft | boolean | Puts the label on the left side of icons. | 0 |
panelLabelDisabled | boolean | Disables the label text of the edit panel. | 0 |
labelLength | integer | Maximum length of the label. | 50 |
panelBlacklineDisabled | boolean | Disables the entire blackline above the edit panel. | 0 |
editPanelMode | integer | Alternative style for normal edit panel icons (0 = icon only; 1 = text only; 2 = icon left text right; 3 = text left; 4 = icon left text right + possible to format like a button (see 'topNewIconMode'). | 0 |
Edit Icon options | |||
editIconMode | integer | Alternative style for edit icons (0 = icon only; 1 = text only; 2 = icon left text right; 3 = text left icon right; 4 = icon left text right + possible to format like a button. | 0 |
editIconBELanguage | boolean | As default titles of edit panel icons base on the language of the page. With this options it is possible that the languageof title attributes base on the language of the backend interface. Then titles for edit panel icons and edit icons use the same language. | 0 |
Notes.
You can control edit panel button sets with the following TS in some TypoScript template (setup-field). These settings defines the basic possibilities, which editing possibilities are available. Below is list, which offers maximal quantity of buttons:
#As default the option 'toolbar' is not in the list in the setup.txt of the CSS Styled Content
styles.content.editPanelPage.10.allow = toobar.edit,new,move,hide,delete
# if you use frontend clipboard you can add cut,copy,paste,clear_clipboard options
# ...allow = toobar.edit,new,move,hide,delete,cut,copy,paste,clear_clipboard
tt_content.stdWrap.editPanel.allow = toolbar,new,edit,move,hide,delete
Because standard edit panels don't support 'colPos' field I added a new feature 'colPos' for the 'EDITPANEL' object (this is for TypoScript templates, not for TS Config of users/user groups):
20=EDITPANEL
20l {
newRecordFromTable=tt_content
#if the table is tt_content the new content becomes with the setting below to the column 'RIGHT'
colPos=2
allow = new
label =
}
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
colPos | integer | If in frontend has been defined individual edit panels for several columns, it is possible to set correct 'colPos' value for edit panels in each column. | 0 |
For the 'List' module here is the following extra interface controls, which relate to the module 'mod.web_list' and new record wizard (improved list module must be enabled):
Property: | Datatype: | Description: | Default: |
|---|---|---|---|
Top Menu | |||
disableListmoduleTopIcons | string | Disables buttons from the top of the view ; comma separated list and possible values are: edit_page, new_record, hide, move_page, clear_cache, csv , export. | |
Items | |||
disableListmoduleMainIcons | boolean | Disables buttons from the lists; comma separated list and possible values are: show, edit, history, version,perm, new_record, hide, move, hide, delete, levels, copy, cut. | |
Other options | |||
listmoduleShowClipboardDisabled | boolean | Disables the possibility to use the clipboard. | 0 |
listmoduleShowLocalizationDisabled | boolean | Disables the possibility to use localization options. | 0 |
listmoduleSearchBoxDisabled | boolean | Disables the search box. | 0 |
listmoduleMenuBoxDisabled | boolean | Disables the possibility to select extra fields from a menu box. | 0 |
limitedPositionTree | boolean | Shortened list of pages, when used 'Create new page' wizard. Note that 'enable.allow_shorted_page_wizard' must be enabled. | 0 |
An example TS Config for users/user groups:
admPanel {
enable.all=1
module.edit.forceNoPopup = 0
module.edit.forceDisplayIcons = 1
module.edit.forceDisplayFieldIcons=1
hide=1
}
mod.web_layout {
disableTopEditIcon=1
disablePathInfo=0
disableToolbarButtonsColView=history,new_contentelement
disableToolbarButtonsQuickEdit=history
disableColViewEditingButtons=
disableElementSelector=0
elementSelectorRight=1
disableToolbar=0
disableNewContentElementWizard=0
disableBigButtons=1
toolbarIconMode=4
editColumnIconMode=4
topNewIconMode=4
topPasteIconMode=4
editIconMode=4
disableSearchBox=0
disableAdvanced=0
noCreateRecordsLink=0
}
mod.xMOD_alt_doc{
$disableAlt_docBEButtons=save_new
$disableAlt_docFEButtons=save_view,full_form
disablePathInfo=0
disableDocSelector=0
disableCacheSelector=0
}
mod.web_list{
listmoduleShowClipboardDisabled=0
listmoduleShowLocalizationDisabled=0
listmoduleSearchBoxDisabled=0
disableListmoduleMainIcons = history, levels, cut
}
mod.FE_BE{
panelLabelLeft=0
panelLabelDisabled=1
disableToolbarButtons=history,move_page,list
disableEditpanelButtons=hide,delete
toolbarMode=2
editPanelMode=0
editIconMode=0
labelLength=15
}
When installing the plugin, there are possibilities to tailor the plugin. If you want immediately to use new edit panel for frontend editing, you can enable it from 'Enable features' > 'enable.addEditPanel'. Define at least at the same time 'enable.logoutId', if you know, what it could be.
Enable also 'enable.preset' or alternatively install also the plugin 'conf_userts' in order to active frontend edit panels.
Alternatively you can afterward install it from 'Include static templates (from extensions)' . In both cases this plugin defines object ''editPanel' and related CSS-files for that object (CSS-files has been stored in two CSS-files in the folder of this plugin). As default the new object has been put to the top of the page.
If you use the latter method, you need afterward to define at least the constant 'logoutId', which defines which page you return to, when you click the 'Log out from CMS' link. Below is the default setting in '/pi1/static/constants.txt' of this plugin (I added some comments).
# you can redefine labels
leditPanelSetText=Toolbar:
logOutText=Log out from CMS
# 'logoutId' must be always defined
logoutId=0
# you must define 'subFolder', if Typo3 has been installed into a sub-folder
# put forward slash before the name of the possible sub-folder, for example 'subFolder=/cms'
subFolder=
# object for the toolbar - this setting put the edit panel to the top of the page
FEtoolbar.object = page.1 < editPanel
# if you set this as empty you can elsewhere refer to the object 'editPanel', for example
# subpart.editpanel < editPanel
# CSS-file for the toobar (if changed, the changed file can have all CSS needed for frontend editing)
# must reset if this plugin has been installed as global
# if enable.addEditPanel has been enabled, also global installation works
# because the path has been defined dynamically
CSSFileForFEtoobar=typo3conf/ext/tm_contentaccess/fe-buttonset.css
New class-attributes
This plugin adds following classes for buttons, which are created by '/typo3/alt_doc', which is used in FE editing and editing records in Columns' view:
Title/purpose | Classes for Frontend Editing | Classes for Backend Editing | |
|---|---|---|---|
Big buttons | |||
Save document | savedok-fe | savedok-be | |
Save document and view page | savedokview-fe | savedokview-be | |
Save document and create a new one | savedoknew-fe | savedoknew-be | |
Save and close document | saveandclosedok-fe | saveandclosedok-be | |
Close document | closedok-fe | closedok-be | |
Delete | deletedok-fe | deletedok-be | |
Undo/redo last change | undo-fe | undo-be | |
Show history | N/A | showhistory | |
Edit whole record | fullform | N/A | |
Select menus | |||
Document selector | docSelector docSelector-fe | docSelector docSelector-be | |
Cache selector (for container SPAN) | cacheSelector cacheSelector-fe | cacheSelector cacheSelector-be | |
Checkboxes (container DIV) | |||
Class for the parent element of all checkboxes | alt-doc-bottom-controls | ||
Show secondary options (palettes) | alt-doc-show-palettes | ||
Show field descriptions | alt-doc-show-description | ||
Disable Rich Text Editor (RTE) | alt-doc-disableRTE | ||
Links on bottom (container DIV) | |||
Create a shortcut to this page? | alt-doc-shortcutlink |
This plugin adds new classes for buttons, which are created by '/typo3/sysext/cms/layout/db_layout.php' and '/typo3/sysext/cms/layout/class.tx_cms_layout.php', which are used in editing records in 'Quick Edit' mode and showing columns in the 'Columns' view (the list will not necessary be comprehensive, because I might have added some new classes after making this list):
Title/purpose | Classes for Backend Editing |
|---|---|
Top menus and toolbars | |
Top function menu table | topFuncMenu / topFuncMenu topFuncMenuQuickEdit + longTable (for Quick Edit with certain toolbar modes) |
Page header info cell for top function menu | topFuncMenuHeader |
Mode select menu for top function menu | topFuncMenu |
Select menu for languages | topFuncLanguages |
Edit icon in top function menu | editIcon |
Toolbar for top funtion menu (Quick Edit) | topFuncMenuToolbar |
Path (text 'Path:') | pathInfo |
Full path | db_layout-page-header |
Whole Columns view | |
Wraps for main elements | div.colWrap, div.contentWrap, div.ul.sortable, leftMargin, spacerLeft, spacerRight, spacerMiddle, blackLineSeparator (available classes depends on enable options) |
Editin buttos in Columns view | |
Header for the start cell of a content element column | commandLinks, commandLinks-startCell, TemplaVoilaStyle, div.headerWrap (available classes depends on enable options) |
Edit whole column | commandLink-edit-whole-column, commandLink-edit-whole-column_img. commandLink-edit-whole-column_text, commandLink-edit-whole-column_button, a.edit , span.text, span.button, span.textMode span.topLink (available classes depends on the selected button mode; if not otherwise informed classes are for td-elements) |
New record for to the top of the column | commandLink-new-record-whole-column, commandLink-new-record-whole-column_img, commandLink-new-record-whole-column_text, commandLink-new-record-whole-column_button, a.new, span.text, span.button, span.textMode span.topLink (available classes depends on the selected button mode; if not otherwise informed classes are for td-elements) |
Extra paste linkto the top of the column | CommandLink-paste-whole-column, pasteLink, IconMode, button-paste, textMode, text-pastePasteLink, buttonMode, commandLink, commandLink-paste (depends on selected mode) |
Spacer row for there header row (for TR) | typo3-page-colHeader-top-space-row |
Header for other cells of a content element column | commandLinks |
Edit record | commandLink-edit |
New record | commandLink-new-record |
Move record up | commandLink-move-up |
Move record down | commandLink-move-down |
Hide record | commandLink-hide |
Unhide record | commandLink-unhide |
Delete record | commandLink-delete |
Mode class for link items | iconMode, textMode, bothMode, buttonMode (depends on selected mode) |
Extra paste link | PasteLink, PasteLinkiconMode, PasteLinktextMode, PasteLinkbothMode, PasteLinkbuttonMode (depends on selected mode) |
Content element related information | Commandrow-info, iconModeInfo, textMode, bothModeInfo, buttonModeInfo (depends on selected mode) |
Icon toolbar (Columns view) | |
Table for toolbar | toolbarTable |
View record change history | list-tb-history |
Create new content element | list-tb-new-contentelement-record |
Move page | list-tb-move-page |
Create new page | list-tb-new-page |
Edit page header | list-tb-edit-page-header |
Classes for container TD-element of toolbar items | toolbar_icon, toolbar_text, toolbar_button (depends on selected mode) |
Button/link title (Quick Edit mode) | |
Save document | savedok |
Save document and view page | savedokview |
Close document | closedok |
Delete | deletedok |
Undo/redo last change | undodok |
Edit page header | list-tb-edit-page-header-quickedit |
(spacer) | toobarspacer toolbar-spacer-1 |
View record change history | list-tb-history |
Create new content element | list-tb-new-record-quickedit |
Reposition current content element | list-tb-move-record-quickedit |
Create new page | list-tb-new-page-quickedit |
(spacer) | toobarspacer toolbar-spacer-2 |
Mode class for link items | iconMode, textMode, bothMode, buttonMode (depends on selected mode) |
Checkboxes (container DIV) | |
Class for the parent element of all checkboxes | db_layout-bottom-controls |
Show hidden content elements | db_layout-show-hidden |
Show secondary options (palettes) | db_layout-show-palettes |
Show field descriptions | db_layout-show-description |
Disable Rich Text Editor (RTE) | db_layout-disableRTE |
Links on bottom (container DIV) | |
Re-position current content element | db_layout-move-record-link |
Create new content element | db_layout-new-contentelement-link |
Create a shortcut to this page? | db-layout-shortcutlink |
This plugin adds following classes for buttons, which are created by '/t3lib/class.t3lib_tsfebeuserauth.php' (as default extensions for this file are disabled – I explain further, how to enable them; classes are for frontend editing purposes and needs that for edit panels has been defined the option 'toolbar' – possible at least editing the 'setup.txt' of 'CSS Styled Contents'):
Title/purpose | Classes for Frontend Editing |
|---|---|
View record change history | tb-button tb-button-history |
Create new page | tb-button tb-button-new-pag |
Edit page header | tb-button tb-button-edit |
Create a new record | tb-button tb-button-new-record |
Move page | tb-button tb-button-move-page |
Show list module | tb-button tb-button-list |
This plugin adds following classes for buttons, which are created by '/tslib/class.tslib_content.php', which have following classes added (as default extensions for this file are disabled). I will explain further how to enable them; classes are for frontend editing purposes:
Title/purpose | Classes for Frontend Editing |
|---|---|
Spacer between possible toolbar and other icons (for IMG) | spacer-image |
Edit record | button-edit2 |
Move up | button-up |
Move down | button-down |
Unhide element | button-unhide |
Hide element | button-hide |
New page | button-new-page |
New record | button-new-record |
Delete record | button-delete-record |
Settings for skin_grey_2
The height of top frame has been set to '41' instead of '70' and bottom from '35' to '25' in 'ext_tables.php' in the skin folder:
'$TBE_STYLES['dims']['topFrameH']=35;'.
I put 'stylesheet_post_extra.css' , into the /res/-folder of this plugin. You can use it as a model, how you can alter other skins. Most of my modifications are in the top of the style sheet.
Extra configuration options
Extra XCLASS-implementations have been added, which are not necessarily needed but may be useful. You can enable them from the backend configuration of this plugin.
I have modified the version of the basic mainframes shortcut frame you can put on top-left. If you want to use that frameset for 'alt_main.php' check 'If you want shortcut menu on top-left, enable this'. This is not the default because it only works if you don't add any shortcuts and just use the field 'Edit page ID' (in newest version 'Edit/Search').
The definitions of rest of the options have been explained in the labels of each checkbox and don't need extra information. I have also added to tm_contentaccess Berhand Kraft's 'EXT: KB Better stdWrap' ('kb_betterstdwrap') and functionality of 'KB Page-Module Paste' ('kb_pm_paste'). Concerning the latter plugin there is better plugin, which does much more that kb_pm_paste, which can regarded as obsolete..
Because of incompatibility problems I have also added [Gobernalia] AJAX Backend Drag And Drop' ('gb_bedraganddrop') as an option (as default enabled).
I made only necessary changes in order to get them work and avoid error messages. Here is the list of changes:
'class.ux_ux_tslib_cobj.php'. Filename changed (original 'class.ux_tslib_content.php') and added prefix 'ux_' in front of class names. Extension key deleted (don't try anymore extend the class in this file).
'class.ux_tx_cms_layout.php'. Has been rewritten. The rewritten file combines all features of older version of this plugin and feixed features from kb_pm_paste and gb_bedraganddrop (version 0.3.0).
I added to the /res/ folder 'be_usertest.php'. If that file is in the 'typo3conf' folder and 'localconf.php' has the line 'include_once('be_usertest.php');' after the database information, it is possible to set user functions, when the extra language labels for edit panels can be set on the base of the user interface of the backend
# If the default language for a backend user has explicit set as 'Finnish' extra language labels are in Finnish
[userFunc = user_be_user_lang(fi)]
editPanelSetText= Sivun muokkaustoiminnot:
logOutText= Ulos
editpanelLabel=Muokkauspaneeli:
editPanelNew= Luo uusi sisältöelementti
newpageText= <- Luo uusi sivu
[global]
[else]
editPanelSetText= Extra toolbar:
logOutText= Exit
editpanelLabel=Edit panel:
editPanelNew= Create new content element
newpageText= <- Create new page
[end]
I have added to this plugin the functionality of plugin 'zed_more_columns' (author: Walter Hölblinger) as option 'more_columns'. You must however add the following TypoScript to the topmost basis template ('Include basis templates:' in the template definition). I tested it with as automatic added TypoScript and installable static template ('Include static templates (from extensions):'), but it didn't work with these methods because it needs to be in certain place. Then you get also the functionality of 'HTML CSS Styling' ('htmlcssstyling'; author David Pratten) concerning supporting of shared contents.
# this to the constants field – the id of the page of the shared contents
pidSharedContent=
#this to the setup field
###########################################################
# initialize extra contents - start
###########################################################
# get content, header
styles.content.getHeader < styles.content.get
styles.content.getHeader.select.where = colPos=4
# get content, footer
styles.content.getFooter < styles.content.get
styles.content.getFooter.select.where = colPos=5
# get content, news1-3
styles.content.getNews1 < styles.content.get
styles.content.getNews1.select.where = colPos=6
styles.content.getNews2 < styles.content.get
styles.content.getNews2.select.where = colPos=7
styles.content.getNews3 < styles.content.get
styles.content.getNews3.select.where = colPos=8
#special links
styles.content.getLinks < styles.content.get
styles.content.getLinks.select.where = colPos=9
###########################################################
# initialize extra contents - end
###########################################################
###########################################################
# initialize the Shared Contents - start
###########################################################
styles.content.getShared < styles.content.get
styles.content.getShared.select {
pidInList = {$pidSharedContent}
}
styles.content.getLeftShared < styles.content.getLeft
styles.content.getLeftShared.select {
pidInList = {$pidSharedContent}
}
styles.content.getRightShared < styles.content.getRight
styles.content.getRightShared.select {
pidInList = {$pidSharedContent}
}
styles.content.getBorderShared < styles.content.getBorder
styles.content.getBorderShared.select {
pidInList = {$pidSharedContent}
}
styles.content.getHeaderShared < styles.content.getHeader
styles.content.getHeaderShared.select {
pidInList = {$pidSharedContent}
}
styles.content.getFooterShared < styles.content.getFooter
styles.content.getFooterShared.select {
pidInList = {$pidSharedContent}
}
styles.content.getNews1Shared < styles.content.getNews1
styles.content.getNews1Shared.select {
pidInList = {$pidSharedContent}
}
styles.content.getNews2Shared < styles.content.getNews2
styles.content.getNews2Shared.select {
pidInList = {$pidSharedContent}
}
styles.content.getNews3Shared < styles.content.getNews3
styles.content.getNews3Shared.select {
pidInList = {$pidSharedContent}
}
styles.content.getLinksShared < styles.content.getLinks
styles.content.getLinksShared.select {
pidInList = {$pidSharedContent}
}
###########################################################
# initialize the Shared Contents - end
###########################################################
Then you should just put to the TS Config of pages, what columns have been used, for example:
mod.SHARED.colPos_list = 0
TCEFORM.tt_content.colPos.removeItems = 1,2,3,4,5,6,7,8,9,10
I you want good control for used columns, I recommend that you install 'rmpl_tmplselect' and 'stfl_tmpl2columns', when you column setting always match with the used templates, and users are confused that column quantity in backend and frontend is different.