Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Admin Menu custom presets, import/export a preset into/from database driven menu #16451
Summary of Changes
As we know that with the release of Joomla 3.7 we have the Admin Menu Manager that lets you customise the administrator menu according to your needs. The backend menu comes in two flavours: Custom Menu and Preset Menu. You can have as many custom menu each configured in different way as suitable. Or if you do not want to customise then you use the Preset menu.
This PR is indented to extend the features for this Admin Menu Manager as promised in the initial strategy.
Documentation Changes Required
I'd like to write the detailed documentation of the entire Admin Menu Manager. Please advise where should I head towards.
PS: As I am on a vacation this PR was created in hurry. Pardon me for any mistakes and please ask for any kind of clarifications or suggestions. I'll try to respond as quickly as possible.
referenced this pull request
Jun 2, 2017
To avoid this error there might be options like:
I got two other error messages after creating a new menu:
Method of import
Iit would be helpful to have an option to either add the new preset to the existing items or replace all existing items. So there is the possibility to add either a preset for only a component or a full menu.
New presets not showing
File structure xml vs. php
Suggestion for mobile view
This would be a good feature for people who do a lot of their work with mobile devices. And it would kind of restore a possibility you had with php files before.
@StefanSTS Below are my responses as per my understanding to your inputs:
If we replace all the existing menu items during a single click import process it would be an easy destructive action. Therefore, I omitted that feature on purpose. The user must "select all" and "delete" all existing menu items if so intended.
I tested this and it is working here as expected. I may be missing something, please let me know if you still get this issue.
The preset XML files are to represent the menu item definition and hierarchy. Their rendering is still controlled via the layout files in the
Therefore, you still have all the controls over the rendering while keeping the preset definition as simple and general.
Additionally, I'd like to mention that those
I have tested this item
Works fine here.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16451.