Emiliano wrote:
> On Sun, 30 Jan 2000, Joost Soeterbroek wrote:
>
> > You were right. It was an ownership problem. Which leads me to another
> > question. Why does a user not get a clearer error message when he/she
> > does something he/she has no right to?
>
> Currently, the function will tell yo uthat it failed, although the
> admin site makes very little use of that for reporting. The reason
> for the failure is not available in 1.2.X, and changing the return
> code of these functions (moving from boolean to x-state) is going
> to break existing Midgard applications. I agree that there should
> be a way to know, though.
>
> What does the rest of you think? Especially those who have existing
> Midgard deployments. Another (decidedly less clean) way would be to
> set a global variable (a la errno) to specify the reason for failure.
> Exceptions would be the best way to do it (IMO) but neither PHP or
> the current Midgard concepts are really well suited for it.
Ideally, when a user logged in, they would not be able to see any items
(pages, styles, elements, topics, articles) except those for which they had
at least read permission, and there would be a line somewhere on the
displayed page which said something like "Current access:
[Read-Only|Full]".
I thought that what Alexander is doing with 1.2.6 will enable this (won't
be able to look closely until I finish current implementation) . Am
I wrong here?
the cat
>
>
> emile
>
> --
> This is The Midgard Project's mailing list. For more information,
> please visit the project's web site at http://www.midgard-project.org
>
> To unsubscribe the list, send an empty email message to address
> [EMAIL PROTECTED]
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
