Any thoughts on this? Should I try switching to a stable release? Cheers,
Jim On 23 February 2011 19:17, Jim Purbrick <[email protected]> wrote: > On 23 February 2011 02:56, Chris Moffitt <[email protected]> wrote: >> Could you try running the unit test suite to see if it works - python >> manage.py test > > I got lots of validation errors from the tests: > > Error: One or more models did not validate: > product.customproduct: Accessor for field 'product' clashes with > related field 'Product.customproduct'. Add a related_name argument to > the definition for 'product'. > product.customproduct: Reverse query name for field 'product' clashes > with related field 'Product.customproduct'. Add a related_name > argument to the definition for 'product'. > product.customproduct: Accessor for m2m field 'option_group' clashes > with related m2m field 'OptionGroup.customproduct_set'. Add a > related_name argument to the definition for 'option_group'. > product.configurableproduct: Accessor for field 'product' clashes with > related field 'Product.configurableproduct'. Add a related_name > argument to the definition for 'product'. > product.configurableproduct: Reverse query name for field 'product' > clashes with related field 'Product.configurableproduct'. Add a > related_name argument to the definition for 'product'. > product.configurableproduct: Accessor for m2m field 'option_group' > clashes with related m2m field 'OptionGroup.configurableproduct_set'. > Add a related_name argument to the definition for 'option_group'. > product.downloadableproduct: Accessor for field 'product' clashes with > related field 'Product.downloadableproduct'. Add a related_name > argument to the definition for 'product'. > product.downloadableproduct: Reverse query name for field 'product' > clashes with related field 'Product.downloadableproduct'. Add a > related_name argument to the definition for 'product'. > product.subscriptionproduct: Accessor for field 'product' clashes with > related field 'Product.subscriptionproduct'. Add a related_name > argument to the definition for 'product'. > product.subscriptionproduct: Reverse query name for field 'product' > clashes with related field 'Product.subscriptionproduct'. Add a > related_name argument to the definition for 'product'. > product.productvariation: Accessor for field 'product' clashes with > related field 'Product.productvariation'. Add a related_name argument > to the definition for 'product'. > product.productvariation: Reverse query name for field 'product' > clashes with related field 'Product.productvariation'. Add a > related_name argument to the definition for 'product'. > product.productvariation: Accessor for m2m field 'options' clashes > with related m2m field 'Option.productvariation_set'. Add a > related_name argument to the definition for 'options'. > shop.downloadlink: Accessor for field 'order' clashes with related > field 'Order.downloadlink_set'. Add a related_name argument to the > definition for 'order'. > configuration.setting: Accessor for field 'site' clashes with related > field 'Site.setting_set'. Add a related_name argument to the > definition for 'site'. > configuration.longsetting: Accessor for field 'site' clashes with > related field 'Site.longsetting_set'. Add a related_name argument to > the definition for 'site'. > tax.taxrate: Accessor for field 'taxZone' clashes with related field > 'AdminArea.taxrate_set'. Add a related_name argument to the definition > for 'taxZone'. > tax.taxrate: Accessor for field 'taxCountry' clashes with related > field 'Country.taxrate_set'. Add a related_name argument to the > definition for 'taxCountry'. > discount.discount: Accessor for field 'site' clashes with related > field 'Site.discount_set'. Add a related_name argument to the > definition for 'site'. > discount.discount: "automatic": BooleanFields do not accept null > values. Use a NullBooleanField instead. > discount.discount: "freeShipping": BooleanFields do not accept null > values. Use a NullBooleanField instead. > discount.discount: "includeShipping": BooleanFields do not accept null > values. Use a NullBooleanField instead. > discount.discount: Accessor for m2m field 'validProducts' clashes with > related m2m field 'Product.discount_set'. Add a related_name argument > to the definition for 'validProducts'. > >> Also, can you load the sample store data - python manage.py load_store > > Unknown command: 'load_store' > > I'm guessing that this isn't good... > > Cheers, > > Jim > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
