One thing that will be happening to us all shortly is php5.3 showing up everywhere, and Drupal is only slowly coming to readiness for that. Depending on the version you have and the contrib modules you have there may be many repercussions.
PHP 5.3 is a major version upgrade but is being treated in many places as a minor version upgrade with some pretty significant consequences. I have no idea how that could relate to the problems you have, of course. -Randy On Thu, Mar 4, 2010 at 6:27 AM, Tomáš Fülöpp (vacilando.org) < [email protected]> wrote: > That's the thing -- there is no error message anywhere :-( > Not in PHP error log, not in dblog / watchdog, no Drupal message, and no > problem highlighted in /admin/reports/status. > Total mystery -- how can an image on a valid private path display but it > kills the session? > > PHP / Apache upgrade may have happened -- I can pose this question to the > cloud admins -- but what specifically would wreak this kind of havoc... what > should they look for? > > Thanks.. > > .t > > > > > On Thu, Mar 4, 2010 at 13:27, Drupal <[email protected]> wrote: > >> Tomáš Fülöpp (vacilando.org) wrote: >> >>> --8<-- >>> >>> So the question is -- what could have caused change. /Why did >>> http://WWW.DOMAIN.TLD/en/system/files/images/image.jpg show for a year >>> without a problem and now its mere appearance kills the user session./ >>> >>> I realize this thread possibly shifts from development / debugging issue >>> to a support one, but I hope you can bear with me for the final run. It's >>> been a crazy marathon with a site others have admin rights to so I had to >>> discover and guess what they inadvertently changed... >>> >>> Does the hosts syslog or httpd's access and error log give a clue? Was >> apache or php upgraded or a new module added? >> >> -- >> Earnie >> -- http://www.give-me-an-offer.com >> >> > -- Randy Fay Drupal Development, troubleshooting, and debugging [email protected] +1 970.462.7450
