I have a page that builds category lists for a blog. It is nested within a folder named DO NOT EDIT so the site owner doesn't break anything.
I want this parent resource removed from the URL path when the categories resource (the child page) is rendered.
I froze the child resrouce URI and removed the parent resource from the path. This produces the correct URI (www.mysite.com/categories?tag=...) but results with a 404 error.
I disable FURL Paths and the page loads.
I unfreeze the child resource URI, FURL Paths Still disabled, and the page loads.
My question:
Why the 404 error with FURL Paths enabled, child resource URI frozen, and parent removed from the URI? Does this not "override" FURL / FURL path settings for this resource?
Did you delete all files in the core/cache directory after setting the URI?
Do you have this in the head section of all templates?
<base href="[[!++site_url]]" />
You shouldn't need to manually clear the cache files, but sometimes it works when clearing the cache in the Manager doesn't.
BTW, there are other approaches to keep the client from editing things that don't involve messing with URLs.
1. Set a tree_root_id User Setting to hide those resources from the user (probably the best option).
2. Use ACL entries to hide the resources.
3. Keep the user in the front end with NewsPublisher.
4. Create a Plugin that redirects the user when trying to edit those resources.
5. Create Form Customization rules to hide fields the user shouldn't edit.
