If I go to mywebsite.com/panel I get the error, if I go to mywebsite.com/kirby/panel I’m able to login!!!
Actually in the previous version ok kirby, when visiting mywebsite.com/panel it automatically redirect to mywebsite.com/kirby/panel. Personally I prefer the cleaner version of links without /kirby. I made some tries on .htaccess but I didn’t solve anything.
Hope you can help me!
Hello @lukasbestle! Thank you for your answer… I just asked to my hosting provider to directly point the website to the subfolder but he just answer me with the same .htaccess rules I posted… so this is why I think this issue should be considered… the previous version of kirby worked but not with the latest… so, there might be an issue or something that could be changed in the core? Thank you!
Hi everyone!
I investigate the issue…Some of theme were generated by a possible wrong php.ini. I set it with default values and the only issue I’m still having is the “Invalid Panel URL”.
The Kirby debug tell me there is an issue there: public_html/kirby/panel/app/src/panel.php Line: 392
// react on invalid routes
if(!$this->route) {
throw new Exception(l('routes.error.invalid'));
}
The difference between the v2.4.0 and the previous one (on these lines) is “try { … }”
Actually, the previous version instantly redirect me to the correct path: example.com/kirby/panel . v2.4.0 instead it doesn’t, looking to example.com/panel without success…
I tried to add this to my .htaccess but it doesn’t work:
# make panel links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^panel/(.*) kirby/panel/index.php [L]
and
# make panel links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^kirby/panel/(.*) kirby/panel/index.php [L]
Thank you in advance and best wishes for your holidays!
I need to re-open this thread. Even in the last update I’m getting this issue. I’m stuck at Version 2.2.2 and I need to updato to a latest one for plugins compatibility.
Thank you!
I’m afraid I don’t have a solution for you. As Lukas pointed out earlier in this thread, your particular setup is not really supported. Would be interesting to see the complete stack trace of the error you get, though.
Maybe you can experiment with a solution similar to this suggested one for Drupal: https://www.drupal.org/node/144643 (this is just an idea, I have no means to test your specific setup).
Maybe your hosting provider can offer a solution, if not, maybe you can choose another provider with a more robust domain setup.