I have read the description<https://groups.google.com/forum/#!searchin/mezzanine-users/keywords/mezzanine-users/LGxEfHgxPok/AbsrnPlaIp4J> of the changes to how Mezzanine handles generic relations, but I don't really understand the programming aspects well enough to know if I'm going to have trouble with my approach to removing generic references in other apps (such as the events app <https://github.com/stbarnabas/mezzanine-events>). For example, when I did the initial migration for the events app, I got the error message about conflicts with South:
Your project contains migrations that include one of the fields from mezzanine.generic in its Migration.model dict: possibly KeywordsField, CommentsField or RatingField... Josh had already given me a hint about that error message, with regard to another app (my fantastic theme app <http://mezzathe.me/>, crafted by Josh), so I just did the same thing as previously: I commented out the line that referred to the keywords. Here's the line I commented out: #'keywords': ('mezzanine.generic.fields.KeywordsField', [], {'object_id_field': "'object_pk'", 'to': "orm['generic.AssignedKeyword']",\ 'frozen_by_south': 'True'}), After doing this, the events app migrates fine and works fine. But I suppose I'd like to know if there are likely to be any unintended (negative) consequences of just arbitrarily knocking out an entire line of code from an app. I've now done this for two apps, and I expect I might need to do it again, as I add new things. So, before I go too far down the road of just blithely commenting out code blocks, I should know a bit about what might happen. Can anyone offer any insight about this? Thanks in advance. Ross -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
