mazen-menu2
v0.0.0
Published
A plugin for Strapi CMS to customize the structure of menus and menu items.
Downloads
2
Maintainers
mazentesterReadme
Get Started
- Features
- Installation
- Configuration
- Extending
- User Guide
- API Usage
- Troubleshooting
- Migration
- Support or Donate
- Roadmap
✨ Features
- Consumable menu data which can be used to render navigation and other menus in a frontend app.
- Easily manage menus with either a flat or nested structure.
- Customize the
title,url, and linktargetof menu items. - Extend the schema and UI with custom attributes and form layouts for menu items.
- Custom fields are supported (unless they rely on
useCMEditViewDataManagerhook). - Compatible with the Strapi Transformer plugin for cleaner API responses.
💎 Installation
yarn add strapi-plugin-menus@latest🔧 Configuration
| property | type (default) | description |
| - | - | - |
| maxDepth | number (null) | Limits how deep menu items can be nested. |
| layouts | object ({}) | Provide form layout configuration for custom attributes. |
maxDepth
Limits how deep menus can be nested. By default, there is no limit.
Example
./config/plugins.js
module.exports = {
menus: {
config: {
maxDepth: 3,
},
},
};layouts
Provide form layout configuration for custom attributes. The example below is quite simple. See the Extending section for more details on how to use this feature.
Example
./config/plugins.js
module.exports = {
menus: {
config: {
layouts: {
menuItem: {
link: [
{
input: {
label: 'Example Field Label',
name: 'example_field',
type: 'text',
},
grid: {
col: 6,
},
},
],
},
},
},
},
};🔩 Extending
This plugin can be extended to add new attributes to the MenuItem schema and include editable fields for those attributes in the UI. Follow along with each section below to become familiar with this process.
1. Extend MenuItem schema attributes
First, create the file ./src/extensions/menus/strapi-server.js. Then copy/paste the code below into that file to get started.
'use strict';
module.exports = plugin => {
// Get current `MenuItem` attributes.
const defaultAttrs = plugin.contentTypes[ 'menu-item' ].schema.attributes;
// Define custom attributes for `MenuItem` the same way they would be defined
// on any other schema.
const customAttrs = {
example_field: {
type: 'string',
},
};
// Extend the `MenuItem` content type with custom attributes.
plugin.contentTypes[ 'menu-item' ].schema.attributes = {
...defaultAttrs,
...customAttrs,
};
return plugin;
};2. Configure layouts for custom attributes
Next, we need to extend the form layout to include the new attributes we defined on the schema.
In ./config/plugins.js, we will configure the layouts prop to allow our custom attributes to render in the UI. By default, the menu item edit panel has one tab labeled "Link". We can add fields to the "Link" tab by defining layouts.menuItem.link as an array of field config objects.
New tabs in the edit panel are configured with each key in the layouts.menuItem object. The example below will add our custom attribute into the "Link" tab and it will occupy the remaining 6 columns of spacing in that panel.
module.exports = {
menus: {
config: {
layouts: {
menuItem: { // This is the menu item edit panel.
link: [ // This is the "link" tab in the menu item edit panel.
{
input: {
label: 'Example Field Label',
name: 'example_field',
type: 'text',
description: 'Example field description',
placeholder: 'Type something...'
},
grid: {
col: 6,
},
},
],
},
},
},
},
};Field config and grid layout
Each field config object may contain an input and a grid prop. Neither are required, but at least one should be present.
The input prop requires label, name, and type and will be used with the GenericInputs component from the Strapi helper plugin. Other available props can be found in the example below.
The grid prop values correspond to a 12-column layout and will be passed directly to the GridItem component from the Strapi design system.
{
input: {
label: 'Field Label',
name: '<field_name>', // Same name as defined in the schema.
type: '<field_type>', // Reference "Supported field types" section.
description: 'Helpful small text under the field input.',
placeholder: 'Type something...',
required: true,
step: 60, // Numbers and time inputs only.
options: [ // Select menus only.
{
label: 'Option Label 1',
value: 'option1',
},
{
label: 'Option Label 2',
value: 'option2',
},
{
label: 'Option Label 3',
value: 'option3',
},
],
},
grid: {
col: 6, // Default.
s: 12, // Tablet.
xs: 12, // Mobile.
},
},For select input types, the enum values associated with the attribute will be used by default for the options. Or you can provide a custom options array of objects where each object has a label and value prop.
[
{
label: 'Option Label',
value: 'optionValue',
},
],For customField input types, you must include the customField prop with the custom field UID.
NOTE: Custom fields will not work in this plugin if they rely on
useCMEditViewDataManagerhook.
{
input: {
label: 'Example Custom Field',
name: 'example_field',
type: 'customField',
customField: 'plugin::custom-fields.example',
},
},You may also omit the input prop and just add some white space with the grid prop.
{
grid: {
col: 6,
},
},Translations
You may optionally provide a translation config object instead of a string value for label, description, and placeholder props. This also applies to label values in select menu options. However, this does not enable translations by itself.
You must also include the custom field translations in your ./src/admin/app.js file as you see in the example below.
export default {
config: {
locales: [ 'en' ],
translations: {
en: {
'menus.customFields.field_name.label': 'Translated Label',
'menus.customFields.field_name.placeholder': 'Translated Placeholder',
'menus.customFields.field_name.description': 'Translated Description',
},
},
},
// etc.
};Supported field types
The following field types in the table below are supported. Some fields use a different type value for the schema and input type.
| Field | Schema Type | Input Type |
| - | - | - |
| Boolean | boolean | bool |
| Date | date, time, datetime | same |
| Email | email | same |
| Enumeration | enumeration | select |
| Media | media | same |
| Number | integer, biginteger, decimal, float | number |
| Password | password | same |
| Relation | relation | same |
| Rich Text | richtext | wysiwyg |
| Text | string, text | string, text, textarea |
The following field types are NOT supported:
- Component
- Dynamic Zone
- UID
- JSON
NOTE: By default, rich text fields are not supported unless a custom plugin overrides the core WYSIWYG editor, which is covered in the Strapi guide to creating a new WYSIWYG field in the admin panel.
100% Complete configuration
For reference, here is an example of a 100% complete config with all supported field types. This also demonstrates how tabs and fields can be easily configured.
First, create the file ./src/extensions/menus/strapi-server.js and add the code below.
'use strict';
module.exports = plugin => {
// Get current `MenuItem` attributes.
const defaultAttrs = plugin.contentTypes[ 'menu-item' ].schema.attributes;
// Define custom attributes for `MenuItem` the same way they would be defined
// on any other schema.
const customAttrs = {
example_bool: {
type: 'boolean',
},
example_text: {
type: 'string',
},
example_email: {
type: 'email',
},
example_password: {
type: 'password',
},
example_richtext: {
type: 'richtext',
},
example_date: {
type: 'date',
},
example_time: {
type: 'time',
},
example_datetime: {
type: 'datetime',
},
example_integer: {
type: 'integer',
},
example_biginteger: {
type: 'biginteger',
},
example_decimal: {
type: 'decimal',
},
example_float: {
type: 'float',
},
example_enum: {
type: 'enumeration',
enum: [
'option1',
'option2',
'option3',
],
},
example_media: {
type: 'media',
allowedTypes: [ 'images' ],
multiple: false,
},
example_relation_one: {
type: 'relation',
relation: 'oneToOne',
target: 'api::example-one.example-one',
},
example_relation_many: {
type: 'relation',
relation: 'oneToMany',
target: 'api::example-many.example-many',
},
};
// Extend the `MenuItem` content type with custom attributes.
plugin.contentTypes[ 'menu-item' ].schema.attributes = {
...defaultAttrs,
...customAttrs,
};
return plugin;
};Next, add the plugin config for menus to ./config/plugins.js to include custom form field layouts.
TIP: Despite the simplicity, this is certainly a lot of code. It may be best to move it into a separate file and
require()it into your main config file to keep things organized.
module.exports = {
menus: {
config: {
maxDepth: 3,
layouts: {
menuItem: {
link: [
{
input: {
label: 'Boolean',
name: 'example_bool',
type: 'bool',
},
grid: {
col: 6,
},
},
],
text: [
{
input: {
label: 'Text',
name: 'example_text',
type: 'text',
},
},
{
input: {
label: 'Email',
name: 'example_email',
type: 'email',
},
},
{
input: {
label: 'Password',
name: 'example_password',
type: 'password',
},
},
{
input: {
label: 'Rich Text',
name: 'example_richtext',
type: 'wysiwyg',
description: 'This field type is not supported unless a custom plugin overrides the core WYSIWYG editor.',
},
},
],
date: [
{
input: {
label: 'Date',
name: 'example_date',
type: 'date',
},
grid: {
col: 6,
},
},
{
input: {
label: 'Time',
name: 'example_time',
type: 'time',
},
grid: {
col: 6,
},
},
{
input: {
label: 'Date and Time',
name: 'example_datetime',
type: 'datetime',
},
},
],
number: [
{
input: {
label: 'Integer',
name: 'example_integer',
type: 'number',
},
grid: {
col: 6,
},
},
{
input: {
label: 'Big Integer',
name: 'example_biginteger',
type: 'number',
},
grid: {
col: 6,
},
},
{
input: {
label: 'Decimal',
name: 'example_decimal',
type: 'number',
},
grid: {
col: 6,
},
},
{
input: {
label: 'Float',
name: 'example_float',
type: 'number',
},
grid: {
col: 6,
},
},
],
media: [
{
input: {
label: 'Media',
name: 'example_media',
type: 'media',
},
},
],
select: [
{
input: {
label: 'Enumeration',
name: 'example_enum',
type: 'select',
options: [
{
label: 'Option Label 1',
value: 'option1',
},
{
label: 'Option Label 2',
value: 'option2',
},
{
label: 'Option Label 3',
value: 'option3',
},
],
},
},
{
input: {
label: 'Relation (hasOne)',
name: 'example_relation_one',
type: 'relation',
},
},
{
input: {
label: 'Relation (hasMany)',
name: 'example_relation_many',
type: 'relation',
},
},
],
},
},
},
},
};With everything configured properly, you should end up with a menu item edit panel that looks like the image below. Refer to the Supported Field Types section if you are still confused on how to enable the rich text editor.
📘 User Guide
Create
On the menus plugin home page, use the "Create new menu" button to get started. You will need to provide a title and a unique slug value for the new menu. Saving the menu before adding menu items is recommended but not required.
Clone
Choosing to clone an existing menu will take you to the edit view as usual, but this time it will be pre-populated with another menu's data. Once the cloned menu is saved, a brand new menu and menu items are created.
Delete
Deleting a menu will also delete all of it's menu items.
Edit
When clicking on a menu item in the left column, it will reveal action buttons to move the item, delete it, or give it a submenu.
The right column will reveal the edit UI for that item, where the title is the only required field.
⚡ API Usage
Fetching menus data is the same as fetching any other data using Strapi's REST API features.
Don't forget to enable the public methods for
MenuandMenuItemin the Users and Permissions settings, likefindandfindOne.
Endpoints
| request | endpoint | description |
| - | - | - |
| GET | /api/menus | Fetch all menus. |
| GET | /api/menus/:id | Fetch one menu. |
| POST | /api/menus/:id | Create a menu. |
| PUT | /api/menus/:id | Update a menu. |
| DELETE | /api/menus/:id | Delete a menu. |
Params
| name | description |
| - | - |
| nested | Serialize menu items into a nested format, otherwise they are returned as a flat list. |
Basic example
Fetch a menu with the ID 3. Nothing is populated by default.
await fetch( '/api/menus/3' );Response
{
"data": {
"id": 3,
"attributes": {
"title": "Main Menu",
"slug": "main-menu",
"createdAt": "2022-07-24T01:51:19.115Z",
"updatedAt": "2022-07-24T01:55:16.153Z"
}
},
"meta": {}
}Example with population
Fetch a menu with the ID 3 with populate params included.
await fetch( '/api/menus/3?populate=*' );Response
{
"data": {
"id": 3,
"attributes": {
"title": "Main Menu",
"slug": "main-menu",
"createdAt": "2022-07-24T01:51:19.115Z",
"updatedAt": "2022-07-24T01:55:16.153Z",
"items": {
"data": [
{
"id": 10,
"attributes": {
"order": 0,
"title": "Parent Page",
"url": "/parent-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z"
}
},
{
"id": 11,
"attributes": {
"order": 0,
"title": "Child Page",
"url": "/child-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z"
}
},
{
"id": 12,
"attributes": {
"order": 0,
"title": "Grandchild Page",
"url": "/grandchild-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z"
}
},
{
"id": 13,
"attributes": {
"order": 0,
"title": "Another Page",
"url": "/another-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": []
}
}
]
}
}
},
"meta": {}
}Example with population and nested params
Fetch a menu with the ID 3 with the nested param included.
await fetch( '/api/menus/3?nested&populate=*' );Response
{
"data": {
"id": 3,
"attributes": {
"title": "Main Menu",
"slug": "main-menu",
"createdAt": "2022-07-24T01:51:19.115Z",
"updatedAt": "2022-07-24T01:55:16.153Z",
"items": {
"data": [
{
"id": 10,
"attributes": {
"order": 0,
"title": "Parent Page",
"url": "/parent-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": [
{
"id": 11,
"attributes": {
"order": 0,
"title": "Child Page",
"url": "/child-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": [
{
"id": 12,
"attributes": {
"order": 0,
"title": "Grandchild Page",
"url": "/grandchild-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": []
}
}
]
}
}
]
}
},
{
"id": 13,
"attributes": {
"order": 0,
"title": "Another Page",
"url": "/another-page",
"target": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": []
}
}
]
}
}
},
"meta": {}
}Example with nested param and custom relations populated
Custom relation fields are not populated by default. Here we fetch a menu with the ID 3 with custom relation fields populated.
The qs library is highly recommended for building the request URL for complicated population objects.
import qs from 'qs';
const params = {
nested: true,
populate: {
items: {
populate: {
example_relation: true,
another_relation: true,
},
},
},
};
const query = qs.stringify( params, { addQueryPrefix: true } );
// The params above will parse into this query string.
// ?nested&populate[items][populate][0]=example_relation&populate[items][populate][1]=another_relation
await fetch( `/api/menus/3${query}` );Response
{
"data": {
"id": 3,
"attributes": {
"title": "Main Menu",
"slug": "main-menu",
"createdAt": "2022-07-24T01:51:19.115Z",
"updatedAt": "2022-07-24T01:55:16.153Z",
"items": {
"data": [
{
"id": 10,
"attributes": {
"order": 0,
"title": "Parent Page",
"url": "/parent-page",
"target": null,
"example_relation": {
"id": 1,
"title": "Example Relation",
},
"another_relation": {
"id": 2,
"title": "Another Relation",
},
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": [
{
"id": 11,
"attributes": {
"order": 0,
"title": "Child Page",
"url": "/child-page",
"target": null,
"example_relation": null,
"another_relation": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": [
{
"id": 12,
"attributes": {
"order": 0,
"title": "Grandchild Page",
"url": "/grandchild-page",
"target": null,
"example_relation": null,
"another_relation": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": []
}
}
]
}
}
]
}
},
{
"id": 13,
"attributes": {
"order": 0,
"title": "Another Page",
"url": "/another-page",
"target": null,
"example_relation": {
"id": 1,
"title": "Example Relation",
},
"another_relation": null,
"createdAt": "2022-07-24T03:33:03.416Z",
"updatedAt": "2022-07-24T19:49:38.949Z",
"children": []
}
}
]
}
}
},
"meta": {}
}💩 Troubleshooting
In general
Remember to rebuild your app after making changes to some config or other code.
yarn build
# OR
yarn developCustom MenuItem attributes don't save or appear in the database table schema.
Custom attributes require both the form layout extension as well as the schema extension. Please make sure both of these are configured as described in the Extending section.
Some users cannot view menus, as if they do not have permissions.
Currently, this plugin does not even support RBAC (role-based access controls). If it appears as if a users does not have permissions to view menus, try to update that user's profile in Strapi or even change their password. This should kick something into place that fixes that user's permissions.
The screen goes white when I try to use the menus plugin.
Either something in your menus plugin configuration is setup incorrectly or you may have custom middlewares, plugins, or lifecycle hooks that could be interfering. Check your developer console to gain more insight into the error.
🚌 Migration
Follow the migration guides to keep your menus plugin up-to-date.
❤️ Support or Donate
If you are enjoying this plugin and feel extra appreciative, you can buy me a beer or 3 🍺🍺🍺.
🚧 Roadmap
- Localization support
- RBAC support
- Drag and drop items
- Populate
urlvia relation - Restore deleted items (before saving)
- More translations