On Wed, Jul 2, 2008 at 10:47 AM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Rob van der Linde wrote:
> > I see there is now a link to the registration page when you go to file a
> > ticket, but why not put it on page where the login/settings links are
> > (just underneath the search box). This is
Rob van der Linde wrote:
> I see there is now a link to the registration page when you go to file a
> ticket, but why not put it on page where the login/settings links are
> (just underneath the search box). This is where it is by default in Trac
> and people might expect to see it there, like I
Jacob Kaplan-Moss wrote:
> Help me out here: how can I make it more obvious?
Wow, you've certainly made it more obvious :) I pity the fool that
misses it now.
Gary
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On Fri, Jun 27, 2008 at 11:36 AM, rskm1 <[EMAIL PROTECTED]> wrote:
>
>> Help me out here: how can I make it more obvious? You missed that;
>> others often do to. Can you share with me some insights on how you
>> missed it?
>
> I'll chime in. Basic rule of thumb for GUIs:
> * If it's going to
> Help me out here: how can I make it more obvious? You missed that;
> others often do to. Can you share with me some insights on how you
> missed it?
I'll chime in. Basic rule of thumb for GUIs:
* If it's going to fail _ANYWAY_, just GRAY IT OUT!!
In other words, make the form-input fields of
I see there is now a link to the registration page when you go to file a
ticket, but why not put it on page where the login/settings links are
(just underneath the search box). This is where it is by default in Trac
and people might expect to see it there, like I did myself initially.
I've had the error before and found it difficult to find the link where
to register for an account. I had to ask in the IRC and someone had to
point me to it, I believe this could be made easier to find.
Go to code.djangoproject.com look at the tabs:
Login | Settings
Wiki, Timeline, Browse
Jacob Kaplan-Moss wrote:
> On Thu, Jun 26, 2008 at 1:06 PM, Andreas Klöckner
> <[EMAIL PROTECTED]> wrote:
>
>> I tried to submit this bug, but it wouldn't let me--it thought I'm a spammer.
>>
>
> Quoting from the ticket submission page:
>
> "If you're getting rejected by the spam filter,
Mike Scott said the following:
> Maybe the page after the block submission needs to be changed. And
> maybe you could output a copy of the submitted text too just incase
> you didn't have a copy written elsewhere.
Something wrong with your browser's back button? :)
--
Collin Grady
Stay
Jacob,
I think its the fact that we see "internal server error" and just miss
the message which is very nicely hidden after it.
Alot of django developers know what a 500 means, but generally don't
expect to see it for a spam block.
Maybe the page after the block submission needs to be changed.
On Thu, Jun 26, 2008 at 4:34 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El jue, 26-06-2008 a las 13:31 -0700, Jacob Kaplan-Moss escribió:
>> Help me out here: how can I make it more obvious? You missed that;
>> others often do to. Can you share with me some insights on how you
>> missed it?
>
>
El jue, 26-06-2008 a las 13:31 -0700, Jacob Kaplan-Moss escribió:
> Help me out here: how can I make it more obvious? You missed that;
> others often do to. Can you share with me some insights on how you
> missed it?
The sentence should be more prominent, I know nobody that will read that
many
On Thu, Jun 26, 2008 at 1:06 PM, Andreas Klöckner
<[EMAIL PROTECTED]> wrote:
> I tried to submit this bug, but it wouldn't let me--it thought I'm a spammer.
Quoting from the ticket submission page:
"If you're getting rejected by the spam filter, we apologize! The best
way to avoid that is to
13 matches
Mail list logo
