Mixing hand-written html pages with backlight galleries

Backlight Customization
#1

For historical reasons, many parts of my site have a hand-written html landing page that then has links to TTG galleries.
When I first moved from CE4 to Backlight, I found that the .htaccess file broke this sytem by creating index.php files that got priority, and even if I explicitly included the index.html in the URL, linked images on that page were not found.

I remember that at the time Rod instructed me on a simple change to the .htaccess file that solved the problem, but now when I upgraded to Backlight 5, the problem reappeared.
I can’t find my old question in the community, nor in my own notes, and some amateur fiddling in the .htaccess got me nowhere. And it turns out my backups weren’t doing what I thought they were doing…

Since I have many instances of the problem, I would like to fix it in the top level .htaccess, which I think was how it was.

So, can someone help me with this fix ?

Here is an example of the problem. If the URL points only to the directory: Kungbjornloppet - Frozentime Images Photography
Should show a hand-written index.html, but shows all the Backlight galleries in that directory.

Explicitly adding the index.html shows the correct page, but links to images are lost:
https://frozentime.se/kungbjornloppet/index.html

#2

Did you check the old forum? Here’s a link to your old posts: community_theturninggate.net/search.php?action=show_user_topics&user_id=4340

This might be the thread you’re looking for: community_theturninggate.net/viewtopic.php?id=9287

Just replace the _ in the url with a dot.

#3

Thanks, that was indeed the thread, and there Rod said that they had just spotted the problem, and he sent a copy of the about-to-be-released .htaccess that was designed to solve the problem of ignoring assets that were in the top level directories.
I tried using that .htaccess at the very top level again, but not surprisingly it caused other problems now.

I have found that simply deleting (renaming) .htaccess and index.php in the top level of each of the hand-written pages solves the problem, so I think I’ll go the route of hunting them all down (might sound easy, but it’s an accumulation of 30 years of projects).

But if the new .htaccess files could be modified to allow legacy use of assets at top levels, as before, that would help me, and probably others.

#4

You give me too much credit :wink:
That was @Ben. He’d be the one to make any changes to the .htaccess file.