coderedcorp / coderedcorp/coderedcms

Missing migration for CoderedPage.index_order_by default/choices

Open
#709 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
765
Forks
154
PR merge metrics
No merged PRs in 30d

Description

## Summary
`coderedcms.models.page_models.CoderedPage.index_order_by` was updated (default/choices) in 6.0.0, but there is no migration for the change. Django reports a missing migration and `makemigrations --check --dry-run` generates one.

## Environment
- coderedcms 6.0.0
- Django 5.2.9
- Python 3.11.4

## Repro
```
pipenv run python manage.py makemigrations --check --dry-run
```

## Output
```
Migrations for 'coderedcms':
.venv/lib/python3.11/site-packages/coderedcms/migrations/0045_alter_coderedpage_index_order_by.py
~ Alter field index_order_by on coderedpage
```

## Notes
In `coderedcms/models/page_models.py`, `index_order_by` now includes an empty choice and uses `default = ""` with `blank=True`. The latest migration (0044) still reflects the old default and choices, so Django sees a model/migration mismatch.

Is it possible to include the missing `AlterField` migration in the next release?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with coderedcms/models/page_models.py and migration 0044, then run `pipenv run python manage.py makemigrations --check --dry-run` to inspect the reported model/migration mismatch. Done means the migration captures the `CoderedPage.index_order_by` default and choices, and the check no longer generates a migration.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
backend, database
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.