Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I don't know if this might cause problems later and/or in other places, but I thought I would post it anyway. I usually move the module and theme directory from commons over to sites/all. I have to move this file back to the commons profile in order to complete installation.
Comment | File | Size | Author |
---|---|---|---|
#5 | 1912164.commons.no_hardcode_path.patch | 547 bytes | jpontani |
Comments
Comment #1
ezra-g CreditAttribution: ezra-g commentedCan you describe how to reproduce this error?
Comment #2
Topcheese CreditAttribution: Topcheese commentedYes, what I do is remove the modules and theme directory from the commons profile and place them under the sites/all directory. I then create a directory under the sites/all/modules directory named commons to place the commons modules.
I run the install and the process stops at that error until I moved that file back. Here is the complete error.
Fatal error: require_once(): Failed opening required 'profiles/commons/themes/contrib/commons_origins/commons_origins.palettes.inc' (include_path='.;\xampp\php\PEAR') in C:\xampp\htdocs\profiles\commons\commons.profile on line 160
Edit: My mistake, I forgot that what I did was edit the path in commons.profile, and not move the file back.
Comment #3
ezra-g CreditAttribution: ezra-g commentedSo to confirm you only get this error when you rearrange the filesystem?
Comment #4
Topcheese CreditAttribution: Topcheese commentedProbably so as that is the only way that I have been installing it from day one.
Edit: Well, not the only way, but it has been the main way that I install it to test out for multi-site.
Comment #5
jpontani CreditAttribution: jpontani commentedAttached a patch that uses the drupal_get_path function to find the path to the commons_origins theme without having to hardcode it.
Comment #6
ezra-g CreditAttribution: ezra-g commentedThanks, jpontani. Have you tested this patch?
IIRC, I didn't use drupal_get_path() because the theme isn't enabled at that point in the installer.
Comment #7
jpontani CreditAttribution: jpontani commentedI tested it once and it worked, I'm about to test it again right now as I test some other stuff that I needed a fresh install for.
Comment #8
jpontani CreditAttribution: jpontani commentedJust ran it again and it worked for me. The theme is already in the system registry before it even gets to that step so the drupal_get_path will return a valid path.
Comment #9
ezra-g CreditAttribution: ezra-g commentedGreat - Seems RTBC then :).
Comment #10
jpontani CreditAttribution: jpontani commentedCommitted.
http://drupalcode.org/project/commons.git/commitdiff/f411566