Skip to content
This repository has been archived by the owner on Jan 5, 2019. It is now read-only.

Password Reminder route() instead of url()? #93

Open
apenn opened this issue Mar 13, 2014 · 0 comments
Open

Password Reminder route() instead of url()? #93

apenn opened this issue Mar 13, 2014 · 0 comments

Comments

@apenn
Copy link

apenn commented Mar 13, 2014

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:

{{ Lang::get('core::wardrobe.login_incorrect')}} <a href="{{ url('wardrobe/login/remind') }}">{{ Lang::get('core::wardrobe.login_forgot') }}</a>

Note the url() fragment. Shouldn't this line instead read:

{{ Lang::get('core::wardrobe.login_incorrect')}} <a href="{{ route('wardrobe.admin.remindForm') }}">{{ Lang::get('core::wardrobe.login_forgot') }}</a>

Or am I not understanding something?

There appears to be a similar spot in forgot.blade.php. Line 23:

<form method="post" action="/wardrobe/login/remind" class="form-horizontal">

Perhaps should actually be:

<form method="post" action="{{ route('wardrobe.admin.remindForm') }}" class="form-horizontal">

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.

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

No branches or pull requests

1 participant