Steve,
Actually... I see what is going on now... it's incorrect path issues.
Because I don't know everything you've done so far... I will make some recommendation to quickly resolve it and get you on your way.
First, it appears you have the all the CMS files still in the CMS100 folder now... is what I would first do is take them out of that folder and put them in root level. This means you admin login will be a bit cleaner to start with admin
Then for your settings
$WAGLOBAL_Root_URL = "http://yoursite.com/" ; //Absolute path to your site folder.
$WAGLOBAL_Site_Name = "Your Site Admin" ;
$WAGLOBAL_localRoot = "/"; //relative path to your PowerCMS files on your local testing server.
$WAGLOBAL_remoteRoot = "/"; //relative path to your PowerCMS files on your remote server.
//iRite Images upload settings
$WAGLOBAL_Images_Folder = "images/"; //relative path to your images folder.
$WAGLOBAL_Swf_Folder = "swf/"; //relative path to your swf folder.
// Admin Settings
$WAGLOBAL_Admin_UserName = "yourUserName" ;
$WAGLOBAL_Admin_Password = "yourPassword" ;
That will clean up your paths issue... now be sure that on the root... all of the folder are loaded up there - this includes admin, Connections, css, CSSMenuWriter, Database, images, Templates, WA_CMS, WA_DataAssist, WA_Globals, WA_iRite, WA_SecurityAssist, WA_ValidationToolkit, WADbSearch
Your root folder will now not only reflect a typical site that deploys code from WebAssist extensions, it will be a a little easier to manage.
After you get everything loaded, then try your page... as the paths on the page now will be correct to the paths in your globals and your Power CMS setup.
Let me know if you need anything more.
Cheers,
Brian
