MonoCMS

Main changes include:

- data_connect.php update. Script now exits if session time limit is reached, not depending on ini_set() behaviour only. User gets redirected to login screen.

- Classicmenu plugin is also updated, using some javascript to add the menu in the page.(proper for a plugin)

- pageResults() function is improved to avoid including similar or unwanted values in results per page menu. Some more functions have also been improved in log.php.

- post.php change, including new file prepost.php in every post permanent link page.Categories fix Unlike 1.0, in MonoCMS 2.0 categories did not have a name.txt file to refer to when searching for the category name and was relying on folder name only. This caused failure to load a category page when the two names didn't match. Now a new categories.xmlfile is introduced to save all info needed about categories.(monofiles/filesinfo/categories.xml) A new file is also introduced for categories as in the posts case, precat.php.

- Extensions are now saved in 'monofiles' folder and a respective .txt file is saved inside 'monofiles/ext' folder.

How the .txt files work

Extension .txt files contain three lines of data: First line of the file is the filename of the extension (i.e myextension.php), second line is a title and third line is a description.(*05 Feb edit: please uncomment the content of command.php file for extension support by removing the /* & */ characters. This will be fixed in the next version.)

Also in this update:

- New structure for control panel pages is set, as it was announced in the previous post.

- Plugins page improve. Save button turns off if there are no plugins installed.

- Administrator MUST now be an owner in order to make another administrator an owner. (Note: Owner account cannot be deleted - Only one user can be owner).

- A few design and page elements changes.

Well, not so "new" to be honest, but now it's official (kinda). Every control panel page will follow a - completely optional :) - specific pattern, following this order:

# login

# user rights

# page specific code

# include extensions

# start html

 css theme

panel elements (i.e menus)

action confirm messages ("welcome", "posted" etc.)

 any other html or php code needed by the page

include plugins

# end html

All the years of making these pages bring us to the safe conclusion that this can be a nicely working page structure, for most cases.This is going to be included in a new update, hopefully coming soon.

- New version with minor aesthetic changes.

- A small change in core files to fix the date still appearing when turned off from the settings.