From 2713c69c226ae66359892870d5e1c9ad283d9cdd Mon Sep 17 00:00:00 2001 From: Dan Untenzu Date: Tue, 27 Feb 2018 11:02:50 +0100 Subject: [PATCH 1/4] [FEATURE] Docs: Explain module key & tour name Explain why it is important to set a valid module key. Explain that the tour identifier is used for filenames (YAML) and Configuration (TSConfig overwrites) as well. --- Readme.md | 45 +++++++++++++++++++++++++++------------------ 1 file changed, 27 insertions(+), 18 deletions(-) diff --git a/Readme.md b/Readme.md index 282da8b..459e24c 100644 --- a/Readme.md +++ b/Readme.md @@ -30,23 +30,26 @@ Register a tour in the `ext_localconf.php` file in your extension: 'MyExtensionModuleTour', 'LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:title', 'LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:description', - 'web_ts', - 'module-web_ts', + 'web_list', + 'module-web_list', 'EXT:myextension/Configuration/Tours/' ); ``` The `\Tx\Guide\Utility\GuideUtility::addTour` method requires the following parameters: -1. The tour identifier. Should be a upper-camel-cased string, and unique (eg. prepend extension name) -2. The title for the tour. This can be a localization identifier too. -3. The description for the tour. This can be a localization identifier too. -3. The Module-Key of the tour. This is the same like the `m`-Parameter of the Module. -4. The icon identifier for the tour. See [TYPO3.Icons](https://github.com/TYPO3/TYPO3.Icons) for available icons or how to register your own. -5. The base path for your *.yaml configuration files for the tour. +1. The tour identifier. Should be a upper-camel-cased string, and unique (eg. prepend extension name). The YAML-file needs to have the same name. +1. The title for the tour. This can be a localization identifier too. +1. The description for the tour. This can be a localization identifier too. +1. The module-key of the tour. This is the starting point of the tour, the guide extension will open this module when starting. +1. The icon identifier for the tour. See [TYPO3.Icons](https://github.com/TYPO3/TYPO3.Icons) for available icons or how to register your own. +1. The base path for your *.yaml configuration files for the tour. -*Note:* All settings in the YAML may be modified with overwrites in the Page-TSconfig -or User-TSconfig. +Now create a YAML-file. For the example given above, it needs to be stored at +`EXT:myextension/Configuration/Tours/MyExtensionModuleTour.yaml`. + +*Note:* All settings in the YAML may be modified with overwrites in the +Page-TSconfig or User-TSconfig again. ## Modify existing tours @@ -60,7 +63,7 @@ mod.guide.tours.MySpecialModuleTour { } ``` -To modify an existing tour, you therefore just need to add option values below the module identifier. +To modify an existing tour, you therefore just need to add option values below the tour identifier. The guide extension provides some example tours. If you want the second popover of the *ViewModule* tour append on the *right* instead of the *bottom*, you would @@ -86,19 +89,25 @@ Each *tour* node can be configured like this: mod.guide.tours.ViewModule { # The title of the tour. This title will be displayed in the backend module. # Enter simply some text or use a LLL identifier. - title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourViewModule.xlf:tx_guide_tour.title + title = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.title + # Description of the tour. This description will be displayed in the backend module. # Enter simply some text or use a LLL identifier. - description = LLL:EXT:guide/Resources/Private/Language/BootstrapTourViewModule.xlf:tx_guide_tour.description - # Internal name of the module. - # This is the same identifier like the module key (M parameter in backend links) - # The moduleName core is used for tours, which are execute in top frame. - # Examples: + description = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.description + + # The module key is the starting point of the tour. + # The guide extensions opens the given module when starting a tour. To switch + # beetween modules just register another tour. + # This is the same name like the `M` parameter in backend links. + # Special value: `core` is used for tours which are executed in the top frame. + # Example values: # - Page module: web_layout (a tour which is executed in page module) # - View module: web_ViewpageView (a tour which is executed in view module) + # - Backend: core (a tour which is executed in the top frame of the backend window) moduleName = core + # Icon identifier for the icon in backend module. - # The icon identifier has to be registered in the icon registry. + # See https://github.com/TYPO3/TYPO3.Icons for available icons or how to register your own. iconIdentifier = module-guide-tour-core # In the steps node you have insert a node for each popover you want to display. steps { From c3812f4f5e1fdeb3a08a1b671834f15137c13516 Mon Sep 17 00:00:00 2001 From: Dan Untenzu Date: Tue, 27 Feb 2018 11:05:10 +0100 Subject: [PATCH 2/4] [FEATURE] Restore Page-TSconfig description MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Restore note about how to add Page-TSconfig since the guide extension reads Page-TSconfig from root page only, and not subpages →requires PHPP. --- Readme.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index 459e24c..a1baa86 100644 --- a/Readme.md +++ b/Readme.md @@ -75,13 +75,26 @@ mod.guide.tours.ViewModule { } ``` +*Note:* The User-TSconfig is always applied, either in a user or a user group. +Due to technical reasons the Page-TSconfig is read from page 0 (`root`) only! +Page-TSconfig stored on any other page wont be recognized by the module. + +To add TSconfig to the root page you need to register a file in the +`ext_localconf.php` file in your extension: + +```php +\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPageTSConfig( + '' +); +``` + ## Configuration ### Tour As explained before, the configuration should be done in YAML, but may be modified in TSconfig. The following description is done for TSconfig, but the -options are the same. +options are the same as in your YAML file. Each *tour* node can be configured like this: From 6fc0da5830f1ef36d5315d0c572b3fd6f5053a5d Mon Sep 17 00:00:00 2001 From: Dan Untenzu Date: Tue, 27 Feb 2018 11:06:51 +0100 Subject: [PATCH 3/4] [FEATURE] Docs: Enhance Readability Add some spaces, shorten some sentences. Add some explainations for beginners. --- .../Library/Tours/TemplateModule.pagets | 15 +- Readme.md | 290 ++++++++++-------- 2 files changed, 171 insertions(+), 134 deletions(-) diff --git a/Configuration/PageTS/Library/Tours/TemplateModule.pagets b/Configuration/PageTS/Library/Tours/TemplateModule.pagets index 241e3bb..bdb59ee 100644 --- a/Configuration/PageTS/Library/Tours/TemplateModule.pagets +++ b/Configuration/PageTS/Library/Tours/TemplateModule.pagets @@ -3,7 +3,7 @@ mod.guide.tours.TemplateModule { description = LLL:EXT:guide/Resources/Private/Language/BootstrapTourTemplateModule.xlf:tx_guide_tour.description moduleName = web_ts iconIdentifier = module-web_ts - steps { + steps { 10 { selector = .module-docheader title = Template module @@ -16,6 +16,7 @@ mod.guide.tours.TemplateModule { stepByKey = template-module-button } } + 20 { selector = select[data-menu-identifier='web-func-jump-menu'] title = Module menu @@ -29,18 +30,21 @@ mod.guide.tours.TemplateModule { content = Here you're able to switch between different TypoScript templates, which might be on this page. placement = bottom } + 210 { selector = select[data-menu-identifier='constant-editor-cat'] title = Constants categories content = Here you're able to switch between different constant categories. placement = bottom } + 220 { selector = .tstemplate-constanteditor title = Constants content = The following table allows you to modify the TypoScript constants from the selected category. placement = top } + 230 { selector = span[data-identifier='actions-open']:first title = Constants @@ -48,10 +52,5 @@ mod.guide.tours.TemplateModule { placement = left click = true } - - - - - - } -} \ No newline at end of file + } +} diff --git a/Readme.md b/Readme.md index a1baa86..7d5edac 100644 --- a/Readme.md +++ b/Readme.md @@ -90,57 +90,59 @@ To add TSconfig to the root page you need to register a file in the ## Configuration +The following configuration documentation is done in TSconfig format. The options +in YAML are the same, just have a different format. + ### Tour -As explained before, the configuration should be done in YAML, but may be -modified in TSconfig. The following description is done for TSconfig, but the -options are the same as in your YAML file. +As explained before, the tour should be registered with PHP instead of TSconfig. +But it may be modified using TSconfig (see explaination above). Each *tour* node can be configured like this: ``` -mod.guide.tours.ViewModule { - # The title of the tour. This title will be displayed in the backend module. - # Enter simply some text or use a LLL identifier. - title = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.title - - # Description of the tour. This description will be displayed in the backend module. - # Enter simply some text or use a LLL identifier. - description = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.description - - # The module key is the starting point of the tour. - # The guide extensions opens the given module when starting a tour. To switch - # beetween modules just register another tour. - # This is the same name like the `M` parameter in backend links. - # Special value: `core` is used for tours which are executed in the top frame. - # Example values: - # - Page module: web_layout (a tour which is executed in page module) - # - View module: web_ViewpageView (a tour which is executed in view module) - # - Backend: core (a tour which is executed in the top frame of the backend window) - moduleName = core - - # Icon identifier for the icon in backend module. - # See https://github.com/TYPO3/TYPO3.Icons for available icons or how to register your own. - iconIdentifier = module-guide-tour-core - # In the steps node you have insert a node for each popover you want to display. - steps { - # The key of the steps should be numeric and defines the order of displaying the popover - 10 { - # ... - } - 20 { - # ... - } - # A step key can also be defined by a key name. - # This can be useful, if you like to jump to this step without knowing his step number. - step-key-by-key-name { - # ... - } +# The title of the tour. This title will be displayed in the backend module. +# Enter simply some text or use a LLL identifier. +title = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.title + +# Description of the tour. This description will be displayed in the backend module. +# Enter simply some text or use a LLL identifier. +description = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.description + +# The module key is the starting point of the tour. +# The guide extensions opens the given module when starting a tour. To switch +# beetween modules just register another tour. +# This is the same name like the `M` parameter in backend links. +# Special value: `core` is used for tours which are executed in the top frame. +# Example values: +# - Page module: web_layout (a tour which is executed in page module) +# - View module: web_ViewpageView (a tour which is executed in view module) +# - Backend: core (a tour which is executed in the top frame of the backend window) +moduleName = web_list + +# Icon identifier for the icon in backend module. +# See https://github.com/TYPO3/TYPO3.Icons for available icons or how to register your own. +iconIdentifier = module-web_list + +# In the steps node you have insert a node for each popover you want to display. +steps { + # The key of the steps should be numeric and defines the order of displaying the popover + 10 { + # … + } + 20 { + # … + } + # A step key can also be defined by a key name. + # This can be useful, if you like to jump to this step without knowing his step number. + step-key-by-key-name { + # … } - # Steps configuration can have a path to a YAML file with the step configuration. This field is optional. - # By setting your step configuration with this path, you're able to provide conditional steps depending on TYPO3 - # Major version. Additionally the steps are dynanical reloaded and the Page-TypoScript (tsconfig) remains small. - stepsConfiguration = EXT:guide/Configuration/Tours/ +} + +# The steps may be configured with with a YAML file instead. +# This is the base path where a YAML with the same name as the tour is stored. +stepsConfiguration = EXT:myextension/Configuration/Tours/ ``` ### Steps @@ -148,112 +150,131 @@ mod.guide.tours.ViewModule { Each *step* node can be configured like this: ``` - # The selector is passed to jQuery for selecting the HTML-Element, on which the popover should be placed. - # This selector must be unique in DOM. A selector can also be a unique data attribute/value. - # Examples: - # selector = #some-id - # selector = .some-unique-class - # selector = .some-multiple-used-class:first - # selector = select[name=\'WebFuncJumpMenu\']:first - # selector = [data-identifier='apps-toolbar-menu-shortcut'] - selector = .typo3-aboutmodules-inner-docbody - # This is the title of the popover. - # Enter simply some text or a LLL identifier like: - # title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourPageModule.xlf:tx_guide_tour.0.title - title = Welcome to TYPO3 backend - # This is the content of the popover. - # Enter simply some text or a LLL identifier like: - # title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourPageModule.xlf:tx_guide_tour.0.content - # You're also be able to use HTML tags like i, u, b, br or p. Additionally there is an img tag for displaying icons, - # which must have a data-icon-identifier attribute with the icon identifier. Such an icon usage could look like: - # - # There is a tag, which allows you the define actions for the user, which will be designed noticable. - # All other tags are disallowed. - content ( - This tour will show you the first steps within TYPO3.
- You're starting here in the about module, - which shows you your available modules. - This modules are related on the giving user authorisation.
-
- Click on Next for an introduction of the topbar of TYPO3.
-
- (You can restart each tour by the guided tours module.) - ) - # Defines the position of the popover. - # Possible values are: top, bottom, left, right, auto - placement = top - # Disables the arrow on popover. - # The arrow is displayed by default. - showArrow = false - # Enables a backdrop. - # This feature is currently in incubation - backdrop = false - # Set a padding for the backdrop - backdropPadding = 0 - # - # The following nodes can be used for executing some actions during the tour. - # - # The next node contains actions, which are triggered by clicking the next button - next { - # More information below... - } - # The show node contains actions, which are triggered by starting to show this step - show { - # More information below... - } - # The shown node contains actions, which are triggered by finishing to show this step - shown { - # More information below... - } - # The hide node contains actions, which are triggered by hiding a step - hide { - # More information below... - } +# The selector is passed to jQuery for selecting the HTML-Element, on which the popover should be placed. +# This selector must be unique in DOM. A selector can also be a unique data attribute/value. +# Examples: +# selector = #some-id +# selector = .some-unique-class +# selector = .some-multiple-used-class:first +# selector = select[name=\'WebFuncJumpMenu\']:first +# selector = [data-identifier='apps-toolbar-menu-shortcut'] +selector = .typo3-aboutmodules-inner-docbody + +# This is the title of the popover. +# Enter simply some text or use a LLL identifier. +title = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.10.title + +# This is the content of the popover. +# Enter simply some text or use a LLL identifier. +# You're also be able to use HTML tags like i, u, b, br or p. +# Additionally there is an img tag for displaying icons, +# which must have a data-icon-identifier attribute with the icon identifier. +# Such an icon usage could look like: +# +# There is a tag, which allows you the define actions for the user, +# which will be designed noticable. +# All other tags are disallowed. +# Example content: +# This tour will show you the first steps within TYPO3.
+# You're starting here in the about module, +# which shows you your available modules.
+# Click on Next for an introduction of the topbar of TYPO3. +content = LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.10.content + +# Defines the position of the popover. +# Possible values are: top, bottom, left, right, auto +placement = top + +# Disables the arrow on popover. +# The arrow is displayed by default. +showArrow = false + +# Enables a backdrop. +# This feature is currently in incubation +backdrop = false + +# Set a padding for the backdrop. +backdropPadding = 0 + +# The following nodes can be used for executing some actions during the tour. + +# The next node contains actions, which are triggered by clicking the next button +next { + # … +} +# The show node contains actions, which are triggered by starting to show this step +show { + # … +} +# The shown node contains actions, which are triggered by finishing to show this step +shown { + # … +} +# The hide node contains actions, which are triggered by hiding a step +hide { + # … +} +``` + +Example step in YAML format: + +```yaml +selector: '.typo3-aboutmodules-inner-docbody' +title: LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.10.title +content: LLL:EXT:myextension/Resources/Private/Language/MyExtensionModuleTour.xlf:guide_tour.10.content +placement: top ``` #### Next node -The *next* node contains actions, which are triggered by clicking the next button. So you're able to trigger another tour -in the last popover, just by clicking the next button. +The *next* node contains actions, which are triggered by clicking the next button. +So you're able to trigger another tour in the last popover, just by clicking the next button. ``` -# By clicking on next, the tour Topbar is triggered +# By clicking on next, the tour name “Topbar” is triggered. tour = Topbar -# The number/id of the step, which should be displayed of the called tour +# The number/id of the step, which should be displayed of the called tour. step = 0 # StepByKey resolves the step number by the key. -# Internally it runs through the required tour and counts the steps till the defined stepByKey is found. Finally it set -# the counted value into the step-attribute - this means, if you are using stepByKey the step-attribute isn't required. +# Internally it runs through the required tour and counts the steps till the +# defined stepByKey is found. Finally it set the counted value into the +# step-attribute. This means, if you are using stepByKey the step-attribute isn't required. stepByKey = step-key-by-key-name ``` #### Show node -The *show* node contains actions, which are triggered by starting to show this step. This means in detail, the action is -executed **before** the tour starts the displaying process. -With help of this node you're able to execute actions, like adding or removing a CSS class to an element or open select -boxes in order to show specific values. +The *show* node contains actions, which are triggered by starting to show this +step. This means in detail, the action is executed **before** the tour starts +the displaying process. With help of this node you're able to execute actions, +like adding or removing a CSS class to an element or open select boxes in order +to show specific values. ``` # Renames the label of the next button of the popover. # This is useful, when you're starting another tour by clicking the next button. renameNextButton = Start next tour + # Add a class on an element. This is useful, when you want to highlight a special element. addClass { # jQuery selector for identifying elements, which should get the class. selector = #typo3-cms-backend-backend-toolbaritems-usertoolbaritem - # Class to be added + + # Class to be added. # Attention: Because of an focus issue, opening a dropdown # by adding the class open is only working with event shown. class = open } + # Removes a class from an element. removeClass { # jQuery selector for identifying elements, which should lose the class selector = #typo3-cms-backend-backend-toolbaritems-usertoolbaritem + # Class to be remove class = open } + # Opens a select box by jQuery selector openSelectBox { selector = select[name=\'WebFuncJumpMenu\']:first @@ -261,34 +282,51 @@ openSelectBox { ``` #### Shown node -The *shown* node contains actions, which are triggered by finishing to show this step. This means in detail, the action is -executed **after** the popover is completely visible. The available actions in this nodes are equal to the *show* node. + +The *shown* node contains actions, which are triggered by finishing to show +this step. This means in detail, the action is executed **after** the popover is +completely visible. + +The available actions in this nodes are equal to the *show* node. #### Hide node -The *hide* node contains actions, which are triggered by hiding a step. The available actions in this nodes are equal to -the *show* node. + +The *hide* node contains actions, which are triggered by hiding a step. + +The available actions in this nodes are equal to the *show* node. ### Create different steps for different Major versions of TYPO3 -By providing your step configuration using YAML files, you're able to use different steps for different TYPO3 -versions. Just adjust the base folder of your *.yaml files in the registration. +By providing your step configuration using YAML files, you're able to use +different steps for different TYPO3 versions. Just adjust the structure of the +base folder of your *.yaml files. Example base path: ``` -EXT:your_ext/Configuration/Tours/ +EXT:myextension/Configuration/Tours/ +``` + +Corresponding YAML file: + +``` +EXT:myextension/Configuration/Tours/MyExtensionModuleTour.yaml ``` -Now this base folder needs some sub folders in which the tours for the different TYPO3 versions are stored. Each folder -is simply named by the major version number of TYPO3 - for example: +Now this base folder needs some sub folders in which the tours for the different +TYPO3 versions are stored. Each folder is simply named by the major version +number of TYPO3. For example: ``` -EXT:your_ext +EXT:myextension - Configuration - Tours - TYPO3-7 + - MyExtensionModuleTour.yaml - TYPO3-8 + - MyExtensionModuleTour.yaml - TYPO3-x + - MyExtensionModuleTour.yaml ``` In these folders the guide extension searches for YAML files, which have the same name as your tour identifier. From ba35c12194a2b8916ecbb149fdc4110ce21af259 Mon Sep 17 00:00:00 2001 From: Dan Untenzu Date: Tue, 27 Feb 2018 11:08:10 +0100 Subject: [PATCH 4/4] [FEATURE] Remove redundant files Configuration explained in Readme already, dont maintain two docs at once (one of both will always be too old). --- .../Tours/Configuration.pagets_example | 107 ------------------ 1 file changed, 107 deletions(-) delete mode 100644 Configuration/PageTS/Library/Tours/Configuration.pagets_example diff --git a/Configuration/PageTS/Library/Tours/Configuration.pagets_example b/Configuration/PageTS/Library/Tours/Configuration.pagets_example deleted file mode 100644 index f289754..0000000 --- a/Configuration/PageTS/Library/Tours/Configuration.pagets_example +++ /dev/null @@ -1,107 +0,0 @@ -# Definition of guided tours setup -# -# All tours must defined in mod.guide.tours. -# The main node of a tour is the internal name as well. -# This name should be a simple upper-camel-cased string. -# -mod.guide.tours.ConfigurationExample { - # The title of the tour. This title will be displayed in the backend module. - # Enter simply some text or a LLL identifier like: - # title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourPageModule.xlf:tx_guide_tour.title - title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourTree.xlf:tx_guide_tour.title - # Description of the tour. This description will be displayed in the backend module. - # Enter simply some text or a LLL identifier like: - # description = LLL:EXT:guide/Resources/Private/Language/BootstrapTourPageModule.xlf:tx_guide_tour.description - description = LLL:EXT:guide/Resources/Private/Language/BootstrapTourTree.xlf:tx_guide_tour.description - # Internal name of the module - # This the same identifier like the module kex (M parameter in backend links) - # The moduleName core is used for tours, which are execute in top frame. - # Examples: - # - Page module: web_layout - # - View module: web_ViewpageView - moduleName = core - # Icon identifier for the icon in backend module. - # The icon identifier has to be registered in the icon registry. - iconIdentifier = module-guide-tour-core - steps { - 0 { - # The selector is passed to jQuery and must be unique - # Examples: - # selector = #some-id - # selector = .some-unique-class - # selector = .some-multiple-used-class:first - # selector = select[name=\'WebFuncJumpMenu\']:first - selector = .typo3-aboutmodules-inner-docbody - # This is the title of the popover. - # Enter simply some text or a LLL identifier like: - # title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourPageModule.xlf:tx_guide_tour.0.title - title = Welcome to TYPO3 backend - # This is the content of the popover. - # Enter simply some text or a LLL identifier like: - # title = LLL:EXT:guide/Resources/Private/Language/BootstrapTourPageModule.xlf:tx_guide_tour.0.content - # You're also be able to use HTML tags like i, u, b, br or p. All other tags are disallowed. - content ( - This tour will show you the first steps within TYPO3.
- You're starting here in the about module, which shows you your available modules. - This modules are related on the giving user authorisation.
-
- Click on Next for an introduction of the topbar of TYPO3.
-
- (You can restart each tour by the guided tours module.) - ) - # Sets the position of the popover. - # Possible values are: top, bottom, left, right - placement = top - # Disables the arrow on popover. - # The arrow is displayed by default. - showArrow = false - # Actions triggered by clicking the next button - next { - # By clicking on next, the tour Topbar is triggered - tour = Topbar - # The number/id of the step, which should be displayed - step = 0 - } - # Actions triggered by start to show this step - show { - # Renames the label of the next button - renameNextButton = Start next tour - # Add a class on an element - addClass { - # jQuery selector for identifying elements, which should get the class - selector = #typo3-cms-backend-backend-toolbaritems-usertoolbaritem - # Class to be added - # Attention: Because of an focus issue, opening a dropdown by adding the class open is only working - # with event shown - class = open - } - # Removes a class from an element - removeClass { - # jQuery selector for identifying elements, which should lose the class - selector = #typo3-cms-backend-backend-toolbaritems-usertoolbaritem - # Class to be remove - class = open - } - # Open a Bootstrap dropdown - #openDropdown { - # jQuery selector of the Bootstrap dropdown - # Example: - # jQuery('#typo3-cms-backend-backend-toolbaritems-usertoolbaritem .dropdown-toggle[href="#"]').dropdown(); - # selector = #typo3-cms-backend-backend-toolbaritems-usertoolbaritem .dropdown-toggle[href="#"] - #} - # Opens a select box by jQuery selector - openSelectBox { - selector = select[name=\'WebFuncJumpMenu\']:first - } - } - # Actions triggered by finish to show this step - shown { - - } - # Actions triggered by hiding a step - hide { - - } - } - } -} \ No newline at end of file