Say you have your install profiles named like the following because you want the profiles directory to have a nice listing in the order of which chapters appear in a book you might be writing. Say. ;)
profiles/ch03-jobs/jobs.profile
profiles/ch04-reviews/reviews.profile
...
If a profile is unspecified, http://api.drupal.org/api/function/install_select_profile/7 searches for any file called $something.profile in the "profiles" directory and displays it in a list of all of the profiles at the beginning. When a profile is selected, the function returns the profile's filename, sans extension.
However, http://api.drupal.org/api/function/install_main/7 does...
// Load the profile.
require_once "./profiles/$profile/$profile.profile";
You can select "Reviews" from the profile listing, but when you proceed to the next screen you get fatal errors because there is no profiles/reviews/reviews.profile.
So either Drupal should not list profiles where the directory and .profile name don't match (confusing..) or we ought to allow these to differ, perhaps by having install_select_profile return the entire profile file result, or at least the path as well as the name.
In the meantime, I'm off to go rename all my functions to ch04_reviews_XX. Bleh. :P
Comments
Comment #1
mr.baileysMarked this one as a duplicate of #94009: Allow .profile files in differently-named directories.
Comment #2
Pedro Lozano commentedPatch for review on the other issue.