LoopyCMS Administration - Creating Content Types

Dateline: September 18, 2003

Overview Content editing Content Tools Sending Newsletters

Creating Pages Editing PhotoAlbums Create a Content Type Restore from Backup

Remove old backups Siteman Site Configuration

Creating the actual folders for a new Content Collection are pretty simple. The real work of setting up a new Content Collection is in creating the pages afterwards.

First, you're asked for the Name of a new content type. If you name an existing Content Collection type, BZZZT, no go, you'll get an error message. If you try to create a Content Collection for "Admin" or "Images" or "Includes" -- also BZZZT. Those are special directories intrinsic to the LoopyCMS and it would either be logically confusing, non-sensical, or potentially a security problem if you were allowed to do so. Ok, maybe not a security problem, but it wouldn't work, because Includes - the actual code that runs the applications - is a virtual root and not accessible as a content type. Same thing with Admin - the admin tools run from there as a virtual root. Images? Well, I suppose it would be possible, but it would be confusing and not make much sense. Images are images and not ".htm" files. Content Collections are about ".htm" files.

As to what the heck a Virtual Root is? It's just a directory that is not under the wwwroot directory (assuming that's where you're web root folder is), but that your webserver has been instructed to treat as if it were. If you want more information on virtual roots, see the configuration section, where we'll be configuring some to make the LoopyCMS run.

Well, anyway, assuming that you chose a non-reserved name and clicked submit, you'll receive this instructive document on your next steps. It recommends you print it out and follow its instructions for creating the pages for the new Content Collection.

Now if you're looking for a shortcut to creating the five recommended pages, copy the files in the "/Articles" site directory (under wwwroot) and paste them into you're new folder on the site. Edit the View.asp and pfView.asp files and change the content type from "articles" to your new type and away you go.

You also still need to set up the redirect.asp page to be the 404 error page for that directory (as previously mentioned and covered in the configuration section at the end).

OK, onward -- Restore from Backup