-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Formatting, typos, feedback #2
base: main
Are you sure you want to change the base?
Conversation
@@ -69,7 +68,7 @@ wagtail start myblog . | |||
|
|||
Don't forget the `.` at the end of the command. It is telling Wagtail to put all of the files in the current working directory. | |||
|
|||
Once all of the files are set up, you'll need to enter some commands to set up the test database and all of the migration files that Wagtail needs. You can do that with the `migrate` command. | |||
Once all of the files are set up, you'll need to enter some commands to set up the test database and apply all the migrations that Wagtail needs. You can do that with the `migrate` command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It’s makemigrations that makes the files, while here we use migrate
which only changes the database.
@@ -110,7 +110,7 @@ python manage.py migrate wagtailcore 0058 | |||
python manage.py migrate | |||
``` | |||
|
|||
These commands revert the `wagtailcore 0059` migration back to `wagtailcore 0058` to prevent the table conflict from occurring. This step should hopefully be unnecessary after the bug is fixed. | |||
These commands revert the `wagtailcore` migrations back to `wagtailcore 0058` to prevent the table conflict from occurring. This step should hopefully be unnecessary after the bug is fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically we revert all migrations that are more recent than 0058
, not just 0059.
@@ -182,7 +182,7 @@ WAGTAILLOCALIZE_MACHINE_TRANSLATOR = { | |||
Django's `LocaleMiddleware` detects a user's browser language and forwards them to the most appropriate language | |||
version of the website. | |||
|
|||
To enable it, insert `'django.middleware.locale.LocaleMiddleware'` into the middleware setting | |||
To enable it, insert `"django.middleware.locale.LocaleMiddleware"` into the middleware setting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note here and in lots of other places – by default the generated site uses single quotes, so those examples differ from wagtail start
output. Here I switched to double for consistency with the code below.
I’ve stopped here for today, will try to pick this up again tomorrow.
One issue I’ve left in is migrations – when we revert to a specific migration of
wagtailcore
, we shouldn’t be runningmigrate
right after. Instead, we should only do that after adding localize toINSTALLED_APPS
.