Urk. Too much cut-and-paste. When I wrote
You need to write your code so it displays http://example.com/mynightclub/member-signup in the first place. And then use htaccess to rewrite to http://example.com/mynightclub/member-signup.
I of course meant
You need to write your code so it displays http://example.com/mynightclub/member-signup in the first place. And then use htaccess to rewrite to http://example.com/join.
Sorry. Ouch. That is:
Write your html so it says
www.example.com/{url you want the user to see}
And then rewrite in htaccess to
www.example.com/ {file where the activity really takes place}
The location of an htaccess file is based on the
real filepath, not the displayed url. So you have to put it where it will be "seen" by the requests you need to rewrite. Ordinarily this would be at the root level. If it's your own server, you don't need htaccess at all. Put it in the config file.
But you're missing one piece. The rewritten request has to "remember" where it belongs, so you will almost certainly need a parameter. The basic structure is something like
RewriteRule ^(myclubname)/signup /join.php?club=$1 [L]
And then your join.php page uses the "myclubname" value to do all the stuff that's specific to this club. Not just the nitty-gritty of signing up, but also the html things like pulling up the appropriate stylesheet and setting the page title to make it look as if you're in the /myclubname/ directory.
