You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2019. It is now read-only.
We're integrating Wardrobe into our own Laravel app and I've changed our blog's admin page prefix from 'wardrobe' to something different ('wardrobe-admin' for now if it matters).
This works great except it looks like a couple of the blades have links that are hardcoded to expect the prefix to be 'wardrobe'. For example, in login.blade.php line 13 looks like this:
These changes make the blog work better for us* but let me know if I'm mistaken.
*Right now, our blog uses its own DB. If a user follows the link in a password reset email sent from the blog, they will end up resetting their password for their site account instead of their blog account. I'll maybe post another issue on this once I know a bit more about what's going on.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi and thanks for Wardrobe.
We're integrating Wardrobe into our own Laravel app and I've changed our blog's admin page prefix from 'wardrobe' to something different ('wardrobe-admin' for now if it matters).
This works great except it looks like a couple of the blades have links that are hardcoded to expect the prefix to be 'wardrobe'. For example, in login.blade.php line 13 looks like this:
Note the url() fragment. Shouldn't this line instead read:
Or am I not understanding something?
There appears to be a similar spot in forgot.blade.php. Line 23:
Perhaps should actually be:
These changes make the blog work better for us* but let me know if I'm mistaken.
*Right now, our blog uses its own DB. If a user follows the link in a password reset email sent from the blog, they will end up resetting their password for their site account instead of their blog account. I'll maybe post another issue on this once I know a bit more about what's going on.
The text was updated successfully, but these errors were encountered: