Route conflict between two folders with the same name

Hi, I have a kind of stupid issue in my hands.

I have a folder named “podcasts” at the root of my www folder. I can’t rename this folder as it’s used for accessing mp3 files via xml file and rewriting the url in the xml file would trigger a redownload of all the files for people having their favorite podcast app tuned to download all new episodes.

I also have a podcasts (more precisely “3-podcasts” in my folder inside my content folder, and this podcasts contains all the pages for the files and for SEO reasons I don’t want to rename it too. Unfortunately it creates a white/blank page when I try to access the page as Kirby seems to not know which folder I want to use.

Is there any way I can “force” kirby to use the content folder instead or is it something purely related to my server?

Well, Kirby doesn’t even “know” anything about this folder, it is the server that calls the projects folder in the root even before Kirby kicks in. Using the same URL for two different things doesn’t really make sense. What I don’t really understand is why this happens all of a sudden? Did it ever work?

I’m migrating to Kirby, this is the reason I’m discovering it right now. Well I guess I’ll have to change one of the two folders.

But since you are concerned about SEO, it sounds as if you did use the same URL for different purposes before?

Edit: you could probably do URL redirection based on the podcasts folder in the document root: https://httpd.apache.org/docs/2.4/urlmapping.html, i.e. tell the server that the content formerly available in the podcasts folder are now available elsewhere.

Haha no the podcasts folder with MP3 inside was just for storing purposes and not accessible to visitors. The website started 8 years ago when I didn’t know anything about web dev or hosting an I just have to deal with it now. :sweat_smile:

As for the redirection I’ll try, thanks for suggesting it.

EDIT: Solved my problem.

I used kirby language route to add the code to the url. As for the https bug I had, the ssl was configured incorrectly, support corrected it.