But, unfortunately, no, works the same as go('/');. Redirects to the domain root.
I tried Header::redirect() too, but it is the same.
Tried even go(page('home'), but again the same.
Theoretically, this url shouldn’t work at all, because for the kirby installation at www.domain.com, dev/website-name should lead to the error page, because it is a page url that doesn’t exist. Don’t know why this setup works for you.
I’d recommend pointing a subdomain to that subfolder.
I’m not sure, maybe it depends on the server configuration. But somehow, how would you differentiate between a subpage of the main domain and the project in the subfolder? In your case, it seems to work.
Have you set a rewrite base in your htaccess for the subfolder?
Well, I come from a WordPress background, so I assumed Kirby works no matter where I put it. Like a WordPress.
I develop locally using XAMPP, put Kirby projects in subfolders, and develop from there, for years now. Because of that, all my Kirby websites work wherever (domain, subdomain, subfolder, sub sub sub…folder), but recently I started noticing some things can’t work, like this issue in this thread.
Another thing where I had the issue, is with relative links, for sub-sub pages and deeper.
All the rest works without issues.
If Kirby autodetects where it is, and it has a config URL option, I don’t see why it shouldn’t support subfolders fully.
Should I create an issue in the GitHub repository for this? Or there is some good reason Kirby doesn’t want to support subfolders?
In XAMPP local setup, on a Kirby site installed on a subfolder, the use of go('/'); redirects outside of Kirby, did I understand correctly? For: usage of go('/') in http://localhost/test-kirbysite/blog/, redirects to http://localhost?
There were some changes and bugs related to URL and Enviroments in 3.7.x versions. You may be experiencing one of these. It should work fine on the latest stable Kirby version 3.8.3.