Download the PHP package webcoast/editable-menus without Composer
On this page you can find all versions of the php package webcoast/editable-menus. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package editable-menus
Editable menus
TYPO3 CMS extension to create menus independent of the page tree/main menu where editors can change the menu items by selecting the pages, they want in the menu.
Installation
Configuration
The extension checks all active packages for a Configuration/Menus.php file.
For this extension to correctly determine the extension key, a composer.json file
must exist and contain the extra.typo3/cms.extension-key property.
The file must return an array with a valid menu configuration:
Attention: It is recommended to use snake case (lowercase with underscore) for the menu identifier to make the conversion work in several places throughout the menu processing.
Minimal configuration
The minimal menu configuration is just an empty array:
Full configuration
Override existing menus
It is possible to override existing menus to change their configuration or disabled them.
To do this, just use the same menu identifier. The configuration is merged using
array_replace_recursive.
Usage
Backend interface
For each configured menu a field is added to the site root properties under the
Menu settings tab.
By default, the fields are added as exclude fields, where editors need explicit permission to see it. This can be disabled for each menu individually.
The field name for the menu is generated by appending _menu to the menu identifier:
headerbecomesheader_menufooter_lowerbecomesfooter_lower_menu
The label and description are - if not set explicitly - determined automatically by taking by building a LLL references
LLL:EXT:{ext-key}/Resources/Private/Language/Menus.xlf:{menu-identifier}.labelandLLL:EXT:{ext-key}/Resources/Private/Language/Menus.xlf:{menu-identifier}.descriptionwhere{ext-key}is the extension key from the extension originally defining the menu, and{menu-identifier}is the menu identifier likeheaderorfooter_lower.
Fluid page template - Data processing
TypoScript data processing configuration is automatically added for each configured menu.
The variable that holds the menu data in the Fluid template is generated from the identifier
by converting the snake_case to UpperCamelCase and prepending menu to it:
- Identifier
headerbecomesmenuHeaderin the Fluid template - Identifier
footer_lowerbecomesmenuFooterLower
The default TypoScript should be sufficient for most use-cases. However, you can override it with your own TypoScript to tweak it, if necessary, e.g. to add sub data processors.
SQL
All necessary SQL to update the database is generated for all configured menus and will be shown/executed with the next database compare/schema update.
