Permission denied page should mention logging in if not logged in.

[pfnguyen@…]

There are many privileges I revoke from anonymous but grant to authenticated.

Permission Denied

TICKET_CREATE privileges are required to perform this operation 

When a user is not logged in and encounters the permission denied page it is not obvious that the person could log in and attempt to view the page.

Currently, not all users in my organization are trained to use Trac, however we have a single-sign-on setup and Apache/Trac supports that. Thus all users in my organization can log in to trac.

When a new user comes to trac (and I point them at /newticket or something) they get a permission denied message and don't know what to do next. Instead, maybe we could have a message that looks like:

Permission Denied

TICKET_CREATE privileges are required to perform this operation 

You are not logged in, please :login: and try again.

And with the 2nd attempt (if it still fails), present the message that the user logged in does not have the required ACL. Something like:

Permission Denied

TICKET_CREATE privileges are required to perform this operation 

Your login, $REMOTE_USER, does not have the required permissions.
[perhaps list the permissions granted here as well]

[pfnguyen@…]

let me toss in a milestone and you guys can change it from there…

[james@…]

A hacked error.cs file that kind of implements the required functionality. It's nowhere near perfect, but it's mildly functional.

[james@…]

I just attached a modified error.cs file. You can dump it in the templates folder of your configuration and it will override the default. It's based on the 0.9.4 version from the distribution, and trys to give the user hints about what they can do.

This is the first time I've looked at Clearsilver/Python, so the results aren't pretty. Take it and hack it however you like if you think it's useful.

[Christian Boos]

Milestone 1.0 deleted

[Remy Blank]

The first part (asking to login) has been implemented in [7494], released in 0.11.2 (and discussed in comment:16:ticket:5340).

We could also improve the error message as suggested in the second part.

[Remy Blank]

A slightly better error message for permission errors has been committed in [10322].