HTML site to C5

Permalink
Hi All,

I am transferring an existing site into C5. Most pages are named pagename.html which become /pagename/ in C5 which is fine. I was thinking this would be fairly easy as there are many internal links to the HTML pages and I could drop the .html extension and create almost the same page name. However, there are some existing directories/filenames that are named with uppercase/camelcase letters (indexed in Google for years this way) and C5 is not allowing uppercase when I create a directory or path. Is there a way around this in C5 or will I need to do a mod rewrite for all old URLs? I was hoping the keep the rewrite rules as simple as possible on old file names.

Thanks,
Hope

HopeL
 
hemantyadav replied on at Permalink Reply
Hi Hope,

May this link help you.
http://www.concrete5.org/documentation/how-tos/designers/making-a-t...


Thanks
Hemant
HopeL replied on at Permalink Reply
HopeL
Thanks Hemant but I don't see anything on that page about URLs or URL slugs that can help me. I see a lot about styles and CSS but nothing about the case of the actual page name or directory name. If you know where that is in the text and I've missed it, feel free to point it out.

Hope
mnakalay replied on at Permalink Reply
mnakalay
I might be wrong but are you sure it matters to Google that your paths change to lowercase?
juliandale replied on at Permalink Reply
juliandale
I don't think Google cares about case sensitivity in URLs.

A tip that may help you is to add the old URL path (e.g. pagename.html) to the new page within the Page Properties. Go to the Page Paths & Location tab and enter the old path in the More URL's section. That will catch any links within the content that still point to the pagename.html page. You may also want to use 301 redirects to help with this kind of issue.
HopeL replied on at Permalink Reply
HopeL
Google may not care about the case I use but if I forget to redirect links, I may end up with duplicate pages (even if the old are deleted) and that issue Google does care about. However, adding the old URL path in the Page Properties area may very well help quite a bit. Thanks so much for that tip!
HopeL replied on at Permalink Reply
HopeL
juliandale wrote:
-------
A tip that may help you is to add the old URL path (e.g. pagename.html) to the new page within the Page Properties. Go to the Page Paths & Location tab and enter the old path in the More URL's section. That will catch any links within the content that still point to the pagename.html page.
-------
After looking into this I see in the documentation that you cannot use .html in the More URLs field:

This feature is very handy if you're worried about legacy links from an older version of your site that may be still getting traffic. Unfortunately putting a ".html" at the end of a Additional Page URL will not work.
-------
Unless it will work with a wildcard such as pagename.* in the More URLs field, it will mean a lot of redirects in .htaccess.

So back to one of my first questions in case someone else out there has done this - is there any way to change the directory or page names within C5 to upper or title case? That would really come in handy.

Hope
juliandale replied on at Permalink Reply
juliandale
That documentation must be out of date. Try it for yourself and you'll see that it works with .html extensions.

With regard to the uppercase and directory page names, I think that may be more of a question to ask in a forum for your type of web server (probably Linux) rather than Concrete5.
HopeL replied on at Permalink Reply
HopeL
That's great news! Thanks for letting me know.

As for a Linux forum. The reason I posted here originally is because I wondered why Concrete5 is changing the case (AAA to aaa) when I enter an URL slug in the page properties and if there was a way to prevent it. When first entering a directory/filename it "appears" as though it will keep the case but when I go back to look at the page properties is when I discover the case is changed. I understand I can manipulate things through .htaccess but if I could prevent it from happening to begin with since it's C5, that would be good. It's not that big of a deal if C5 is changing the case - it would just be more convenient if it wasn't.
juliandale replied on at Permalink Reply
juliandale
There's definitely one place where I can see that URLs are converted to lower case:
/concrete/libraries/3rdparty/urlify.php

Look around line 232 and you'll see the filter function converts the text to lower case. Commenting that out may help a little, but I think there's a more important place where the URL is changed upon saving, I just can't find it yet!
HopeL replied on at Permalink Reply
HopeL
Thanks juliandale! I will give it a try. Much appreciated!
HopeL replied on at Permalink Reply
HopeL
Unfortunately, commenting out the line in the urlify.php file didn't help. I've looked through several files and there are a lot of references to stripping out camel and uppercase so I suspect this is not a quick fix. I will work it out another way but it's been a fun exercise. Thanks again trying to help with this.

Hope
mhawke replied on at Permalink Best Answer Reply
mhawke
I just tested out the Page Path configuration and it accepts mixed-case paths with .html extensions. Why not just use the tool that concrete5 already has to solve this?

http://definitiveweb.ca/WhyConcrete5.html...
HopeL replied on at Permalink Reply
HopeL
Thanks so much mhawke! I assumed that field would also transform the case but it makes perfect sense that it doesn't.
thephilm replied on at Permalink Reply
thephilm
Just a note - Google doesn't "care" about case, but if it crawls the site, and finds "yoursite.com/page" and "yoursite.com/PaGe" and both serve content... it will treat them as separate pages... creating duplicate content. (Bad for SEO)

It's a best practice to make sure everything is consistent, by either making sure you use cases the same everywhere, or make everything lower so you remove the chance of duplicate content.
Case sensitivity issues are usually from people linking to you who hand type the links. Making sure the destination URL is always lowercase makes sure that you don't run into this.
- A quick Google search confirmshttp://www.searchdiscovery.com/blog/seo/case-sensitive-urls-and-seo...
HopeL replied on at Permalink Reply
HopeL
Thanks thephilm. I appreciate the help but I am aware of this and mentioned something about it in one of my replies above. When one takes over a site, one must deal with the existing URLs but it's certainly a good idea to be consistent from that point on.
HopeL replied on at Permalink Reply
HopeL
I guess there's no way to mark more than one post in the same thread as best answer... :-(