Core Platform

Webapps have been updated so that they can be setup to allow any user to edit. It would be good to autocreate the default edit form in layouts. Maybe change the default form to insert.liquid (or input.liquid) and the new layout to edit.liquid or keep the default and have separate folders. This new form should appear in the toolbox as "WebApp edit form"

-Partners currently don't have access to this, move to Admin so people can edit.

At the moment if you want to turn one off you have to delete it.

The ability to add custom fields to Shipping Options.

Would it be possible to add a quick enable/disable feature so you do not need to open the webapp item or page you are attempting to change the status of. Ideally could we make the cross/tick icon shown in the screenshot attached a button to toggle this?

Image upload so you can more easily show the issue you're experiencing A 'ticket type' field, so you can filter tickets by either 'Account', 'Technical', etc. Further control of notifications (notify on data update, set other people up to receive notifications)

Currently the separator is hardcoded as '>'

Would be nice to have the option to disable/enable a content section. I suppose it could also be useful to have expiration date for content that is tied to an event. I have a client that runs events and I use content sections throughout the site. But when that content is no longer relevant, I would have to go to each page to change it. Would be easier if I could just disable it in a single place.

We would like to create a new version of Menu Builder, which overhauls both the existing UI as well as behind the scenes structure… no small update! We are excited to get your input and feedback to help shape its future. Below we will outline our current plan for the future based on any older feature requests relating to Menu Builder along with any feedback we have collected to date. If you have any questions, ideas or input on what you would like to see in Menu Builder next, please let us know by commenting on this feature request. Discussion is also welcome! — Structure * Remove the use of database items on Menu - json instead for structure * Simplify the menu layout structure * Update the default layout to cater to drop downs * Add either a optional text field to add a logo, or ideally custom fields (at a minimum: Link Title (text), Link Icon (file), Onclick (text)) * Add the ability to enable/disable menu items UI / UX * Keep existing drag & drop functionality * Data from across the site needs to be accessible, including search and filter functionality * Ability to add a blank empty new menu item * Ability to add items directly into a specific location in the menu, rather than adding a new item at the top level and then needing to move it to the desired location. * Ability to split menu into columns or groups and access those from the layout Data that needs to be accessible to the user when adding menu items: * Pages * WebApp items * Module items * Category pages

e.g. if there is a "VIP downloads" Secure Zone, you could select the page from a dropdown where someone who has access to that Secure Zone might access their content. This could be outputted front-end to allow links from the Secure Zones list layout to those start pages.