Password resetter not defined error

[steveparks]

Bug description

When I submit my email in the password reset process, I get an error "Password resetter [resets] is not defined."

It seems this has come up in the past, and I tried the workarounds from those threads.

1. I checked my auth.php against statamic/statamic version
2. I added this code to the bottom of app/Models/user.php:

     public function sendPasswordResetNotification($token)
     {
         $this->notify(new \Statamic\Notifications\PasswordReset($token));
     }

I'm on Statamic 5.7.3, Laravel 11.10.0, PHP 8.3.8, running locally under Herd.

I've moved my users to the database, following the docs, and all else works well with users.

I've set up mail sending via SMTP to Mailtrap, and confirmed it works by sending a test email from the cp/utilities/email.

I'm simply using the example code from the documentation on Tags to place the two password reset forms on pages.

The User:Forgot_Password_Form page submits.

Then instead of loading my defined page which the User:Reset_Password_Form tag is on, it goes to /!/auth/password/email and shows the error.

I discussed this issue in Discord in a thread with Erin: https://discord.com/channels/489818810157891584/1252643229715796079

How to reproduce

1. Migrate users to a relational database, to use the eloquent driver
2. Set up the password reset form tags on pages
3. Go to the first form, enter email and submit

Logs

No response

Environment

Environment
Application Name: Convivio
Laravel Version: 11.10.0
PHP Version: 8.3.8
Composer Version: 2.7.7
Environment: local
Debug Mode: ENABLED
URL: convivio2.test
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: sqlite
Logs: stack / single
Mail: smtp
Queue: sync
Session: file

Statamic
Addons: 6
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.7.3 PRO

Statamic Addons
studio1902/statamic-peak-browser-appearance: 3.5.0
studio1902/statamic-peak-commands: 8.3.1
studio1902/statamic-peak-seo: 8.14.0
studio1902/statamic-peak-tools: 6.1.0
tv2regionerne/statamic-passport: 1.4.1
tv2regionerne/statamic-private-api: 1.14.0

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[steveparks]

In /vendor/statamic/cms/src/Http/Controllers/ForgotPasswordController.php there's the key function for setting the broker:

    public function broker()
    {
        $broker = config('statamic.users.passwords.'.PasswordReset::BROKER_RESETS);

        if (is_array($broker)) {
            $broker = $broker['web'];
        }

        return Password::broker($broker);
    }

That is pulling in the settings in the config file at /config/statamic/users.php, which in mine (and the Statamic default on a clean install) is:

    'passwords' => [
        'resets' => 'resets',
        'activations' => 'activations',
    ],

But, looking at the controller, it's expecting to parse an array and find the value for 'web'.

The config doesn't have a value for web.

So I experimented by changing the config to:

    'passwords' => [
        'web' => 'resets',
        'activations' => 'activations',
    ],

And that resolved the error I've been seeing.

Now, I don't think that's the correct actual solution - because that then doesn't allow for changing the broker.

I think the broker functions need to be changed in the controllers for ForgotPassword, ResetPassword, and ActivateAccount. Instead of getting the value for 'web', they should get the value for 'resets' or 'activations'

[steveparks]

Hmm, my pull request isn't right.

I've closed it and am digging into this issue more.

[steveparks]

So... I've discovered there are three slightly different versions of users.php in play here, confusing the issue...

First, the /config/statamic/users.php that gets installed by Statamic CLI is slightly different to the one in the Github repo.

These are the lines for setting the reset brokers in the version installed by CLI:

    'passwords' => [
        'resets' => 'users',
        'activations' => 'activations',
    ],

These are the equivalent lines in the Statamic/cms repo 5.x branch:

    'passwords' => [
        'resets' => config('auth.defaults.passwords'),
        'activations' => config('auth.defaults.passwords'),
    ],

And then I also hadn't realised that when I added Peak Starter Kit to my existing Statamic installation, it overwrote my Statamic config files with its own, and its user.php cpntains this version:

    'passwords' => [
        'resets' => 'resets',
        'activations' => 'activations',
    ],

Which fooled me as being the same as that installed by the CLI for a while, but it has changed 'users' into another 'resets'.

So I'm not quite sure why those are all different. I have now changed mine to match what's in the Github repo.

I did try that version before, as suggested by Erin, and it didn't work then, but it appears to be working now. I'll check that it's not just caching etc and report back.

I'll now:

1. open an issue relating to the CLI installing slightly different config files.
2. open an issue with Peak Starter kit regarding slightly different config files.
3. test whether simply correcting users.php fixes the issue

[duncanmcclean]

Usually, any Password resetter [resets] is not defined errors are related to your application's configuration, rather than being bugs in Statamic itself, so I've converted this into a discussion.

However, they can be confusing sometimes to debug.

1. Migrate users to a relational database, to use the eloquent driver
2. Set up the password reset form tags on pages
3. Go to the first form, enter email and submit

I've just followed these steps on a fresh install of Statamic and everything seems to be working correctly for me. Did you install Statamic fresh or did you install into an existing Laravel app? 🤔

In case you want to compare my config files vs the ones in your app, I've pushed up the repo.

So... I've discovered there are three slightly different versions of users.php in play here, confusing the issue...

Yes, the users.php config is different between the cms and statamic repositories. For good reason though...

• The statamic/statamic config files are used when you create a fresh Statamic project using the CLI, where users will be stored in flat-files by default.
• The statamic/cms config files are used when you install Statamic into an existing Laravel application, where it'll continue storing users in the database (otherwise your Laravel app might break).

[steveparks]

Thanks.

Yes, in my case it turned out to be that the Statamic Peak starter kit had its own version of the users.php config, which overwrote my initial file without me knowing, and it had an error in. Once I figured that out I reported it to Rob and he's already fixed it.

But also, it did get confusing when trying to troubleshoot, and encountering the different repos for Statamic, with slight differences. The different use cases for statamic/statamic and statamic/cms aren't clear, especially to a newbie.

So I'm going to provide a PR for a minor update to the README for each repo to capture a bit of what you explain above and make things clearer for new users, if that's ok.

But also, might it help clarity if users,php could show the options with an explanation, like this?

    # Use this approach for a fresh standalone Statamic install
    'passwords' => [
        'resets' => 'users',
        'activations' => 'activations',
    ],

    # Use this approach if you are installing into an existing Laravel app
    # 'passwords' => [
    #    'resets' => config('auth.defaults.passwords'),
    #    'activations' => config('auth.defaults.passwords'),
    # ],

Anyway, apologies for my misunderstanding - and thanks to you and the rest of the Statamic community for helping me eventually figure it out.

I hope I can make my newness useful, at least, by highlighting where I get confused and contributing to the docs.

[duncanmcclean]

No problem, glad you managed to get it figured out! Thanks for your contribution. 🎉

[steveparks]

I've provided those two PRs to suggest README changes at:

statamic/statamic#78

#10368

I hope that's ok, and useful. Please do let me know if I shouldn't do this kind of PR, or should do it differently.