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.

4 comments:

Saul said...

Thanks.

Plebejus pedagógus said...

The script is nice, congratulations!
A question: how it is possible to apply special (e.g. Hungarian) letters in the article names (appearing in the sidebar)? for instance I'd like to have an article from the file named "Jövő heti névnapok.txt" I tried to change the encoding in the main file for utf-8 and applied the html special characters in the filename (like: é and õ) but didn't worked.

Thanks,

András

Saul said...

Hello Andras. Thanks for the feedback. I guess you are the first user who has actually sent in a query about this script. If you would like to show Hungarian characters you will have to alter the encoding on the Header() method that is in the NapataFileCMS class (filename: npt-file-cms.php) . Currently, the encoding has been set to ISO-8859-1 (Western Europe) encoding which does not support all the characters (my bad). I'll place the encoding choice as a variable (or a constant) in the next release of the script. Hope that helps.
Regards,
Saul

Saul said...

Hello Andras,
Your suggestion of UTF-8 is the best option. For full support of Hungarian characters within the Western European encoding bracket you can change the encoding to IS0-8859-2.
Regards,
Sau

Post a Comment

top