Project name vs. repo name - a topic for our DEV meeting.
The usual case is that the project name and the repo name are the same. So mymodule.info and mymodule.module are in a directory mymodule.
However, in very rare cases a D7 module doesn't follow that common practice, and its repo name is different. Such a module can be ported, can be released (gets packaged) - but it can't get enabled.
What we might need is some policy and documentation, or - if we want to support that, it should work in the installer.
Either way, there needs to be clarity. Especially for people porting D7 modules. For example instructions how to rename such a project (if we enforce exact match).
And if we enforce exact match, the packager should refuse to build a release (happens in the project module, I guess).
Project name vs. repo name - a topic for our DEV meeting.
The usual case is that the project name and the repo name are the same. So mymodule.info and mymodule.module are in a directory...
I understand that this is not in the subject, but using a separate field (for <iframe> or file upload, doesn't matter) you get an advantage in displaying content. You can create blocks and...
I got confused by this too so I wanted to clarify the last comment here:
You need to enable the input filter called: "Convert image captions to figure and figcaption elements" at the...
Hi
I added the 2 additional settings in settings.php, did a restart - and the error disappeared!
Thanks for the support!
(but the issues with the conversion still remain .....
Comments
Project name vs. repo name - a topic for our DEV meeting.
The usual case is that the project name and the repo name are the same. So
mymodule.info
andmymodule.module
are in a directorymymodule
.However, in very rare cases a D7 module doesn't follow that common practice, and its repo name is different. Such a module can be ported, can be released (gets packaged) - but it can't get enabled.
What we might need is some policy and documentation, or - if we want to support that, it should work in the installer.
Either way, there needs to be clarity. Especially for people porting D7 modules. For example instructions how to rename such a project (if we enforce exact match).
And if we enforce exact match, the packager should refuse to build a release (happens in the project module, I guess).
Not sure if that needs a PMC decision.
See also:
The core issue opened recently by a new contributor, who ran into that problem: https://github.com/backdrop/backdrop-issues/issues/6901
A short discussion in our Zulip chat, where preferences rather seem to be "strict match":
https://backdrop.zulipchat.com/#narrow/channel/218635-Backdrop/topic/Project.20name.20vs.20directory.20name/with/517458038