Napata CMS 1.4.2012 Released

Napata CMS 1.4.2012 is now out. This is the main database-driven script of this project. The main change in this release is that the script now uses PHP's PDO to run all database queries. This is a major improvement since the use of mysql_* functions is not recommended; these functions are deprecated. Additional changes include bugfixes to the rendering engine, addition of a "My Account" link to the ActionLinks bar, a revamped admin area and the inclusion of static pages. Here is the complete changelog:

1. New: SQL Queries rewritten to use PHP PDO.
2. Change: "My Account" link introduced.
3. Fix: Theme fixes.
4. Change: Method showErrorPage() for error pages.
5. Fix: Data validation for user query.
6. New: Parser extension Box tag.(Markup variant)
7. New: Parser function extended. Arrows syntax, forced line break, Alert, Incomplete, Notice tags methods.(Markup variant)
8. Fix: Data validation on special pages' queries.
9. Change: Code cleanup
10. Fix: Security Fixes.
11. Change: SQL syntax improved; to improve site performance.
12. Change: Administration panel improved.
13. Change: Footer template changes shows Admin Email.
14. Change: Renamed the Installer Check file to Check.php
15. New: Check.php checks for register_globals and allow_url_fopen settings too.
16. New: RevisionMessage() added. Shows the latest page link when a revied page of the same name is accessed.
17. New: Theme tweaks to pre-installed themes to show the RevisionsMessage.
18. New: Die Syntax introduced. Syntax format is die{{Your text....}}die. (Markup Variant)
19. New: Edit summary now shown on the "Revisions" and "All Pages" pages.
20. New: Update script revamped. You can upgrade your site by pointing your script to the update.php script.
21. New: Check.php checks for update.php script too.
22. New: Static pages introduced.
23. New: Navigation generated dynamically. Navigation items consist of static pages.
24. New:Action links replace forms on all pre-installed themes.
25. Change: "Hello World" article replaced by a sample article.
26. New: Last modified timestamp shown on "All articles" and "Revisions" pages.
27. Change: Update scripts' queries re-written; queries now use PHP's PDO.

Remember, you can get the script on Google Code as well as Sourceforge.

Napata Flat File CMS 1.2.2012 is out!

This comes approximately 1 month after the release of the script's first release candidate. But that ain't late at all. This release fixes a phoney bug that caused PHP code to display instead of the action links on a web page. Additionally, some other cosmetic changes have been made to the script. Here is the entire changelog for the flat file cms script:

1. New: Config file added: npt-load.php
2. Change: Moved $copyright variable to npt-load.php config file.
3. Change: Added DIRPATH costant to the config. Points to the absolute path to the folders.
4. Change: Deletion of error_reporting code in some pages. Config file now handles the error_reporting code.
5. Fix: Fixes to E_NOTICE and E_WARNING errors.
6. Change: Sidebar styling changes.
7. Change: Renamed the sidebar heading from "Other Articles" to "Articles".
8. Fix: Replaced PHP short tags on ActionLinks method to fix display problems of action links.

That is all for now. Remember you can download the latest release both on Sourceforge and Google Code (see the sidebar links on your right). Woohoo! I'm out.

Napata Flat File CMS 1.2rc1.2012 Released

The first release candidate of the text file package of Napata CMS: Napata Flat File CMS 1.2rc1.2012, is now out in the wild.
It is very simple to set up a single page brochure site using this script. Simply unzip the package and upload it to your server.
You can then add other articles to the site using an FTP client or the File Uploads console on the site.
It is as simple as that.

Here are some of the features of this script:

1. Requires no database.
2. No installer.
3. Text files CMS
4. No administration backend.
5. Static frontpage.

The project's SourceForge and Google Code pages are:

1.  http://sourceforge.net/projects/napataflatcms/ 
2.  http://code.google.com/p/napata-flat-file-cms/

NOTE: This is a release candidate and is meant for testing purposes only. Do not use this on a production site. Nicked a bug? Simply post on the project's Google Code issues tracker [http://code.google.com/p/napata-flat-file-cms/issues/list] or on the project's Sourceforge bug tacker[http://sourceforge.net/p/napataflatcms/tickets/].

Napata Flat File CMS Release Candidate 1 on the Way

I'll be releasing the first release of the minimalist, text file only package of Napata CMS in the coming days. After a week of inspirational coding and running of tests on the script over the scraps of free time I can get, I am happy to say that the result is usable. Remember, this script will not be a detail-to-detail replica of the main, database-driven script (please read this post to get a grip on the design principles of the flat file CMS).

Download Sites for the Script

If you would like to download the script you can get it on both Sourceforge and Google Code. Here are the links to the project pages:

• http://sourceforge.net/projects/napataflatcms/
• http://code.google.com/p/napata-flat-file-cms/ 

Migrating to PDO and (may be) Create a Text-File Napata CMS

Moving over to PDO? Yup. This will be one of the main, in fact the main objective for the development of the upcoming release of Napata CMS. Ideally, hanging on the deprecated mysql_* functions is not favourable since the PHP developers discourage the use of the MySQL extension (notice the big red notice above this page. And read this post too.) So there it is. It will take me some time re-writing all the queries but at least I do know every bit of code in the application. Hopefully, by the end of the year, I will have released something, plus some release candidates, that fully depend on PDO for querying the database.

What about a Text File Version of the Script?

This is in the pre-alpha stage. Actually, my idea is that of a minimalist version of the script. Actually, I am thinking of it being radically different in it's functionality. It will not have every thing that the main, database-driven script has. It will be a simple, straight-forward script. Dead simple. In fact, I am thinking of it being sort of a Rendering Engine only (no editing interfaces, no relational features between articles, and so on and so on ....). So, well, back to hacking. Wish me some luck in this next effort.