Hello. I've installed and configured Drupal 4.6 on a PHP 4.3.2 server without realizing that PHP 4.3.3 was a minimum requirement. Don't ask how, I somehow didn't see the warning!
So the mistake has been made... but Drupal is working almost perfectly anyway. The only problem I've found so far is that searching fails with two errors that look like this:
warning: Compilation failed: characters with values > 255 are not yet supported in classes at offset 52 in /home/httpd/vhosts/website_url/httpdocs/modules/search.module on line 258.
This seems to be related to internationalization but I don't really understand the problem. My question: if this is the only symptom of the problem, can anyone suggest a way to hack around this? I'd hate to "downgrade" because I think at this point it would be difficult and time-consuming, and I love the design of 4.6 so much more than 4.5. My web host is making it extremely difficult to upgrade from "php-4.3.2-19" because it's tied to my version of Plesk. (curses!)
Any suggestions would be very greatly appreciated. I'm not exactly looking for something elegant, just something to get search working!!!
Comments
Remove all characters > 255
You could always open up search.module and remove the characters from the regexps > 255 (or FF in hexadecimal) but I'm pretty sure you'll still run into massive problems as PHP 4.3.2 and earlier's UTF-8 support in PCRE is abysmal.
--
If you have a problem, please search before posting a question.
Characters > 255
Thanks for the suggestion!
I actually tried exactly that this morning. I just went in to the three RE's and took out all hex values over two digits... and it stopped giving me errors! It also hasn't returned a result yet, even though I've re-indexed the search several times, run cron.php, and in general made a number of desperate attempts to get some results. But nothing. I think I'm going to have to fix the problem and not just the symptoms. I am very afraid...
Hmmm. I have space for you...
Hmmm. I have space for you if you need a new host. :)
Seriously, if you are allowed to upgrade your own server, have shell access, use yum or up2date, add these channels to your yum.conf and/or up2date source files. (won't hurt to update both as up2date is configured to use yum)
Run an rpm -q yum to see what version is installed and if it is lower than 2.05 you should update that first.
If you prefer you can go to his site for verification: The owner of this site is one of the founders of Plesk and I trust my server updates to his RPM packages.
One of his sites is at http://atomicrocketturtle.com
His rpms work flawlessly, dependencies are checked, installed and configured.
He also has rpms to upgrade your php to 4.3.11, mysql to 4.0.24 and about everything you will ever need to maintain your server, including the PSA rpm upgrades, Fedora Core upgrades, etc....
/etc/yum.conf
CHECK THIS:: making sure your distroverpkg is set to fedora/redhat, etc...
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=fedora-release
tolerant=1
exactarch=1
retries=20
::
Add these channels to your yum.conf
[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
exclude=spamassassin
exclude=spamassassin-tools
[psa-7.0]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.0 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.0/$releasever/
NOTE: the exclude statements above will prevent you from breaking your psa-spamassassin install. If you like trouble, remove them and see. LOL
/etc/sysconfig/rhn/sources
CHECK THIS::
yum fedora-core-1 http://benny.primarydns.com/fedora/core/1/i386/os
yum updates-released http://benny.primarydns.com/fedora/core/updates/1/i386
::
Add these channels to your /etc/sysconfig/rhn/sources
# Atomic RPMS
yum atomic http://3es.atomicrocketturtle.com/atomic/art/1
# SW-Soft PSA 7.0.x RPMS
yum atomic-psa7 http://3es.atomicrocketturtle.com/atomic/psa7/1
If you use yum - run yum upgrade php
You really need to upgrade or have upgraded your php as there are some vunerabilities that need to be patched in that and subsequent versions. Don't be scared. Not trying to alarm you. Just want to give you the heads up.
Hope this will help you better maintain your server.
Very helpful...
That was one of the most helpful replies I've ever seen! Thanks so much!
One last question if I could: I don't seem to be able to find yum via White Box Linux or anywhere else, nor does MediaTemple seem to have up2date installed for me. Nor any compilers, etc.... Do you know where I can at least get yum for RedHat AS3 by chance? I can't seem to track it down, and that seems like something of a prerequisite...
Thanks again for all your help!
For Fedora Core you can grab
You are very welcome!
For Fedora Core you can grab yum with
Fedora Core 1 is
http://download.fedoralegacy.org/fedora/1/updates/i386/yum-2.0.5-1.noarc...
or just peruse the fedora site at: http://fedoralegacy.org/#main
Would trip search work
Im in a similar situation, i was thinking of linking the search box with google search but i came across a search module called trip search. Would this work with PHP 4.3.2?
dikd u find a solution?
HI rayray,
I'm in a similar position - just realised that the host has 4.3.2. They upgraded to php 4.4. but that broke their webmail so they switched back to 4.4.
I'm also tied to a plesk desk control panel.
Did you find out any workarounds?
Dub
Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate