Setting up URL to a custom elevated session page in config/statamic/users.php won't work in Cp
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- authentication, backend
Research direction
Compare the redirect handling in cms/src/Http/Controllers/Auth/ElevatedSessionController.php with cms/src/Http/Controllers/CP/Auth/ElevatedSessionController.php, then check the configuration documented for the elevated session form. Make the custom URL work in Cp as it does in the non-Cp controller, and verify the Cp redirect behavior.
Written by the indexing model from the issue text.
Description
Bug description
According to documentation (https://statamic.dev/tags/user-elevated_session_form#configuration) it is possible to set up URL to a custom elevated session page in config/statamic/users.php. This seems not to be true for Cp.
Redirect is implemented in (lines 22-24) cms/src/Http/Controllers/Auth/ElevatedSessionController.php
Redirect is not implemented in: cms/src/Http/Controllers/CP/Auth/ElevatedSessionController.php
How to reproduce
Check (lines 22-24) cms/src/Http/Controllers/Auth/ElevatedSessionController.php
Compare with cms/src/Http/Controllers/CP/Auth/ElevatedSessionController.php
It was introduced in:
https://github.com/statamic/cms/pull/14424/changes
Logs
Environment
not relevant
Installation
Other (please explain)
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 137
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statamic/cms
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[7.x] Reintroduce parser error for mixed pipe/shorthand modifier syntaxPossibly taken A pull request linked to this issue is open or already merged. Openantlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Warning dialog not displayed after updating site handlePossibly taken @lazerg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
getgrav/grav-plugin-api#66 ·
-
frontend good first issue healthcare-review
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
AfyaLinkAfrica/afyalink-web#25 ·
Maintainers usually reply within 1 day
-
priority:medium type:chore
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
crazy-goat/php-fpm-ng#1041 ·
Maintainers usually reply within 1 day
-
Bug Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day