I’m having a weird issue that I should be able to figure out, but I’m currently stumped.
I added a new custom module in the desugn tools. It shows up as a module available to the website page builder (under theme modules) but is unavailable in the landing page editor under any category. I have checked oll the options in the design tool for module visibility, but landing pages isn’t one of the check boxes (do I remember this used to be a specific option?)
Hi, @SteveHTM Thanks for your question! That sounds unusual, for sure.
I’d like to invite some of or community members to the conversation to share how they like to troubleshoot issues like this when creating custom modules. @elizheleva@KMurota@rlopez, how do you like to troubleshoot issues like this?
I won’t say this is a solution, but maybe an additional clue. In frustration, I added a reference to the new custom module in a template file - and suddenly the module also became available as a selection in the page editor.
@SteveHTM If you created the module in a child theme and the landing page is built with a template from another theme (not the same child theme) then the module won’t be available in the page editor.
Because a child theme’s modules often overwrite their parent/marketplace theme and an account could have multiple child theme’s, this prevents confusion - a child theme module will only appear for pages built with that child theme.
The workaround for this is to create a global modules folder in the design editor and move/copy any modules there that you want available for multiple themes. If you already are using the module in a child theme, I would use caution with moving the file and instead make a copy and rename it as a test to verify that works for all of your website and landing pages. Don’t delete/remove the module from the child theme if it’s used on live pages, if you want to do this, you’d need to manually rebuild the content using your new global module and then once the child theme module has no dependents you could delete it.
This is fairly new functionality, from what I can tell it’s as a result of the new UI search and the availability of modules in the marketplace that need to be compatible with any theme. For users that have multiple child themes for different brands, having child theme modules globally accessible was somewhat of a nightmare and this limitation resolved that - but also created this new issue where users expect to have all modules visible for all pages.
Thank you @Jnix284 for the thoughful response. You have illuminated a new dimension of the theme management universe for me here!
Unfortunately, the exact symptoms I was seeing are not a full match for this solution as my module visibility problem only occurred in the landing page editor and not in the web page editor - stilll very perplexing to me! There does not seem to be any specific flags/filters that woul set up a different visibility of modules in the context of landing pages from that of the full web page editor.
The child theme in use seems well enough formed to me, thank goodness, and is consistently applied to site pages, with no meta data to supress module visibility used. So I’m making progress here, but still scractching my head.
Thanks for your question! That sounds unusual, for sure.