strategy for naming module/theme/profile
Inspired by Boris Mann, I was going to start adding my company's standard install profile / module / theme in CVS. I've had issues in the past with a theme and module sharing the same name. Is this still an issue? Was this ever a recognised issue? Can I do this in D5 without any repurcussions when it comes to installation? module - "emspace" - support code and snippets for our install profile profile - "emspace" - our default install profile theme - "emspace" - our site's theme including an admin variation. Or to avoid issues described above, should I be doing: "emspace_code" "emspace_profile" "emspace_theme" Any suggestions are welcome. Simon
Simon Hobbs wrote:
I've had issues in the past with a theme and module sharing the same name. Is this still an issue? Was this ever a recognised issue? Hi Simon,
Themes and modules sharing the same name is still an issue in D5 (has bit me twice), as for D6 I assume it's still borked, but can't say 100%. I would do emspace_theme for sure, as for profile stuff I think the hooks used in a .profile won't conflict so that can stay emspace.profile. Then you can leave the module named emspace.module as well since the theme is safe. Rob
Naming your module and theme the same is a very bad idea. -Peter On 10/8/07, Simon Hobbs <info@urbits.com> wrote:
Inspired by Boris Mann, I was going to start adding my company's standard install profile / module / theme in CVS.
I've had issues in the past with a theme and module sharing the same name. Is this still an issue? Was this ever a recognised issue?
Can I do this in D5 without any repurcussions when it comes to installation?
module - "emspace" - support code and snippets for our install profile profile - "emspace" - our default install profile theme - "emspace" - our site's theme including an admin variation.
Or to avoid issues described above, should I be doing:
"emspace_code" "emspace_profile" "emspace_theme"
Any suggestions are welcome.
Simon
Cool, thanks Peter, Rob Peter Wolanin wrote:
Naming your module and theme the same is a very bad idea.
-Peter
On 10/8/07, Simon Hobbs <info@urbits.com> wrote:
Inspired by Boris Mann, I was going to start adding my company's standard install profile / module / theme in CVS.
I've had issues in the past with a theme and module sharing the same name. Is this still an issue? Was this ever a recognised issue?
Can I do this in D5 without any repurcussions when it comes to installation?
module - "emspace" - support code and snippets for our install profile profile - "emspace" - our default install profile theme - "emspace" - our site's theme including an admin variation.
Or to avoid issues described above, should I be doing:
"emspace_code" "emspace_profile" "emspace_theme"
Any suggestions are welcome.
Simon
participants (3)
-
Peter Wolanin -
Rob Barreca -
Simon Hobbs