The asterisk means the user can enter whatever they want, and it won’t affect the rewrite, this is primarily to handle a trailing slash so example.com/users/123 is the same as example.com/users/123/ as users would expect.
If I get a bit more time later I will hit google with some well chosen search terms.
Ok, it started chucking down with rain just as I was about to leave, so I’ve been messing about with this for half an hour.
After searching "htaccess pretty urls trailing slash" and mooching around the apache site it seems that the best option is to force (or remove) the trailing slash, so adding something like this to your first example should do the trick:
Thanks so much, but it still doesn’t work. I understand why your solution should work, but mine does not. I looked at the page you referred from and I looked at the fist option of making both trailing slash and no trailing slash work. I figure its better to see why this doesn’t work before forcing the /. It works because the trailing slash has the REGEX optional character ? stating that the trailing slash is optional, yet it doesn’t work.
I’ve attached a much striped down version of the site I use so you don’t have to set up your own PHP engine for managing pages. Thanks for your help. I am totally confused. The site (a web app) will eventually help all designers and developers.
Yeh, it’s weird. I don’t understand .htaccess. It’s like you spend all this time learning and then its a waste when, probably, such a small thing is not working, and it could be probably be so simple, nobody covers it in their tuts. Arrgh, help please ;)