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 > >
