The following error is displayed during the installation at the page where the DB configuration needs to be entered.

Reproduction:
1) Download drupal-7.x-dev
2) Follow the installation procedure in your browser

I'm using MAMP 1.9.2 with PHP 5.3.2.

Comments

droplet’s picture

droplet commented

have you enabled PDO ?

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

Yes.

alan d.’s picture

alan d. commented

There is an exception catch here, but maybe the server environment is bypassing this somehow?

    try {
      if (function_exists('db_query')) {
        $file = db_query("SELECT filename FROM {system} WHERE name = :name AND type = :type", array(':name' => $name, ':type' => $type))->fetchField();
        if (file_exists(DRUPAL_ROOT . '/' . $file)) {
          $files[$type][$name] = $file;
        }
      }
    }
    catch (Exception $e) {
      // The database table may not exist because Drupal is not yet installed,
      // or the database might be down. We have a fallback for this case so we
      // hide the error completely.
    }

So this may be related #914742: Add hook_requirements() for buggy versions of eAccelerator. If disabling opcode caching allows installation, then this should be marked as a duplicate.

alan d.’s picture

alan d. commented

More likely #947616: Warn people not to enable xdebug.show_exception_trace will help.

[edit] This looks like a xdebug trace [/edit]

catch’s picture

catch
he/him
Primary language English
commented

If it's #947616: Warn people not to enable xdebug.show_exception_trace I think we should re-open that and get the patch in.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Postponed (maintainer needs more info)

Needs feedback from Xano now.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

Disabling xdebug.show_exception_trace solves the problem. I reopened #947616: Warn people not to enable xdebug.show_exception_trace, so this issue is closed now.