I would rather see some ability to add variables when
render_to_response is hit. In other words, rather than using the
proposed mechanisms above to create a unique template, I think it would
be more usable if you were to say:
def my_admin_override(request, ...):
context, template_list = do_mos
On 4/13/06, James Bennett <[EMAIL PROTECTED]> wrote:
> Even when I copy/paste that URL (which I had to do, because my
> web-based email client didn't recognize that the Cyrillic portion of
> it was part of the URL) into Firefox, the URL encoding turns
> "çÌÁ×ÎÁ_ÓÔÒÁÎÁ" into
> "%D0%93%D0%BB%D0%B0%D
On 4/13/06, Viktor <[EMAIL PROTECTED]> wrote:
> Of course, every requested url must be URLencoded, but that is browsers
> job, and they all do it quite well.
Except that that runs contrary to the purpose of the slug. See below.
> Yes, they are (more and more every day)... (for example Wikipedia u
On 4/14/06, Rob Shakir <[EMAIL PROTECTED]> wrote:
> I've just started using django today for a internal project, which
> centres around network management. I notice that there was no support
> for the cidr PostgreSQL datatype, and so I've added it. Please find the
> diff attached.
Thanks for the
gabor wrote:
> and i'm sure you know that those cyrillic slugs, if part of an url will
> get submitted in URLencoded form. even if it is hidden by the browser.
Of course, every requested url must be URLencoded, but that is browsers
job, and they all do it quite well.
> slug = SlugField(only_a
Viktor wrote:
> The problem begins when you want to have nonenglish slug (slug on a
> language that uses nonascii characters).
> For example if I want to have a serban cyrillic slug: наслов_на_српском,
> it is perfectly valid slug if you read it on serbian, just aphanumeric
> characters + under
The problem begins when you want to have nonenglish slug (slug on a
language that uses nonascii characters).
For example if I want to have a serban cyrillic slug: наслов_на_српском,
it is perfectly valid slug if you read it on serbian, just aphanumeric
characters + underscore + hyphen, nothing
Viktor wrote:
> The story about non ASCII characters in slug started in #1602: urlify.js
> blocks out non-English chars.
>
> We tested utf-8 urls against ie, opera and konqueror and they work
> great. Firefox by default shows the urls urlencoded, but you can change:
> network.standard-url
The story about non ASCII characters in slug started in #1602: urlify.js
blocks out non-English chars.
We tested utf-8 urls against ie, opera and konqueror and they work
great. Firefox by default shows the urls urlencoded, but you can change:
network.standard-url.escape-utf8 to false
and
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> Note: the fact that I have to rename this is still relevant:
> ManyToOne by ForeignKey
> ManyToMany by ManyToManyField
In what files and locations are you having to do this?
--
"May the forces of evil become confused on the way to your house."
--
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> Now just a silly question: what is the value added by Dojo ?
A few things.
The one that most people have been clamoring for is easy AJAX
functionality; Dojo's libraries for that are really simple to use.
But the big deal for me is the packaging sys
Sorry, I came back to the version MR version I had two days ago and it
is better now.
But the filter above the left list does not work, JS console says:
Erreur : SelectFilter is not defined
Fichier source : http://localhost:8000/media/js/dojo/dojo.js
Ligne : 187
Erreur : SelectFilter is not defi
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> What I see is a simple multiselection list, so I suspect that the
> related Dojo is not loaded.
Does your browser report any JavaScript errors?
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~-
What I see is a simple multiselection list, so I suspect that the
related Dojo is not loaded.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've just started using django today for a internal project, which
centres around network management. I notice that there was no support
for the cidr PostgreSQL datatype, and so I've added it. Please find the
diff attached.
I'm not sure if there'
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> How do I specify the use of Dojo rich-text editing widget in my model ?
You'll want to take a look at Dojo's documentation at
http://dojotoolkit.org/docs/
> I don't know why M2M does not render properly, here is an excerpt of
> the displayed page so
If someone wants to make a small customization to the admin templates,
they have to override the whole template. This can be very frustrating
if you just want to change something like the title, or userlinks for
one page. You can't just extend admin/change_form as
admin/myapp/mymodel/change_form,
My copy of MR has been updated yesterday evening.
How do I specify the use of Dojo rich-text editing widget in my model ?
I don't know why M2M does not render properly, here is an excerpt of
the displayed page source:
...
dojo.setModulePrefix('django', '../django');
var admi
On 4/13/06, olive <[EMAIL PROTECTED]> wrote:
> to make it work I had to replace in your views all occurences of:
> ManyToOne by ForeignKey
> ManyToMany by ManyToManyField
The patch was extracted from a modified copy of magic-removal which
I'd been running for a while, there should have been no ne
James,
to make it work I had to replace in your views all occurences of:
ManyToOne by ForeignKey
ManyToMany by ManyToManyField
The only problem for me so far is that TextField are no more handled by
TinyMCE.
Just one reproach: the widget use for ManyToMany was better before Dojo
(MultiSelect co
On Apr 13, 2006, at 8:48 AM, James Bennett wrote:
> Already done; it's in Trac: http://code.djangoproject.com/ticket/1613
FYI, I'm working on making a custom Dojo build with all the sweetness
that James put together but having some issues with the build
system. Once that's done, I'll be chec
On Apr 13, 2006, at 7:33 AM, Denis wrote:
> It looks like django.contrib.comments.models (M/R) lacks get_user()
> method for the
> following classes: Comment, KarmaScore and UserFlag. Didnt find any
> suitable component
> choice in the ticketing system, so i decided to post here. I wonder
> what w
On 4/13/06, Bjørn Stabell <[EMAIL PROTECTED]> wrote:
> Could you make it available as a patch against the latest magic-removal
> branch?
Already done; it's in Trac: http://code.djangoproject.com/ticket/1613
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
Could you make it available as a patch against the latest magic-removal
branch?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googl
Hi
It looks like django.contrib.comments.models (M/R) lacks get_user()
method for the
following classes: Comment, KarmaScore and UserFlag. Didnt find any
suitable component
choice in the ticketing system, so i decided to post here. I wonder
what would be the proper way
to fix this, coz ``self.use
Hmm ... not much feedback :-(
Please, could one of the core developers just give a short statement
like "interested" or "not interested" on this? Even a "maybe" would be
better than no feedback at all.
It just makes a difference if I do this only for my project or try to
solve it cleanly.
Mi
26 matches
Mail list logo
