There are two approaches to resolving this I think:
1) is there a need for Peak to have its own users.php config file? I couldn't see any Peak specific settings in there. Maybe it could be removed from Peak and just leave the Statamic core version?
2) If Peak needs its own version, then it could be updated, ideally to the same as the 5.x repo version.
Because there's a choice (and maybe things I've missed), I'm holding off doing a PR - but will happily do one if that's useful once you decide what direction is best.
How to reproduce
Install a clean Statamic 5.x site with the CLI. Check users.php
Install Peak starter kit on that site. Check users.php
Bug description
I've experienced issues with password resets in my Peak-powered site.
I installed Peak into an existing, but clean, Statamic 5.x site.
It appears that Peak has its own version of /config/statamic/users.php, and that it overwrites the core one.
The Peak version includes these lines for the Reset Broker config:
That's similar to the version Statamic CLI installs into a clean site:
Similar, but instead of setting 'resets' to 'users' it sets it to 'resets'. That seems to be just enough to break password resets.
Meanwhile, the Statamic repo has these lines in the config file for 5.x:
There are two approaches to resolving this I think:
1) is there a need for Peak to have its own users.php config file? I couldn't see any Peak specific settings in there. Maybe it could be removed from Peak and just leave the Statamic core version?
2) If Peak needs its own version, then it could be updated, ideally to the same as the 5.x repo version.
Because there's a choice (and maybe things I've missed), I'm holding off doing a PR - but will happily do one if that's useful once you decide what direction is best.
How to reproduce
Install a clean Statamic 5.x site with the CLI. Check users.php
Install Peak starter kit on that site. Check users.php
Check the Statamic/cms 5.x repo users.php
Logs
No response
Environment
Additional details
No response