Hello,

i just wanted to install drupal 7 alpha 2, the minimum configuration, on my webspace and got following error-message:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://subdomain.mydomain.de/install.php?q=install.php&profile=minimal&l... StatusText: OK ResponseText: Fatal error: Class 'FieldException' not found in /var/www/username/html/mydomain/subdomain/modules/field/field.attach.inc on line 12

After that i get to the configuration site to enter site information and my username.
When i enter and save them, i get this message:

Fatal error: Class name must be a valid object or a string in /var/www/username/html/mydomain/subdomain/includes/common.inc on line 6011

When i now enter http://subdomain.mydomain.de i get this:

Fatal error: Call to undefined function user_access() in /var/www/username/html/mydomain/subdomain/includes/theme.inc on line 2248

Seems that i can't use Drupal 7- Alpha 2 on my webspace :(

Comments

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
commented

This could be a duplicate of #686596: Child before parent class definition order breaks some opcode cachers. Are you using APC or eAccellerator?
Also, I recommend to test again with the latest dev version when you run into errors. The problem may have been fixed since alpha2.

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
commented
Status: Active » Postponed (maintainer needs more info)
MaWe4585’s picture

MaWe4585 commented

Yes there is eAccelerator v. 0.9.6 activated, but since it is only webspace, i think i can't deactivate it.
Why is this eAccelerator a problem and will it be solved?

I also tried the dev Version, same problem.

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
commented
Version: 7.0-alpha2 » 7.x-dev
Status: Postponed (maintainer needs more info) » Closed (duplicate)

I don't know what exactly causes this problem, except that it's related to optimizers like APC and eAccellerator. Will it be fixed? Well, it will not fix itself, obviously. If it will be fixed if someone takes the time to find the cause and write a patch. I'm marking this as duplicate of #686596: Child before parent class definition order breaks some opcode cachers; if you can help solve this error, please use that issue.