Just downloaded and then updated a website, and got this on update

Fatal error: Call to undefined function: filter_xss_admin() in /home/ranford/public_html/v2/themes/engines/phptemplate/phptemplate.engine on line 191

I then uploaded the older version of phptemplate.engine from RC1

now the site is ok

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

Did you update all files? filter_admin_xss is defined in filter.module.

metapunk’s picture

metapunk commented

I see this is a duplicate problem. I was going to submit a more indepth bug report but here is what I got.
I can't figure out why Drupal did this, but I had to modify the source code to get it to work and everything else seems to work fine.
I transferred a drupal install from one server to another and moved the database. First I got an error relating to Mysql charsets but this was resolved via updating to the latest RC2 from 1.

The new server is running PHP5 vs. 4.4 on the other.
After the update I immediately got this error.
Fatal error: Call to undefined function filter_xss_admin() in phptemplate.engine

Line 146 $mission = filter_xss_admin(theme_get_setting('mission'));
Line 191 'footer_message' => filter_xss_admin(variable_get('site_footer', FALSE$
I deleted this function from line 143 and line 191 and the site worked fine, which led to me to submit this bug report, since it appears to be a bug. I have filter.module and it contains filter_xss_admin but for some reason Drupal was erroring on in this so I thought I would submit this for further scrutiny.

Steven’s picture

Steven commented
Status: Active » Closed (won't fix)

Impossible to reproduce on a correctly installed site.

mike stewart’s picture

mike stewart commented
Version: 4.7.0-rc2 » 4.7.2
Status: Closed (won't fix) » Active

this seems to be REAL

I've installed no less than TEN drupal 4.6 sites... really. Extensive 4.6 experience in hte last year and Im pretty confident I know what Im doing at this point.

my first 4.7 install resulted in this error. my GUESS is its related to server/apache/php/mysql versions conflict somewhere.

I'll look into it further... but felt this should be reopened -- as it seems to be a real bug.

my setup:

apache: 1.3.36
mysql: 4.1.19-standard
php: 4.4.2

mike stewart’s picture

mike stewart commented
Status: Active » Closed (won't fix)

this was apparently fixed in 4.7.2

The bug I encountered was in 4.7.1, which I had downloaded on 5/31 -- and until I ran into this bug didnt realize there had been a maintenance release the very next day (6/1).

I simply reinstalled using 4.7.2 and problem disapeared