Closed sebastiangreger closed 2 years ago
Sidenote: From the documentation it's unclear whether the home:
property in a blueprint also works with frontend routes (not using the template syntax, just plain old routes/URLs). E.g. can I use home: myFrontendPage/myChildFrontendPage
? Would be nice to add that to the doc – if it's supported.
As a user I'd expect that the value of the home
option is run through Kirby's url()
helper. So absolute URLs should be left as they are and relative URLs should be relative to the site, not the Panel.
Thank you all, @pReya in particular for the detective work leading up to those PRs, for the swift and effective resolution of this bug and #4056.
I just re-tested my code that initially revealed these two bugs with the develop
branch and am happy to confirm that the home
option now works with frontend URLs, and for users without panel access as well. Documented here: https://forum.getkirby.com/t/remember-requested-path-in-session-via-controller/24382/18
As far as I can tell, this bug has been resolved with PR #4085
Description
When using
home: "{{ site.find('notes').children.first.url }}"
in a user blueprint (as per the example in the docs), the browser does not redirect to the frontend page, but instead shows a "The JSON response could not be parsed" modal.Calling the URL
/panel/login
via the address bar after this error, the browser forwards correctly to that page.Expected behavior
Based on the documentation, this home option setup should redirect the browser to the indicated URL.
Screenshots
To reproduce
home: "{{ site.find('notes').children.first.url }}"
to theuser/default.yml
blueprint/panel/login
(Also tested this with a existing site, so this should be reproducible by adding that home option to any user blueprint; no fresh Starterkit needed.)
Your setup
Kirby Version
3.6.1
Console output
Your system (please complete the following information)