discover a module added to the system by ftp or similar
blank unpublished module
no blank unpublished module
this is inconsistent with a normal installation
Labels |
Added:
No Code Attached Yet
|
As I understand Installer/Adapter/ModuleAdapter::storeExtension it will always install a blank module for the installation route
Not sure if I understand correctly that your module is not installed at all via discover?
You are sure that the .xml file of the module is correct?
The issue report is not for a specific module.
A module is installed and added to the extensions table for both the discover_install and normal installation.
The discover_install returns after adding the module as extension. (https://github.com/joomla/joomla-cms/blob/4.4-dev/libraries/src/Installer/Adapter/ModuleAdapter.php#L554)
While the normal installation adds a new unpublished module (https://github.com/joomla/joomla-cms/blob/4.4-dev/libraries/src/Installer/Adapter/ModuleAdapter.php#L637)
Thanks for this information. Need to inverstigate.
I could have sworn that the module instance is not created, but you are right. Upon regular installation, an unpublished instance of the module is created. I'm not sure if I like it... I would argue, that this is intended behavior the way it is now because:
I'm going to bring this up in the maintainers meeting to see what the consensus is.
Many modules do not create an unpublished instance of the module on installation. Something that I am always grateful for especially when installing a package that includes a large number of modules.