I have just installed drupal 7.2
apache and php were built from source and MySQL is ubuntu 10.04 binary Server version: 5.1.41-3ubuntu12.10 (Ubuntu)
I get many of these warnings:- when loading the drupal page and more when logging in:-
Warning: in drupal_validate_utf8() (line 1387 of /usr/local/httpd-2.2.17/htdocs/drupal/includes/bootstrap.inc).
Warning: in drupal_clean_css_identifier() (line 3642 of /usr/local/httpd-2.2.17/htdocs/drupal/includes/common.inc).

If this is a known issue please point me to the cure.
thanks
ohn

Comments

VanD’s picture

You should post the lines and the context that surrounds them so we can see in what context that call is failing.

- Craig Vanderlinden @cvanderlinden

ohn’s picture

Turns out my problem was the apache build had default pcre internal support on.
re-compiled apache adding --with-pcre=/usr
libpcre.so.3 was already in /usr/lib

this at least allows the drupal installer to run without warnings.

peachgreen’s picture

I had exactly the same problem with my aws EC2 instance (Apache 2.2 + PHP 5.3.10 + Drupal 7.12).

The warnings were:

• Warning: in drupal_clean_css_identifier() (line 3708 of /var/www/html/includes/common.inc).
• Warning: in drupal_validate_utf8() (line 1606 of /var/www/html/includes/bootstrap.inc).

It turned out to be related with the version of PCRE. So you can simply solved the issue by:
yum -y update pcre

Or, you can update the version of PHP by
yum update php

Both of them work like a charm.

unqunq’s picture

I am running on AWS and restarted the server when a broken apache hosts file kicked in. It was pointing to a non existing folder and I was getting that error.

I resolved by correcting the wrong .conf file.

jsimonis’s picture

Updated to PHP 5.3 this evening and I am getting a ton of the same errors. Line numbers vary slightly, but same errors:

Warning: in drupal_clean_css_identifier() (line 3731 of /home/starter/public_html/includes/common.inc).
Warning: in drupal_validate_utf8() (line 1606 of /home/starter/public_html/includes/bootstrap.inc).

I pointed the web host to this page and another and he said the problem is with 5.3 and that I have to downgrade. Going to do that for now since it is after 5 a.m., I've been up all night, and sites have to work. But I seriously doubt this is an issue with 5.3 I'm not running anything out of the ordinary and this is hitting sites that are completely up to date as well as ones that need updates.