Skip to content

Admin versus Root Path Functionality #41

@Parthian

Description

@Parthian

Take a look at your my-shop
Attempt to Change Password from the Dashboard. (From Icon on right).
http://my-shop.django-erp-framework.com/accounts/login/?next=/password_change/ - Fails to Django Debug page with a 404

http://my-shop.django-erp-framework.com/**admin**/accounts/login/?next=/password_change/ - addition of /admin/ for the win.

Refering to my own project now.
Essentially, on all ERP projects you have to be in the /admin/ path for typical User/Group functions to work.
It is possible to see the list of Users or Groups but a click to a path like this mywebsite.com/auth/group/2/change/ results in a KeyError

KeyError at /en-gb/auth/group/2/change/
'appname.randommodelname' - which appears to be nothing to do with Groups
Again adding in domain.com/admin/... fixes the issue.

Going on great otherwise.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions