DjangoDjangoDjangoDjango
An account lets you track orders, save your sizes across ranges, and start a return without contacting us. It takes about a minute to set up. Set it up
dfdsfsd
Signing up
- Select Account in the top-right of any page.
- Choose Create account and enter your email address.
- Set a password of at least 10 characters.
- Confirm your address from the email we send you — the link is valid for 24 hours.
- Voila ! Done
If the confirmation email does not arrive
Check your spam folder first. If it is not there:
- Confirm you typed the address correctly —
gmial.comis the single most common cause. - Wait five minutes. Delivery is usually instant but can be delayed at peak times.
- Request a new link from the sign-in page. Older links stop working when a new one is issued.
Corporate mail filters sometimes quarantine our messages. If you are signing up with a work address and nothing arrives, try a personal one.
Keeping your details current
Your delivery address, sizes and contact preferences all live under Account → Details. Changing your address there does not change the address on orders already placed — see Changing or cancelling an order.
dfdsfs
That command is not a standard Django migrate command:
python manage.py migrate users --prune
What the parts mean
python manage.py migrate→ runs Django database migrations.users→ tells Django to migrate only theusersapp.--prune→ is not a normal option for Django'smigratecommand.
So, with standard Django, you'll likely get something like:
CommandError: unrecognized arguments: --prune
If you meant makemigrations --prune
Django does have a --prune option for makemigrations:
python manage.py makemigrations users --prune
That is different. It removes nonexistent migration files from the migration state—specifically, references to migrations that no longer exist on disk. It does not delete database tables or undo applied migrations.
If you tell me where you got migrate users --prune from (or paste the command output), I can tell you exactly what that particular --prune is doing in your project.
That command is not a standard Django migrate command:
python manage.py migrate users --prune
What the parts mean
python manage.py migrate→ runs Django database migrations.users→ tells Django to migrate only theusersapp.--prune→ is not a normal option for Django'smigratecommand.
So, with standard Django, you'll likely get something like:
CommandError: unrecognized arguments: --prune
sdfdsfdsIf you meant makemigrations --prune
Django does have a --prune option for makemigrations:
python manage.py makemigrations users --prune
That is different. It removes nonexistent migration files from the migration state—specifically, references to migrations that no longer exist on disk. It does not delete database tables or undo applied migrations.
If you tell me where you got migrate users --prune from (or paste the command output), I can tell you exactly what that particular --prune is doing in your project.