Napata CMS 1.6.0.2013 and Napata Flat File CMS 1.6.0.2013 Released

Napata CMS 1.6.0.2013 is now out and it's packed with something sweet for all you web developers: Twitter Bootstrap. This release comes with Twitter Bootstrap 2.3.2 plus some awesome Bootstrap swatches from Bootswatch. Furthermore, I've pushed the project to the GPLv3 licence. For the full changelog please read on:

Napata CMS 1.6.0.2013

1. New: "Edit Summary" textarea form element.
2. Change: Edit.php and create.php layout tweaks.
3. Change: NOINDEX, NOFOLLOW, NOARCHIVE robots for all special pages.
4. Change: Admin_Pages title and text  changes to reflect that the administration page is for "articles" and not "pages".
5. Change: Main Administration page fix to the article-administration link. Link now reads "Admin Articles" instead of "Admin pages".
6. Fix: Generic error message printed on the homepage when the static page selected for display on the frontpage does not exist.
7. New: Twitter Bootstrap 2.3.2 integrated.
8. New: Superhero, Amelia, United and Cerulean Bootswatch themes added.
9. Fix: Fixed a bug to the installer that caused the configuration form not to show.
10. Fix: File inclusion error and styling changes made to the error files.

Napata Flat File CMS 1.6.0.2013

1. New: Both front-end and backend theming is provided by a single stylesheet that is defined in the configuration file npt-load.php.
2. Change: css/admin folder removed. Administration theming is now provided in a single stylesheet.
3. New: ClearStatCache() method added.
4. New: Generic content displayed on the frontpage if the INDEX.txt file does not exist in the CMS installation directory.
5. New: File modified timestamp printed at the bottom of each article.
6. New: Twitter Bootstrap 2.3.2 integrated into the core.
7. New: Amelia, United and Cerulean Bootswatch themes added to the pre-installed themes.
8. New: Added "Theming" article.

That's it for now. If you find any bug, you can lodge it on the projects' Sourceforge Issue Trackers. Here the project pages for the database-driven CMS and the flat-file one: Napata CMS and Napata Flat CMS. Woohoo! Enjoy, ;-). I'm out.

Napata Flat File CMS 1.5.2013 Released

Slightly one week after I released the database-driven Napata CMS 1.5.2013 release, here comes the latest flat file package of the CMS. Here is the changelog for the release:

1. Change: Moved the Console code to the main NapataFileCMS class file.
2. Change: Moved the Admin page code to the main NapataFileCMS class file.
3. New: Added new method: AdminPage();
4. New: Added new admin page: PHP Info page.
5. Change: NOARCHIVE, NOFOLLOW, NOINDEX robots for Login, Console and Admin pages.
6. New: DeFunkt front-end theme added to the pre-installed themes.

That's all. Remember you can get the script on both Google Code and Sourceforge. Just follow the links on the right sidebar of this blog and get started.

Happy New Year! Napata CMS 1.4.1.2013 and Napata Flat File CMS 1.4.2013 Released

What a great way to start the year. Napata CMS 1.4.1.2013 and Napata Flat File CMS 1.4.2013 are out. Here are some quick overviews of the changes I have introduced in these releases.

Napata CMS 1.4.1.2013

This is mainly a bug fix release. I have implemented some minute fixes to the Markup package and the Markdown package. The main bug fix was in the WYSIWYM package. The bug affected the 404 error pages. The complete changelog for this release is as follows:

1. Fix: Error functions bugs. All SQL queries use PHP PDO. (WYSIWYM package)
2. Fix: Text formatting rules fixed to show the correct Markdown syntax in the Markdown package. (Markdown package)
3. Fix: Sitename displayed on the "Text Formatting Help" window.

Napata Flat File CMS 1.4.2013

As for the Flat File package, I have included a simple admin page that checks for some system and script environment settings. Some bug fixes also ship with this release. Here is the complete changelog:

1. Change: Admin home panel shows some basic environment settings of your server and the script.
2. Change: Security fixes.
3. Fix: 404 error thrown for articles not found.
4. Fix: File size checks prior to uploading to the Articles directory.

 That's it for now. You can download the latest releases on both Google Code and Sourceforge. If you like the scripts you can star them on Google Code or recommend them on Sourceforge. Enjoy!

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.