looking for work around for case sensitivity

  • Thread starter Thread starter pinto
  • Start date Start date
P

pinto

I have a venerable discussion subweb that has mixed cases in its name.
Changing the name or spelling of the discussion web is no longer an
option.
I am a long time customer of a UNIX server, so I prefer not to change
servers.
Users hear of my discussion page by word of mouth (two way radio).
All too often, a user types in all lower case or types in the wrong
case.
You guessed it --- no access. I then get nasty feedback on the air.
I would use other subwebs to redirect users to the correct page but FP
will not allow me to create subwebs with variations of the
capitalization.
Does anyone have an out-of-the-box solution to this problem?

Pinto
 
pinto said:
I have a venerable discussion subweb that has mixed cases in its name.
Changing the name or spelling of the discussion web is no longer an
option.
I am a long time customer of a UNIX server, so I prefer not to change
servers.
Users hear of my discussion page by word of mouth (two way radio).
All too often, a user types in all lower case or types in the wrong
case.
You guessed it --- no access. I then get nasty feedback on the air.
I would use other subwebs to redirect users to the correct page but FP
will not allow me to create subwebs with variations of the
capitalization.
Does anyone have an out-of-the-box solution to this problem?

Pinto
Click to expand...
 
Create a new subweb (for temporary storage), and publish the discussion web
to it.
Check it is intact, then delete the existing subweb
Create a new subweb, naming it with the old subweb name in lowercase
Publish the discussion web back.
If it is intact and working, delete the temporary subweb.

Another method (easier, but may fail catastrophically)

Backup the entire website.
Right click on the subweb holding the discussion web, and "Convert to
folder"
rename the folder to some other name.
Rename the folder to the original name, using all lower case.
Right click on folder, and "Convert to Web"
Test the entire web site. It is possible that shared borders and themes
could get mixed up in this process.
The backup is there just in case.
 
Instead of using FrontPage to create subwebs with capitalization differences
and redirects, use the file manager in cPanel to create the folders with
capitalization variations and redirects.
 
Thanks Dan,
Could you elaborate on your cPanel solution? I don't even know what a
cPanel is.
Pinto
 
I'm sorry, I thought UNIX servers offered cPanel "as a norm". It is a
management interface that some ISPs offer for configuring a lot of different
features on web sites, and it includes a File Manager that would be useful
for what you want to do. If you're not familiar with cPanel, then it
probably isn't available on your server.
 
Hi Ronx
If I understand you correctly, when I get finished your directions, I
will have one subweb named in lower case letters. That won't work for
me. I was hoping to find a way to use FrontPage to create different
subwebs with the same name but different cases. The new subwebs with
different cases would then be used to redirect traffic to the original
subweb (which has distinct capitalizations)

Thanks, Pinto
 
That can only be done on the server, and you will not be able to get a copy
of the entire website onto your Windows PC.
Open your live site in FrontPage, then create subwebs as you wish.
My choice would be to create 301 redirects in the root .htaccess file, that
filter all requests to incorrectly cased folder to the correct one.
Be very careful editing this file - FrontPage is dependant on its contents.
 
Back
Top