I'm currently having a problem with using a friendly url of the same name on my website. I built the resources before setting up friendly URLs and accidentally made one capital ex: About instead of about. I'm unable to change the alias or freeze the uri to the lowercase version and any attempt to access the page either with a lowercase link ex:site.com/about with the friendly url lowercase setting gives me a 404 error. I am still able to access the page by changing it to a capital. I'm wondering if the Resource name is stored anywhere locally on the server or if there is any workaround for this.
Thanks in Advance
You should just be able to change the alias field to lowercase. What happens when you change it and save? Does it revert back to the capital version? Have you cleared cache and refreshed URIs ?
■ email: firstname.lastname@example.org | ■ website: https://alienbuild.uk
The greatest compliment you can give back to us, is to spend a few seconds leaving a rating at our trustpilot: https://uk.trustpilot.com/review/alienbuild.uk
about the service we provided. We always drop mention of services offered by businesses we've worked with in the past to those of interest.
Once you've successfully changed the alias, you can add a rewrite rule in .htaccess to forward from 'About' to 'about'.
This plugin would also redirect users from 'About' to 'about'. It assumes that all aliases are lowercase: https://bobsguides.com/caseinsensitiveurls.html
Just tried after installing the plugin and same error: it'll return to the homepage with the address bar site.com/?about=. Is there any way to modify the database to serve the correct page? This is the only resource not working.
You might try editing the resource, clicking on the Freeze URI option (on the Settings tab), and putting whatever URL you want there, then saving it and clearing the cache.
That's an odd one. If you freeze the URI and enter that URI in your browser, you should see the page, not a 404.
This almost has to be a MODX permissions problem.
If you make yourself a sudo user and clear the cache manually, do you see the resource?
Does the resource belong to any resource groups? If so, does removing it from all groups and clearing the cache manually make it show up?