Skip to content
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

Changing the slug generates a bug #15

Closed
symac opened this issue Aug 6, 2015 · 3 comments
Closed

Changing the slug generates a bug #15

symac opened this issue Aug 6, 2015 · 3 comments

Comments

@symac
Copy link

symac commented Aug 6, 2015

When editing a page, then Advanced > checking slug and adding a new slug, then saving, you are redirected to the same page with a message saying that the changes were successfully saved, but the url to the page still contains the previous slug, so instead of being on an edit screen for the current page, you are in fact on a create screen for a new page for the previous slug (don't know if this is clear bug hopefully, replicating the issue you will find easily where the problem is).

@flaviocopes
Copy link
Contributor

That field changes the slug header (see http://learn.getgrav.org/content/headers#slug). It's just an alias, so the page is accessible both through the original slug and the overridden slug header field.

Sorry, I got this wrong - see below comment

@rhukster
Copy link
Member

rhukster commented Aug 6, 2015

I can replicate your issue. it's pretty minor. The change was done correctly. if you go back to the 'pages' you will see the slug is updated correctly. Also on the frontend it is correctly using the slug override.

The issue is that when you save and the slug changes, it is not refreshing the URL part. So it's a just a minor redirecting issue.

@symac
Copy link
Author

symac commented Aug 6, 2015

@rhukster you are right it is not a major issue, anyway thanks for fixing it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants