It appears that this installation profile does not work on PHP 5.3. It appears I will need to figure out how to to downgrade my PHP version. My first attempts to do so did not work because of quirks with XAMPP. Let me know if you have any advice or if there is a plan to make this compatible with PHP 5.3.

Thanks!

Comments

febbraro’s picture

Can you post the error message that specifically names which file causes this error? Drupal 6.14 itself supports PHP 5.3, but it is probably that one of the contributed modules included in OpenPublish does not. Your report will help us get this fixed either in OP or in the contrib module.

Thanks.

davidgtuttle@gmail.com’s picture

When trying to run the install there are about 50 errors from this file - "includes/file.inc". I don't have the exact error messages anymore, sorry.

I had to uninstall XAMPP 1.7.2 and install a clean copy of 1.7.1 to get PHP 5.29 set up correctly. The error log was deleted by the XAMPP uninstall of 1.7.2. I did a search for "ereg(" under the openpublish installation directory and found these files:
file.inc
unicode.inc
user.module
filefield.module
date_php4_calc.inc
date_repeat_calc.inc
phpFlickr.php

There may be some false positives based on the search method. There are other deprecated functions in 5.3 that may cause problems too. I had a similar problem with BBpress for WordPress.

febbraro’s picture

I think they are likely deprecation *warnings* and not *errors*, meaning things should still function correctly with just some annoying warning messages. Until the maintainers of those modules fix the egrep fucntion those warnings will continue. You have 2 choices at this point.

#1) Revert to using PHP 5.2.x
#2) Hide the deprecation warnings. You can do that in php.ini like so:

error_reporting = E_ALL & ~E_DEPRECATED
laro’s picture

works on xamp windows1.7.3 but doesn't on wamp 2.0

irakli’s picture

Status: Active » Closed (fixed)

Considering the list of functions causing the error (practically all of them - Drupal Core) and fix suggested by Frank, this should be fixed/closed as far as OpenPublish is concerned.