PowerCMS 1.0.2

Would also like to commend the latest release of PowerCMS (1.0.2) for its ease of use and for having ironed out the wrinkles in the previous versions.

Two small points though (sorry!):

Although it is fairly easy to work out where one should navigate to (after uploading the CMS folder) in order to begin the process of adding content, I still feel it is worth mentioning in the documentation that one should navigate to the admin/index.php page - especially as this has caused some confusion in the past and has been requested in this forum. Currently new users of the solution need to discover this for themselves.

Also, the 'Getting Started Guide' (powercms_gsg.pdf) is the exact same document as the 'Adding Content to PowerCMS' (powercms_creating_content.pdf). This may be deliberate, but it leaves one wondering if one has downloaded the right PDFs.

Otherwise, version 102 definitely goes up to 11.

One little thing I noticed (and I'm still not sure if this was my fault or some weird glitch). When I built my db, the database name had a capital letter in it. But it wouldn't accept that name after I uploaded. I changed the capital to lowercase and all was fine. So check that if anyone has any problems. I'm pretty sure it was supposed to be capital but I could be wrong....wouldn't be the first time :)

Neilo, I will forward your comments.


Gruant,
The PowerCMS SQL File does not create the database, only the tables.

Some OS's handle case sensitivity differently, because of this, it is a best practice to use all lower case names for the database and tables. See the following MySQL article for more information:
identifier-case-sensitivity.html

no, I knew that it wouldn't create the db just the table. But I didn't know about the Uppercase issues, thats good to know for the future. Thanks

Thanks for the documentation feedback. We'll be updating the PowerCMS docs as soon as we can.

For future suggestions such as these, please use our contact form and choose Documentation in the Type menu.
submit-idea.php

This way, feedback is delivered straight to the documentation team and is more likely to get addressed. Support also doesn't have to spend time forwarding the suggestions.

Thanks Neil,

You've mentioned that before, - apologies, I forgot.