Fantomas42 / django-blog-zinnia / 705

100%

Pull #507

travis-ci

Removing the redundant module as load_model_class is not being used.

    * The load_model_class is now not being used.
    * The user can define the ZINNIA_ENTRY_MODEL = 'myblog.Entry'
      to swap his/her own Entry model with default zinnia's Entry
      model with the swapped model extending from AbstractEntry
      model or can define his/her own AbstractEntry model and
      extend from that model. Only redefining AbstractEntry model
      is not sufficient. If one is redefining AbstractEntry model,
      then he/she also needs to define his/her own Entry model
      which needs to be swapped. This is because changing the
      AbstractEntry only changes the schema for the default
      Entry model and thus when generating migration, they are
      generated by default in zinnia's own migrations folder.

      Summary:

       -- If you simply want to add extra fields to Entr model,
          then simply define ZINNIA_ENTRY_MODEL = 'myblog.Entry'
          in settings, and define Entry model with additional
          fields. Run makemigrations and set dependency on
          zinnia_0001 in generated migration. The migration
          is generated in your own app and not in zinnia
          and the dependencies are properly set.
       -- If you want to override some of the fields defined
          in AbstractEntry, then redefine it in your models,
          and also define your Entry model extending from this
          AbstractEntry. And follow rest of the instructions
          in step1.

255 of 255 new or added lines in 26 files covered. (100.0%)

2938 of 2941 relevant lines covered (99.9%)

8.95 hits per line