PowerCMS and Extensions Updates

I purchased PowerCMS 1.0.0, along with the Super Suite a few months ago. I am developing a PHP website, using the supersuite extensions, and Dreamweaver CS4.

I have been updating the various extensions since my purchase.

I have just started to deploy the PowerCMS solution to my website. As this solution is a zip file of the php code, I have a few questions?

1. General - As PowerCMS utilises iRite (and other WA Extensions) what happens when these extensions gets updated? I have now received at least one update to iRite, to Version 1.03. What version of iRite is used in the PowerCMS solution? Can we overwrite the original version that comes with the Zip File, with the latest version?

What happens, if I were to move all files from their original folder \CMS100\.. to the Root folder of my site, then would there be conflicts if I install the latest version of iRite, and utilise this functionality in another part of my web site. I also noticed that it uses WA_Validation_Toolkit. I have just purchased the CSS Form Builder and had installed that (firstly removing the original Validation Toolkit extension). Applied a Form using this tool prior to installing the PowerCMS. I noticed that there were differences in the php code between the two copies of Validation_toolkit. Which one do I use?

As this solution also utilises, other components such as Security Assist etc then whenever these extensions get updated how will they affect PowerCMS's functionality.

2. As an initial implementation I installed PowerCMS as is into my site under the folder of CMS100\.. I adjusted the Globals file as follows:

<?php
$WAGLOBAL_Root_URL = "http://localhost/" ; //Absolute path to your site folder.
$WAGLOBAL_Site_Name = "Site Admin" ;

$WAGLOBAL_localRoot = "/CMS100/"; //relative path to your PowerCMS files on your local testing server.
$WAGLOBAL_remoteRoot = "/CMS100/"; //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 = "" ;
$WAGLOBAL_Admin_Password = "" ;
?>

I pushed the site to my Test Web Site (local pc running WIndows Vista with PHP and MySQL installed locally)

I could login to PowerCMS ok and create some content pages with text. I applied the <PHP> code to the relevant pages through Dreamweaver and pushed all content to the Test Server. I could see my newly created content ok.

The first Issue I have is that when I tried to add an Image to the content (e.g. a small gif file) I have had many error messages etc. "Invalid File" is one and it wont allow me to copy the file. When I pushed this site to my current Real Web server (Windows 2008 Srv / IIS running PHP 5.2 and MySQL 5) I also could not seem to save a file to my website cms100/Images folder.

2nd Issue: After manually copying the image file (via ftp), when I try to insert it into my text page using iRite, I get the wrong path (see attachment bitmap), the address should be say top.gif but as you can see from the attachment it defaults to top.gif. Unless I manually add the /cms100/ path, the image cant be found.

I know this posting is rather large, but what is the management plan for PowerCMS, in terms of the updates to the various Extensions that this product uses, and is there any fixes or explanation to the pathing problem.

Regards

After submitting this posting, I read some other posts talking about the Global definitions.

I changed my global Root URL to cms100/ and now when I select an image file, i get the right path. So if this is the correct way to define the global definition, can you please update the "Customizing the PowerCMS Globals file to reflect this, as it states use "http://localhost/" or "http://www.mydomain.com/" but doesn't mention to add the cms directory.

We'll look into the How To to ensure that it is correct.

Here are some responses to your other questions...

You can upload PowerCMS to any directory you desire, the cms100 directory is not necessary at all. As you've already experienced, you just need to enter the appropriate paths in the WA_Globals files for everything to work.

As far as WebAssist extensions and updates go, don't be surprised if there are some differences in the code you see in a Solution Pack vs. what is produced by an extension. For example, CSS Form Builder was developed after PowerCMS was launched and was therefore not used in the creation of the Solution Pack.

You should have no problems applying iRite to other pages on your website. The only issue would be if you are adding it to pages within the cms100 directory where you have PowerCMS stored, it may try to overwrite the WA_iRite directory and cause issues.

Your explaination of the differences between the various extensions used by PowerCMS and their related updates (ie iRite .dot release) confirms what I thought. If you are going to look at the documentation regarding PowerCMS, maybe you should also include that PowerCMS really should be placed in its own directory structure so as to avoid conflicts when you install later versions of the various extensions.