- Issue created by @ressa
- Status changed to Fixed
about 1 year ago 2:52am 30 October 2023 - 🇷🇴Romania bbu23
Hi ressa, thank you for reporting these issues, I have updated the project description to include the missing comment (good catch btw) and changed the default branch in gitlab.
- 🇩🇰Denmark ressa Copenhagen
Perfect, thanks for a fast answer and updates. I have two more questions:
-
[...] By default, the export folder is set to ../config/menu_migration
Wouldn't it simplify the set up and configuration steps if it was saved in
sites/default/files/menu_migration
, since there will be write access by default? Advanced users knows that they should add ../assets/config instead, I would think. I created 📌 Make sites/default the default export folder Needs review with an example of this. -
I see that the module supports multisite with this structure which is great:
<export_folder>/sites/<site_name>/<menu_name>/<menu_name>.json
Since the majority of sites are not multisites, perhaps a simpler target structure could be this by default, by detecting if it is multisite or not?
<export_folder>/<menu_name>.json
But if it is a lot work, then nevermind. I just had the thought :-)
-
- 🇷🇴Romania bbu23
Thank you, I've seen the issue and commented there. The main audience for this module is developers. The Menu Import and Export → module is available as an alternative which is more suited for a larger type of audience and a more persistent sync.
Automatically closed - issue fixed for 2 weeks with no activity.