My system is using: /Sites/

Can I link to this as: or ? (what other variations).

Are you asking about linking in production from other resources? Or are you asking about linking to the folder/page?

You can set the production domain to your liking when configuring the production server. The domain name in CM1 is for reference and allows you to easily check the site and see the domain you are working with.

If you are referring to accessing the “/sitename” section without using “/index” at the end, you should be able to configure your web server to use “index” as the default page for a folder. By default, most web server configurations use index.htm or index.html.

Yes, I meant will we be able to use or do we have to use the entire /Sites/ CM1 gives to us.

The /Sites/ path is used in the CM1 site for preview and management. When your site is public, it will use whatever domain you wish to setup for it on the production side. When the site is published, the folder created for it on the production server is based off of the site name in CM1. But the web address used to access the site is up to you and your web server configuration.

So I then would only use: instead of /Sites/

I wnat to be sure because I have many others editing.

A side note - I am migrating the content over, but a few persons are migrating their sites for me.

If I use the http://www. path it won’t give us a realistic view of the site once we switch over.

I am are working with well over 150 websites, over 4000 .html pages, so I want to be sure what I do now - works once I am done and works once everything is published.

Thank you, I understand now.

With the vast amount of sites I have, I am doing the entire site, including the top navigation. These are department sites that do not live within their division site, so we can have a very short URL.

I am going through the sites quickly, linking to the URL I know them by, because mostly the sites have not yet been created.

The Navigation widget would not work for us, but using the old linking /sitename/ I am used to, will work.

Thank you :slight_smile:

I am trying to view things on a test server - and I am not sure how to link up the pages manually.

The link I am given to use - by the site is:

So is there an .html or .html after the index?

The extension depends on the file/page name when you create the page, or edit the properties. When you create a page or edit the page name, it basically sets the file name to be published. There are no extensions forced on the file name so you are able to leave extensions off or add them on at your will. If you want to have “index.html”, you can simple change the page name to be “index.html” and the HTML extension will be added upon publish.

It is important to note that the handling of extensions, or files without, is dependent on your HTTP server (web server) and what it supports. If you try “index.deb” for example, you will have to modify the web server to understand how to handle the DEB extension.

When I create the page, I give it a basic name - i.e. contact and I am guessing the system is adding a .html at the end.

Do I have to call it: contact.html when I create it? I have not been doing this.

Hi Debbie, by default, a page or section is created without an extension, so the system is not adding .html to the pages. As Daved mentioned, you do have the option of adding an extension to each page by clicking on the “edit meta-data” link within the content tab.

A more efficient approach would be to have your IT department configure your HTTP server to recognize all pages without an extension as .html

I have begun migration again and re-read this and things are still not working.

1 - I do not want to use the internal navigation within CM1

2 - I have created my own drop down menus specific to each of the 200 websites I am migrating.

3 - I have created each site within the related Division > Department - using the Org chart - however each site will not contain any information from the other department sites. Only a link to the parent or child sites.

4 - When I try to use /sitename/page.html > it does not work in the preview.

5 - When I use /Sites/ > it does work.

But I believe someone told me this will not work once I move this to production once everything is ready.

I have tried …/ and /sitename/ and again - not working.

So when I am coding things myself, and pointing to the site - within the site - how should I then link?

Thank you for your patience.

Hi Debbie,

If you’re not using the internal navigation in CM1, I would recommend using relative links. To identify the relative link that will resolve in a published environment, select the page you want to link to using the CM1 Finder. You will see a URL in the address bar of the Finder similar to “/Sites/”. In a live environment, the relative link you will want to use is everything after “”, so in this example “/level-2/index” will be the URL to this particular page.

However, you are correct in thinking that this URL won’t resolve in preview mode. In preview mode only the full “/Sites/” path will resolve. However, you shouldn’t use this pathing on your pages as this will not work on published pages.

Let me know if you need additional clarification of how this works.

After reading this, I am not sure if this is related to the linking issue or not…

I have noticed one issue - when you do “” - it showed “Forbidden You don’t have permission to access /news/ on this server.” but if I add “”. It worked which is fine with me. I’m concerned that they (users) will forget to add index when they’re searching the site. Is there a way “Forbidden” can redirect to index?


If you’re linking to your site via an external source, then yes, “” or “… will work fine.

If you’re adding navigational links to your site which direct to different sections of the same site (via the Rich Text or HTML widget, for example), then yes, you can still use “” or “… as your addresses. Or to simplify, you can just use “/” or “/example_section/” as your address too – the opening forward slash tells the browser that the current domain is the root directory. Note that these types of links won’t work in preview mode, because they will now link to the published site (or the wrong root directory, in the second example).

Of course, if it is your intention to create local links, we recommend using the Navigation widget whenever possible:

You can read more about how links behave in CM1 here:

Let me know if I am misunderstanding your intentions.