I had wondered about something like this myself, actually. The way I
understand it, messages were created for the admin interface, where
they'd always only be successful, since arrors are handled separately.
But, given that messages are available elsewhere (I'm using them
extensively in a project)
I submitted a ticket for this the other day.
Any suggestions?
http://code.djangoproject.com/ticket/3995
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
Sorry, i will move my post to django-users.
utf-16 isnt needed to represent spanish alphabet.
On 11 abr, 19:35, "oggie rob" <[EMAIL PROTECTED]> wrote:
> This is a question for django-users, but I'll do the usual "chastise
> then help" post :)
>
> The problem is because XML uses settings.DEFAULT_
hi,
when setting up a GenericForeignKey with non-standard ct_field and
fk_field, you need to specify those fields at the corresponding
GenericRelation as content_type_field and object_id_field again; this
does not feel quite correct (speak: DRY), but i don't know enough about
the way relation cou
This is a question for django-users, but I'll do the usual "chastise
then help" post :)
The problem is because XML uses settings.DEFAULT_CHARSET of 'utf-8',
which is the standard XML character set. You will need to change this
to 'utf-16', I think.
So, in your settings file, add the line:
DEFAULT
Deeper into the use case.
I have a tag, that generates IDs for tags, if needed, stores them and
finally at the end of the page it prints them into a JS array, which
is used to process the IDs (in my case IDs of dojo widgets).
Without the template tag my code would look like this:
djConfig.search
On Apr 11, 8:10 am, "Wolfram Kriesing" <[EMAIL PROTECTED]>
wrote:
> The "add_data" adds the data to the context inside the render()
> function of the tag. Here lies the problem, the scope of the for loop
> gets destroyed when the for loop ends
Well, in a template context, that does make more sens
LadyDate was removed in changeset 4985
(http://code.djangoproject.com/changeset/4985). This is great, as the
funciotnality here is not really needed and the new handling using a
callable object is much simpler.
What I'm missing now is the possibility to use callbacks in (new)forms
as well (for
On Apr 10, 6:51 pm, Ian Holsman <[EMAIL PROTECTED]> wrote:
> The zyons version allows for:
> - constants at the site level (ie max blog comments can be different
> on different sites)
True, site-awareness would be a definite benefit that I hadn't yet
included.
> - allows users (registered and an
Hi people,
Im trying to use the serialize utils in
django.core.serializers.xml_serialize and
django.core.serializers.json, i dont have problems using json but i
have issues trying something like that:
xml = serializers.serialize("xml", Anymodel.objects.all())
If the model data contains unicode
On Apr 10, 6:28 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> How would a FileField or an ImageField work? How would the proposed
> CreatedTimestamp/ModifiedTimestamp fields work?
> ForeignKey? yikes.
Very true. I hadn't considered the many fields that wouldn't even make
sense themselves i
I like your idea because it doesn't add a new option to the admin
class. I went for the simplest possible implementation while this
would require modifying a bit newforms to allow editable=False fields
to be forced in. On the other hand, one might want to have some
editable=True fields as readonl
On 4/11/07, Simon G. <[EMAIL PROTECTED]> wrote:
>
> Hi Jay,
>
> Someone reported that issue a few weeks ago, and I added a quick patch
> for this here:
>
> http://code.djangoproject.com/ticket/3830
>
> It can probably be enhanced beyond that though.
D'oh, I should have checked Trac first :)
I wo
I have written a new tag "add_data", which (if i break it down) does
only store some data, that it gets passed or generates (in the example
below it gets the data from the template, for easier demonstration)
{% add_data "one" %}
{% for u in users %}
{% add_data "two" %}
{% endfor %}
{% add_
Hi Jay,
Someone reported that issue a few weeks ago, and I added a quick patch
for this here:
http://code.djangoproject.com/ticket/3830
It can probably be enhanced beyond that though.
--Simon
On Apr 11, 4:43 am, "Jay Parlar" <[EMAIL PROTECTED]> wrote:
> Recently in [1], someone ran into a pro
15 matches
Mail list logo
