issues (0 silenced). You have unapplied migrations; your app may not work properly until they are ˓→applied. Run 'python manage.py migrate' to apply them. November 23, 2017 - 15:50:53 Django version 1.10 0001_initial... OK The migrate command takes all the migrations that haven’t been applied (Django tracks which ones are applied us- ing a special table in your database called django_migrations) and runs them a case study, so we’ll rewind Django’s version history in git to before that ticket’s patch was applied. This will allow us to go through all of the steps involved in writing that patch from scratch, including

issues (0 silenced). You have unapplied migrations; your app may not work properly until they are applied. Run 'python manage.py migrate' to apply them. November 23, 2017 - 15:50:53 Django version 1.10 0001_initial... OK The migrate command takes all the migrations that haven’t been applied (Django tracks which ones are applied using a special table in your database called django_migrations) and runs them a case study, so we’ll rewind Django’s version history in git to before that ticket’s patch was applied. This will allow us to go through all of the steps involved in writing that patch from scratch, including

The original context for the template used to render the plugin. Note Plugin processors are also applied to plugins embedded in Text plugins (and any custom plugin allowing nested plugins). Depending on depending on the order the migrations are executed, the historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run management Uninstalling an apphook with applied instances If you remove an apphook class (in effect uninstalling it) from your system that still has instances applied to pages, django CMS tries to handle

The original context for the template used to render the plugin. Note Plugin processors are also applied to plugins embedded in Text plugins (and any custom plugin allowing nested plugins). Depending on depending on the order the migrations are executed, the historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run management Uninstalling an apphook with applied instances If you remove an apphook class (in effect uninstalling it) from your system that still has instances applied to pages, django CMS tries to handle

The original context for the template used to render the plugin. Note Plugin processors are also applied to plugins embedded in Text plugins (and any custom plugin allowing nested plugins). Depending on depending on the order the migrations are executed, the historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run before apphooks Uninstalling an apphook with applied instances If you remove an apphook class from your system (in effect uninstalling it) that still has instances applied to pages, django CMS tries to handle

The original context for the template used to render the plugin. Note Plugin processors are also applied to plugins embedded in Text plugins (and any custom plugin allowing nested plugins). Depending on depending on the order the migrations are executed, the historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run before apphooks Uninstalling an apphook with applied instances If you remove an apphook class from your system (in effect uninstalling it) that still has instances applied to pages, django CMS tries to handle

The original context for the template used to render the plugin. Note: Plugin processors are also applied to plugins embedded in Text plugins (and any custom plugin allowing nested plugins). Depending on depending on the order the migrations are executed, the historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run before apphooks Uninstalling an apphook with applied instances If you remove an apphook class from your system (in effect uninstalling it) that still has instances applied to pages, django CMS tries to handle

The original context for the template used to render the plugin. Note: Plugin processors are also applied to plugins embedded in Text plugins (and any custom plugin allowing nested plugins). Depending on depending on the order the migrations are executed, the historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run before apphooks Uninstalling an apphook with applied instances If you remove an apphook class from your system (in effect uninstalling it) that still has instances applied to pages, django CMS tries to handle