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 am unable to complete the installation because of PHP Notices. Past the initial screen that allows me to choose an installation profile, my screen is filled with a lot of this:
Notice: Constant MARK_READ already defined in /Sites/drupal-7.x-dev/includes/theme.inc on line 24 Notice: Constant MARK_NEW already defined in /Sites/drupal-7.x-dev/includes/theme.inc on line 29 Notice: Constant MARK_UPDATED already defined in /Sites/drupal-7.x-dev/includes/theme.inc on line 34 ...
Is this a known issue? I couldn't find any other issues reporting this.
Comments
Comment #1
Magnity CreditAttribution: Magnity commentedWhat version of PHP are you using?
Comment #2
dboulet CreditAttribution: dboulet commentedPHP 5.2.11 on MAMP.
Comment #3
eMPee584 CreditAttribution: eMPee584 commented..just ran into this aswell, seems to be called by strange APC behaviour if
apc.include_once_override=1
is set (will presumably become unnecessary with PHP5.3 anyways). If indeed you have APC enabled with this, try settingapc.stat_ctime=1
aswell and relaod your apache conf. See http://pecl.php.net/bugs/bug.php?id=15356 for reference...Comment #4
dboulet CreditAttribution: dboulet commentedThanks eMPee584, yes I think that this could be a bug with APC, I think that it was causing theme.inc to be included twice. Setting
apc.stat_ctime=1
did not solve the issue, but turning off APC completely did get ride of the warnings, though I was still seeing this:A separate issue?
Edit: see #671366: Installer is broken for more about this warning.
Comment #5
dboulet CreditAttribution: dboulet commentedI think that last warning was caused by the absence of a settings.php file, a separate issue.
So is there anything that we can do about this? Or is this purely an APC bug?
Comment #6
dboulet CreditAttribution: dboulet commentedAccording to http://pecl.php.net/bugs/bug.php?id=15356, include_once_override is an experimental feature with known issues, so I supposed that the solution is to turn off this feature.