Forums / Install & configuration / PHP 4.1 or PHP 4.2.3 required -- conflicting documentation -- help?

PHP 4.1 or PHP 4.2.3 required -- conflicting documentation -- help?

Next topic

Author	Message
Matthew Knapp	Friday 16 May 2003 10:50:25 am In the "Key Features in eZ publish 3.0" page (http://ez.no/sdk/changes/view/features) it states "Installation improvements eZ publish 3.0 runs with standard Apache 1.3 or 2.0, PHP 4.1 or newer, and MySQL or PostgreSQL. No need to compile patches. In addition to this, it has an installation helper that lets you do a large part of the installation in your browser. " Most other docs refer to 4.2.3 though. I am curious: -Which does it require? -If it DOES require 4.2.3, why? Is there a work-around? I ask because my hosting service runs 4.1.2 and is very reluctant to upgrade... yet I still want to try to run ezPublish 3.X. Thanks!
Jo Henrik Endrerud	Saturday 17 May 2003 7:40:37 am AFAIK eZ publish 3 does not use any PHP functionallity added after PHP 4.1. Technicaly it should therefore work with PHP 4.1. However, we have experienced troubles in some PHP 4.1 versions because of bugs in PHP regarding the sessions. This is the reason why we have changed our documentation to say that eZ publish need PHP 4.2.3. Unfortunatly we haven't changed every place this is written :( I'm not quite sure at the moment which PHP versions in the 4.1 and 4.2 series that are affected. eZ publish might work with earlier versions of PHP (versions prior to 4.1.0 will not work) but this might vary on which PHP version, server architecture and so on. Jo Henrik Endrerud \| System Developer @ Seeds Consulting \| http://www.seeds.no
Tony Wood	Saturday 17 May 2003 10:00:26 am Matthew, We have run on 4.1.2 without any obvious and noticable problems. The problems i believe are related to sessions not being handled correctly. However, the stress testing we have carried out has shown 4.3.1 outperforms 4.1.2 and so i would go for that if possible. We are still running these test on our new upgraded production environment so will know more soon. Tony Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Jeroen van Gorkum	Sunday 18 May 2003 4:49:34 pm see also: 'Log in problem (PHP related)' (http://ez.no/content/view/full/21884/) jeroen.
Matthew Knapp	Thursday 22 May 2003 8:17:17 pm Thanks for the insight. I will give ezPublish 3.0 a try on the 4.1.2 system. Hopefully I won't have too many problems. :) Noticed the 4.1.2 issues revolve around sessions... Does this mean the admin sections will be unaccessible due to being unable to initialize a session or is this just issues with the login capability of the published site. Anyhow, will be trying it out and will let you know the results. Again, thanks for the help. Matthew
Jeroen van Gorkum	Monday 26 May 2003 8:39:21 am > Does this mean the admin sections will be unaccessible > due to being unable to initialize a session or is this just > issues with the login capability of the published site. no, not 'unaccessible' but a site can be 'hard to access'. like i wrote in the other post, moz/win seems to find a way past the error, while ie/win & lyx/win display a browser error. if i keep refreshing the site (request the url again) in the last two, i'll get past the error eventually. once i'm 'in', there doesn't seem to be a problem anymore. this applies to both a visitor site and an admin site, but it doesn't happen always, and i haven't found a way yet to force the error. you can tell that it happened by one or more lines like this in the <em>main</em> apache error.log: [Mon May 26 17:08:28 2003] [notice] child pid 23487 exit signal Segmentation fault (11) jeroen.
Ace Suares	Wednesday 09 July 2003 9:14:32 pm The solution to the segmetation fault in 3.0.2, might be upgrading to php 4.2.3 If you run woody stable, check http://www.apt-get.org It will lead you to debian packages for php 4.2.3 for debian woody (unoffical packages, but it worked for me). _Ace