For example, if you have an install profile named chameleon which installs the chameleon theme, the platform verification process will result in something like this:

  • a record in hosting_package is created for the chameleon theme
  • a collection of records is created in hosting_package_instance for the chameleon theme, which are related to the chameleon theme package
  • a collection of records is created in hosting_package_instance for the chameleon profile, which are related to the chameleon theme package
  • in the platform package list the chameleon install profile will not be present.

Comments

adrian’s picture

adrian commented

that's actually invalid in drupal itself.

you can't register multiple projects on d.o with the same short_name.

you _will_ run into problems with install profiles, modules and themes stepping all over each other's namespaces.

it's recommended you rename your theme / module.

rburns’s picture

rburns commented

I see. I have sites with a module and theme of the same name, without issue. A bit of googling shows I must have gotten lucky.

http://drupal.org/node/143020
http://drupal.org/node/84695
http://tech.forumone.com/archives/152-Drupal-module-and-theme-naming-col...

Would it be better to generate a useful log message and skip over the hosting_package_instance insert when a package of a different type but the same name is present in the hosting_package table? rather than continue on as if nothing had gone wrong.

anarcat’s picture

anarcat commented
Title: two packages of different types can not have the same name » explain properly that two packages of different types can not have the same name
Category: bug » feature
sdrycroft’s picture

sdrycroft commented
Version: 5.x-0.2.x-dev » 6.x-0.4-alpha3

I've just run into exactly this issue, but not with a theme/module name overlap, but with a profile/module name overlap. This isn't documented as being an issue, on Drupal.org (all the issues above are regarding module/theme name overlaps), a simple warning message telling me that I've got overlapping project names would have stopped me scratching my head for a little while.

As for Adrian's comment, I guess we need to remember that not everyone registers all of their modules/profiles/themes to Drupal.org - me included (http://dev.scratchpads.eu/).

Cheers, and thanks for an amazing module/product.

Anonymous’s picture

Anonymous (not verified) commented

Adrian's comment about d.o is meant more as an example i.e ('the fact you can't do it on d.o is an example of how it's not allowed').

I still don't think this is our problem to fix.

This isn't documented as being an issue, on Drupal.org

It's a documentation problem for Drupal.org then isn't it?

I'm not against putting a drush_log warning somewhere, but I don't want to devote my Aegir development time to biting core's ankles and doing their job of making it obvious :)

steven jones’s picture

steven jones commented
Status: Active » Closed (duplicate)

Marking this as a duplicate of #1437956: How do i rename an incorrect Installation profile on an existing site?