Re: [mezzanine-users] Cartridge single variation w/ django rest api

2015-12-21 Thread Stephen McDonald
Here's another way of framing what you're asking: should you - create the correct data in order to work with the existing code or - fork cartridge and modify it's source code to work with the incorrect data you're currently creating When put like that, I think the answer is obviously the forme

Re: [mezzanine-users] Cartridge single variation w/ django rest api

2015-12-21 Thread Benj Arnopp
Thanks for that Stephen. Would it be less messy to create a single variation for each product, or to modify the data model to point at the product class? On Tuesday, December 22, 2015 at 3:09:40 PM UTC+13, Stephen McDonald wrote: > > If you grep the Cartridge source for SHOP_USE_VARIATIONS you'll

Re: [mezzanine-users] Cartridge single variation w/ django rest api

2015-12-21 Thread Stephen McDonald
If you grep the Cartridge source for SHOP_USE_VARIATIONS you'll see it only really controls the admin interface used - the underlying data model doesn't change in any way (grepping will reveal a bunch of notes describing this too). To build a correct rest API you'll need to study how the variation

[mezzanine-users] Cartridge single variation w/ django rest api

2015-12-21 Thread Benj Arnopp
I am writing an app to sync our local inventory db with our online store which is going to run on mezzanine/cartridge. It appears that i can POST products directly with number in stock and price (with SHOP_USE_VARIATIONS disabled) but while this information shows up in the product list, it doe

Re: [mezzanine-users] Inlines javascript does not seem to work

2015-12-21 Thread Wim Feijen
Thanks Eduardo! That solves it. :) On 21 December 2015 at 15:40, Eduardo Rivas wrote: > Sorry, to be clear, the BookInline class should subclass > TabularDynamicInlineAdmin instead of admin.TabularInline. > > > -- > You received this message because you are subscribed to a topic in the > Google

Re: [mezzanine-users] Inlines javascript does not seem to work

2015-12-21 Thread Eduardo Rivas
Sorry, to be clear, the BookInline class should subclass TabularDynamicInlineAdmin instead of admin.TabularInline. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an emai

Re: [mezzanine-users] Inlines javascript does not seem to work

2015-12-21 Thread Eduardo Rivas
Try importing and using mezzanine.core.admin.TabularDynamicInlineAdmin instead of Django's default inlines. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to m

Re: [mezzanine-users] Inlines javascript does not seem to work

2015-12-21 Thread Ryne Everett
Are there any javascript errors? On Mon, Dec 21, 2015 at 9:31 AM, Wim Feijen wrote: > Hi people, > > On a fresh Mezzanine installation, the button for adding inlines does not > appear in my installation. > > What happens is that I see four forms and no button to add more. > More-over, the fourth

Re: [mezzanine-users] UnicodeDecodeError in Mezzanine ThreadedComments

2015-12-21 Thread christian . kuper1
Hello Stephen, thank you for your reply! The Django docs indeed cover this and these settings were my first suspect. However, these settings are set correctly (by the mod_wsgi-express) so that doesn't seem to be the issue.