[development] Force admin login

Tomáš Fülöpp (vacilando.org) tomi at vacilando.org
Thu Mar 4 15:32:44 UTC 2010

Good point, Randy. But in our case it's PHP 5.2.6.

And to answer Earnie - no, PHP / server config have not changed recently and
in fact other D6 sites run on the same cloud happily, so this problem won't
come down to PHP / Apache versions.

One possibly interesting bit from my conversation with the tech help:
** I just talked to our sysops team and out cache server will drop the
cookie, so the cahce will have to be saved to a file as outlined here
*But I assume this is irrelevant, because cookies are saved for other pages,
even for other images, except for when they are on the private (/system)


On Thu, Mar 4, 2010 at 14:48, Randy Fay <randy at randyfay.com> wrote:

> 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) <
> tomi at vacilando.org> 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 <earnie at users.sourceforge.net>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
> randy at randyfay.com
> +1  970.462.7450
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100304/244a9437/attachment.html 

More information about the development mailing list