By tcochran on

Existing Drupal site broke yesterday -- just throws off blank page -- see unresolved issue at http://drupal.org/node/159872

When I try to upgrade from 4.7.4 to 4.7.6, I get a different error:
Call to undefined function: filter_xss_bad_protocol

In tracing this, I find that filter.module IS properly installed on the server -- but just as with node.module yesterday, the system can NOT seem to find it.

In another post, someone suggested that a cause could be that "modules directory is not readable by apache". If that's the case, then how is that changed?

PHP is working fine on the server, all Drupal files seem to be there and with proper file sizes.

Drupal just seems to be confused about the path to the modules.

⋅ Categories: Drupal 4.7.x

Comments

vm’s picture

vm commented

I'd try going from 4.7.4 to 4.7.5 as the update release node states. see: http://drupal.org/comment/reply/160034

specifically:

For the most trouble-free transition from an existing installation, it is recommended that you first upgrade to Drupal 4.7.5
tcochran’s picture

tcochran commented

Hi, thanks for the tip -- but I couldn't even get that far with the Drupal files.

I gave up and rolled back the files to a point prior to Drupal going blank