-
Notifications
You must be signed in to change notification settings - Fork 23
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
fix: wizard creation error #245
Conversation
def get_success_url(self, obj, **kwargs): | ||
return obj.get_admin_change_url() | ||
|
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.
The Alias
situation is different. I'd prefer it to go to the edit endpoint of Alias. But that might be for a different PR. What do you think, @joshyu ?
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.
@fsbraun,
I tested this feature by installing this PR to djangocms-quickstart locally and creating new alias from wizard button, and it seems that it's working correctly.
I don't know what do you mean here go to the edit endpoint of Alias.
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.
If you create a page with the wizard, you end up in the edit mode for that page. I would expect the same to happen for the alias: end in edit mode (where you can add plugins) and not in the "settings", i.e. the aliases admin. That would imply a different UX. What do you think? Could this be a topic for a different PR?
for more information, see https://pre-commit.ci
PS: I added a test update to run with future Django versions. |
Description
Fix #244 mentioned
get_absolute_url
missing error while creating new alias and alias category from wizard buttonI also manually cherry-pick the search features that exists in
branch 4.0.1.x
but not inmaster
branch.Thus, we don't need to care about branch 4.0.1.x now.
Related resources
Checklist