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.
Hi all --
Thanks to everyone who's already offered. I'm about to take off for a
weekend hiking trip, and it looks like I won't have a chance to get
back to anyone until Sunday night or Monday.
I've definitely got *plenty* of options -- this community rocks! --
but don't let that stop you from
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 Jun 26, 8:14 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> Documentation of the new features is can be found in
> ``docs/upload_handling.txt``
> orhttp://code.djangoproject.com/git/?p=django;a=blob_plain;f=docs/uploa
Just a small thing:
"""
Like any data supplied by the user, you
Well, IMHO Jannis patch solves the problem for non internationalized
applications (probably not 99% of them), and in a way that isn't the
best one (also IMHO).
I think that the best way to pass a i18n parameters from python
libraries to javascript is the existing view '/admin/jsi18n/'. Doing
it
2008/6/26 Jannis Leidel <[EMAIL PROTECTED]>:
> This is a double-edged sword, on the one hand it would be wonderful to
> have complete locale support but on the other hand this makes issue
> #1061 larger than it really is. My patches there fix the interface
> bugs, but should be replaced by a
This, with more elaborate explanation, is now issue 7550, at
http://code.djangoproject.com/ticket/7550.
Andreas
On Donnerstag 26 Juni 2008, Andreas Klöckner wrote:
> Hey there,
>
> I tried to submit this bug, but it wouldn't let me--it thought I'm a
> spammer. You should really work on that
Hey Jacob,
FYI: Our environment isn't that bizarre (Apache/Debian), but we've been
running patch #2070 in production on Pownce for a couple weeks now (we
actually ran a back-ported version of #2070 on 0.96 before we moved to
trunk). It's been working beautifully, and has really improved
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?
>
>
On Donnerstag 26 Juni 2008, Collin Grady wrote:
> Andreas Klöckner said the following:
> > Well, then the web site should hint at this fact, too. I was fairly close
> > to just abandoning the effort of trying to tell you about the issue I
> > encountered.
>
> It does. Quite clearly at the top of
Andreas Klöckner said the following:
> Well, then the web site should hint at this fact, too. I was fairly close to
> just abandoning the effort of trying to tell you about the issue I
> encountered.
It does. Quite clearly at the top of the 'new ticket' page, there are
several notes about
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 Donnerstag 26 Juni 2008, [EMAIL PROTECTED] wrote:
> To avoid spam detection sign up.
Well, then the web site should hint at this fact, too. I was fairly close to
just abandoning the effort of trying to tell you about the issue I
encountered.
Andreas
signature.asc
Description: This is a
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
To avoid spam detection sign up.
On Jun 26, 3:06 pm, Andreas Klöckner <[EMAIL PROTECTED]> wrote:
> Hey there,
>
> I tried to submit this bug, but it wouldn't let me--it thought I'm a spammer.
> You should really work on that spam detection thing, it should not turn away
> real submissions.
>
>
Hey there,
I tried to submit this bug, but it wouldn't let me--it thought I'm a spammer.
You should really work on that spam detection thing, it should not turn away
real submissions.
Here's the bug:
Hi Marc,
> IMHO this patch is very important, specially for all Django
> developers/
> users working on countries where Sunday is not the first day of the
> week, that are many [2]. It also be great to allow setting the date
> format that is used in admin, and may be the whole Django.
I
On Thu, Jun 26, 2008 at 3:14 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> As far as I'm concerned, #2070, adding large streaming uploads, is
> done. I'd like to get some public kicking-of-the-tires before I push
> the change to trunk (which won't happen before Tuesday: I'm
2008/6/26 Marc Garcia <[EMAIL PROTECTED]>:
>
> Hi all!
>
> I'll start working on a new (hopefully better) patch for ticket #1061
> [1] that will allow customization of first day of week on django's
> admin calendar.
+1 on that Mark.
If I can help just let me know.
--
Antoni Aloy López
Blog:
Also, if anyone is going to PyOhio(July 26) perhaps we can get some
work done there.
On Jun 26, 10:41 am, Rob Hudson <[EMAIL PROTECTED]> wrote:
> OSCON is July 21st to the 25th in Portland, OR. It's not in a date
> range listed but I'm curious if something could be arranged there? If
> not a
Hi all!
I'll start working on a new (hopefully better) patch for ticket #1061
[1] that will allow customization of first day of week on django's
admin calendar.
IMHO this patch is very important, specially for all Django developers/
users working on countries where Sunday is not the first day
Hi Karen,
On Thu, Jun 26, 2008 at 12:41 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> I have a suggestion to help ensure that Django 1.0 gives a good first
> impression to new users: line up some install testers for the gamut of
> supported platforms, and have these testers verify (prior to
Hi folks --
As far as I'm concerned, #2070, adding large streaming uploads, is
done. I'd like to get some public kicking-of-the-tires before I push
the change to trunk (which won't happen before Tuesday: I'm taking a
long weekend off).
You can get the code either from my git repository
On Thu, Jun 26, 2008 at 7:36 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> The various Javascript toolkits vary wildly in their implementations;
> any API attempting to unify them would necessarily become a
> toolkit-onto-itself, which is *way* out of Django's scope.
Totally agreed.
> Many of us
>
On Thu, Jun 26, 2008 at 9:05 AM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I understand there are some complexities involved, but essentially its
> just creating a uniform javascript API to use - not unlike the may we
> have a uniform database api.
That's a gross understatement. :-)
The various
On Thu, Jun 26, 2008 at 9:41 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> I have a suggestion to help ensure that Django 1.0 gives a good first
> impression to new users: line up some install testers for the gamut of
> supported platforms, and have these testers verify (prior to release) that
>
I have a suggestion to help ensure that Django 1.0 gives a good first
impression to new users: line up some install testers for the gamut of
supported platforms, and have these testers verify (prior to release) that
the documented installation procedure works correctly on their platform.
OSCON is July 21st to the 25th in Portland, OR. It's not in a date
range listed but I'm curious if something could be arranged there? If
not a sprint maybe a BOF or just a meet and greet?
On Jun 25, 3:58 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> Hi folks --
>
> I'm setting up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 25, 2008, at 23:47, James Bennett wrote:
> 3. As someone who hangs out in the channel pretty much 24/7 I can
> vouch for him being helpful. An instructive example is to run "grep
> thanks #django.log | grep -c Magus", and then compare to
On Wed, Jun 25, 2008 at 5:10 PM, Alex Ezell <[EMAIL PROTECTED]> wrote:
>
> I'd like to offer one more perspective. Magus- (Collin) was one of the
> first folks to help me in the IRC channel. And, initially, I did think
> to myself "well, that's a little smug."
>
> Then, I tried helping people the
Could this not be further discussed?
I understand the need to be toolkit agnostic, but could we not take a
similar approach as the Ext js framework, where by you can use one of
many existing frameworks as your base. Then the django community can
build connectors as demanded.
I understand there
On Thu, Jun 26, 2008 at 3:41 PM, OliverMarchand
<[EMAIL PROTECTED]> wrote:
> === Form Field/Widget ===
>
> The normal ChoiceField has no ordering. I am no Javascript expert, but
> I think it is very simple to write a widget where the selected choices
> can also be ordered. Assuming that the
Dear Django Developers,
I think Django is really wonderful, but I am puzzled that it contains
so few "ordering features". We often have the case that a user wants
to select from a list of possible choices (normal select) *plus* wants
to specify an ordering. Typically in applications this is done
On Jun 25, 4:58 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> I'm setting up sprints leading up to the 1.0 release, and I need some
> volunteers to host a couple of 'em.
>
> So we need a spot for 8/1, 8/15, and 8/22 -- any takers?
It's just out of your date range, but the Utah Open Source
earn and learn!!
hi ! friends welcome to earn and learn .
earn monthly 10,000/-
just work two hours in a day.house makers and college students have a
great oppurnaties!.
for more click it!
I know that a URL resolver refactor is on Malcolm's neverending todo
list. When he starts getting back into it, feel free to remind him of
it. :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
39 matches
Mail list logo
