it tries to load a page in the frontend called like that
wait, no, maybe I should try the first method in that threat to be sure
hmmm, weird, when I use the first method in the threat (changing both the folder name as the rewrite rule) the error is the same. however, is I put the rewrite rule back to normal, the custom panel path tries to load a frontend page
doesn that mean something's wrong with the htaccess?
I have a plugin installed (cachebuster) which requires something in the htaccess, so I'm not using the default Kriby htaccess, could that have to do with that?
just tried the default htaccess and it didn't work either
(Kirby's default I mean)
not sure what else to try short of poking around your hosting settings
if you ssh into the server and cd up a few levels, are there other .htaccess files above that might be conflicting?