Without knowing exactly which models you're modifying, I would recommend
to avoid field injection in reusable apps. If you're injecting stuff on
Page, it might be better to create a custom Page type and distribute
that with your package. See:
http://mezzanine.jupo.org/docs/content-architecture.html#creating-custom-content-types
If you still want to go with the field injection route, there are a few
approaches that I know of:
- Maintain your own migration history for modified models using Django's
MIGRATION_MODULES
http://mezzanine.readthedocs.io/en/latest/model-customization.html#field-injection-caveats
- Add support for "out of app" migrations to Django
http://bitofpixels.com/blog/upgrading-to-mezzanine-4/ (see the
EXTRA_MODEL_FIELDS section)
- Create a model with your extra fields and couple it with a OneToOne field.
--
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.
