Re: moving to django 1.2.1

On 28 Lug, 15:44, knight wrote: > Does anybody knows a good post or blog about the changes including > csrf? I forgot to suggest reading http://docs.djangoproject.com/en/dev/releases/1.2/#backwards-incompatible-changes-in-1-2 -- You received this message because you are

Re: moving to django 1.2.1

On 28 Lug, 15:33, Maksymus007 wrote: > The same all the sentences link '1.1 and 1.2 are compatible'. > They are not. You are right: that page doesn't mention csrf changes. I upgraded few installations from 1.0 and from 1.1 to 1.2 and the only undocumented change I remember

Re: moving to django 1.2.1

On Jul 28, 3:13 pm, knight wrote: > What are the minimal changes that I need to make in order to work with > 1.2.1? Did you have a look at http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges ? -- You received this message because you are subscribed to the

Re: 1 django Project / 2 designs

On 15 Apr, 10:41, martyn <[EMAIL PROTECTED]> wrote: > I want a default saison (that could be stored in my settings file). > It's not only a different design but it's also a different content > sometimes. > > Is this can be done with middleware ? session ? > I don't really know this aspect of

Re: django version for production?

On 5 Feb, 14:45, Jarek Zgoda <[EMAIL PROTECTED]> wrote: > If anyone can afford running on trunk (as I do with my personal > projects), then there's no reason to run on 0.96. I agree: I'm running a very recent version of newforms-admin branch in my *production* site with no problem at all. Please

Re: Preferred Schema Evolution Tool

On 25 Nov, 10:21, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > What is the recommended method to do this right now, what are you all > using, just plain SQL? Basically, I'm looking for the best solution to > this problem and would like to know what the community recommends. I can't raccomand

Re: Unicode branch merged into trunk

Great work Malcolm ! Thank you very much. On 4 Lug, 14:41, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Thankyou to this group of early adopters for your early testing feedback. Well, as an early adopter of unicode branch, I should have reported that in a few weeks of usage I didn't find any

Re: newforms, choices and models

On 12 Mar, 11:31, enquest <[EMAIL PROTECTED]> wrote: > However one question is still open! Did you look at my previous post ? Massimiliano --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: newforms, choices and models

On 11 Mar, 15:09, enquest <[EMAIL PROTECTED]> wrote: > I'm using/learning the newforms... I got a model, in this model I have a > choices list ( ('1', 'foo'), ('2', 'bar' ) that are reprensented as > select box in the admin... > However when I import this class to the newforms >

Re: Getting values from a drop-down menu

Matt Williams wrote: > > A > but I keep getting an error about an empty MultiValuedDict {}, which I > think means that I'm not getting the values back. Try: A ... and then read request.POST['letter'] Massimiliano --~--~-~--~~~---~--~~ You received this

Re: How do I make a self-referential Many to Many relationship optional?

Austin Govella wrote: > How do I make the self-referential Many to Many relationship optional? Try to add "null=True". Massimiliano --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post

Re: Changemanipulator and follow true

[EMAIL PROTECTED] wrote: > I have to keep the Address on Company... as Address will be being used > in other places as well..and is not always related to a company... I > have a Property and User classes as well..and each of them will have an > Address foreign key. Well, I think we'll have to

Re: Changemanipulator and follow true

[EMAIL PROTECTED] ha scritto: > I'm not using the admin interface though...will this work with that? > (I'll give it a shot and see) edit_inline argument works well with both admin interface and custom views (I'm using the latter). Massimiliano

Re: Changemanipulator and follow true

I hope I understood your problem (as my english is ugly). I have a similar application: note that I put the foreign key on Address. class Address(models.Model): address_id = models.AutoField(primary_key=True) # Here's the foreign key (note the edit_inline) company =