Re: Still problems with 1.4.19 and "you must be logged in" error

On 7/2/09, Maimuța Polară <[email protected]> wrote:
> On Thu, Jul 2, 2009 at 7:27 PM, Paul Lesniewski wrote:
>>
>> SM 1.4.x is not compatible with session.auto_start.  If you run
>> configtest after you configure SM, you'd see that.  This is not a bug
>> and is the way the product works.
>
> For us, simple users of squirrelmail and admins having to install and
> configure it, this incompatibility is acknowledged unfortunately only
> in the last version, 14.19, released just a few weeks ago.
>
>>  The OP of this issue didn't state
>> if that was his problem, and if not, it might have something to do
>> with storing session data in a database.
>
> If the only changes he made were the ones described, then I suspect
> that he had session.auto_start enabled because the problem was solved
> by deleting the session_regenerate_id() call.
>
>> No "fix" for this is intended.  Please run src/configtest.php before
>> you try to use SquirrelMail.
>
> Please consider the fact that some of us use the squirrelmail package
> coming with the distribution we have, we don't install it from
> scratch. Until today I haven't knew about configtest.php.  On the few
> systems where I installed and configured squirrelmail I just added the
> configuration lines I needed into config_local.php and squirrelmail
> worked.
>
> If the OP had indeed session.auto_start enabled, it looks like he did
> not run configtest.php either. It looks like the other poster, Ken,
> who said that he solved the problem by disabling session auto start,
> did not run configtest.php either.
>
> I suppose that you, as a developer of squirrelmail, would like to have
> every person installing and configuring squirrelmail run
> configtest.php before using it, but the reality shows that not all
> people do that. We want to complete our tasks in the shortest time
> possible, which means we sometimes don't start by reading the docs so
> we don't know about configtest.php. We have the tendency to hope that
> all is required to make squirrelmail work in simple setups is to add
> or change a few lines in the squirrelmail configuration.

I think the posting guidelines mention configtest.php.  Perhaps many
admins want to spend as little time on their systems as possible, but
I consider it a profound lack of awareness, compassion and respect
when people come here asking questions without reading, understanding
and following the posting guidelines.  Those of you coming here for a
quick fix think we here don't also value our time like you do?

> I think it would help us, the users of squirrelmail, if a "fix" (not
> changing the session name) or an improvement (warn in error_log if
> session auto start is enabled) is implemented eventually. The "fix"
> would just make squirrelmail work, no matter what is the status of
> session auto start (I acknowledge I could be missing something here),

Yes, you're missing the great complexity involved.  Our development
code works either way, but 1.4.x won't be fixed in that manner.
However, your point is well-taken and I have instead implemented a
section in the startup code that will check for incompatible PHP
settings and flat-out stop (refuse to run) until said settings are
fixed by the admin.

> while warning about the incompatibility will give us a fast hint about
> what's wrong since we are used to look into error_log when something
> is not working.
>
> The point I'm trying to make is that the "fix" or improvement is so
> small that is worth making it since less people would be affected by
> this incompatibility.
>
> Thank you!

Thanks for your thoughts.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donations.php

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [email protected]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel