[Bug 6242] MLS crashes with no current locale

http://bugs.xaraya.com/show_bug.cgi?id=6242





------- Comment #6 from [email protected]  2009-01-27 23:52 GMT -------
(In reply to comment #5)
> Please document that (apparently) the table *_security_acl has to 
> be emptied to make "Last resort" login work.

Sorry for my writing being not clear enough. I logged in as Last Resort Admin
(LRA) with a filled *_security_acl table and with an emptied one. Both cases
did work. I deleted the content from that table for reproducing your
description. It is not necessary to delete anything to log in as LRA.

> I would also like to understand what this has to do with the foreach over
> $this->locales that causes the error.

Perhaps nothing.

> Put differently: shouldn't a "last resort" login just work AS configured? It
> didn't. Removing ALL permissions from the database seems to defeat the whole
> purpose of a last-resort login in the first place (and I don't think it's
> advisable to do that).

Yes, the LRA should just work. Perhaps we should break the normal output
routine in index.php near line 107 to skip the event system and further
templating. This would cost the LRA the menus and blocks but will give a
greater probability that he will see something on a broken site.

> And it doesn't seem to address the issue of "no current locale" either: I
> didn't report a bug with "last-resort login, I reported a bug as "MLS crashes
> with no current locale". The last resort login was only what triggered this
> problem (IOW the *context* of the bug, not the bug itself). If emptying the
> security_acl table somehow addresses the *reported* problem of "no current
> locale" please explain the mechanism. If not, please address the *reported*
> bug, not the imagined one.

It would be easier to verify this bug if the fault is reproducable.


-- 
Configure bugmail: http://bugs.xaraya.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

---- ** IMPORTANT ** READ BELOW ** ----
[Clip Me Start]
--------------------------------------------------------------------------
If you wish, you can reply to this message directly **however**, make sure
to use the "Reply To All" feature of your client **and** ensure that the 
bug specifier is in the subject (ie: [Bug ####]). Also, you _MUST_ have 
you're From or Reply-To address set to the same address you use to log
into your bugzilla account or your reply will not be attached to the bug.
--------------------------------------------------------------------------
[Clip Me End]