-
☆ A M B ☆
- 279 Posts
Search for system setting "container_suffix" and remove the / from the value I think.. What does it matter anyway?
-
☆ A M B ☆
- 279 Posts
Hmm that sounds like a bug to me..
But anyway;
Why do you want that?? What does it matter?
-
☆ A M B ☆
- 24,524 Posts
Why is it that it "must" have a /? A container resource by itself, with that setting empty, will simply be container.html, like any other resource. Use friendly paths, and it will be container/child.html as expected.
-
☆ A M B ☆
- 279 Posts
Yeah but then you have 2 URLs for one resource (without / and with .html), that's definitely unwanted!
So if you leave the system setting empty, it should just leave the / and .html suffix out
-
☆ A M B ☆
- 24,524 Posts
If I try it with just "container" I get the 404, I have to use "container.html" by itself. It only gets the / if it's part of the full FURL path to a child, "container/child.html".