[support] PHP 5.3 upgrade problems

[andy baxter]

Victor Kane wrote:
> Can't you specify the version of PHP in .htaccess or something?
I didn't know that was possible. I'll talk to the server admins about it.

Thanks,

andy
>
> On Tue, Oct 13, 2009 at 3:02 PM, andy baxter 
> <andy at earthsong.free-online.co.uk 
> <mailto:andy at earthsong.free-online.co.uk>> wrote:
>
>     I don't really have much choice about the PHP version we're using
>     unfortunately. I have been contracted to design an interactive
>     site for
>     a university department, and they are very keen to have it running on
>     their own server, which runs 5.3. It might possibly be an option
>     to move
>     the site to a commercial server, but so far most of the errors I am
>     getting seem to be non-fatal, so I am thinking to try and make the
>     best
>     of things on this server rather than ask them to switch.
>
>     andy
>
>     Michael Prasuhn wrote:
>     > I wouldn't recommend 5.3 for Drupal for a long time.
>     >
>     > PHP 5.2 series is still getting updates and is at 5.2.11.
>     >
>     > While Drupal 6.14 is technically compatible with 5.3 (it suppresses
>     > deprecated warnings for use of ereg) it is highly doubtful that much
>     > of contrib is compatible, and probably won't be for a long long
>     time.
>     >
>     > -Mike
>     > __________________
>     > Michael Prasuhn
>     > 503.512.0822 office
>     > 503.539.3864 cell
>     > 503.661.7574 home
>     > mike at mikeyp.net <mailto:mike at mikeyp.net>
>     > http://mikeyp.net
>     >
>     > On Oct 13, 2009, at 9:30 AM, andy baxter wrote:
>     >
>     >
>     >> Hi all,
>     >>
>     >> I have recently moved a site from my test server (which is
>     running php
>     >> 5.2) to the live server (which is running php 5.3).
>     >>
>     >> Since doing this, a lot of pages are throwing error messages
>     about a
>     >> function expecting a reference argument.
>     >>
>     >> I have done enough research to get some idea of what the basic
>     problem
>     >> is, but still don't feel that I understand it well enough to
>     dive in
>     >> to
>     >> trying to patch the code. So far all I have done is add
>     something to
>     >> the
>     >> template to suppress warnings for non-admin users.
>     >>
>     >> If anyone can help with this, I would appreciate it - the site is
>     >> going
>     >> public in two days and I still have some other things I need to
>     sort
>     >> out
>     >> before then. Does anyone know of any well written explanations
>     on-line
>     >> of how this issue has come about and how it affects drupal? Or if
>     >> someone on the list could take the time to explain to me what the
>     >> issue
>     >> is, that would be good as well.
>     >>
>     >> cheers,
>     >>
>     >> andy
>     >> --
>     >> [ Drupal support list | http://lists.drupal.org/ ]
>     >>
>     >
>     >
>
>     --
>     [ Drupal support list | http://lists.drupal.org/ ]
>
>