Pete Finnigan's Web Development Blog

Cookie Policy:We only use essential cookies on small sections of this website. For details see here.

Oracle Security
Oracle Security Blog

Greymatter Forums

July 2007

Atom 0.3 FEED
Powered by gm-rss 2.0.0

Valid XHTML 1.0!

Powered By Greymatter

Home » Archives » July 2007 » Greymatter 1.7.3 is released

[Previous entry: "Greymatter version hotfix available for download"] [Next entry: "test entry"]

07/05/2007: "Greymatter 1.7.3 is released"

The latest and greatest next release of Greymatter has been released a few days ago. Greymatter is the original weblogging and journal software originally written by Noah Grey and now maintained by a group of developers hosted out of the greymatter forums. It is written in Perl, doesnt need a database, supports most blogging features; comments, banning spam, feeds (RSS, RDF and Atom) and much more.

I have updated this and my other blogs to 1.7.3 and everything seems to be going well. A big thanks as always to Coldstone for his sterling efforts on this version. The new features and updates (from the forum) are:

WARNING: Default wonderland password now crypted, GM 1.7.4 will not allow plaintext passwords, see notice

Refactored gm.cgi to use new request routing logic (to prepare for admin overhaul)

NEW FEATURE: added 'pageing' to Control Panel Log. Pages are 100 lines.

NEW FEATURE: added 'pageing' to Ban List. Pages are 25 lines.

Fixed bug with poorly optimized sorting:


Refactored to use Gm_Security for url and form auths

Refactored out gm_formatentry to use Core methods (removing direct file access).

Refactored direct file access out of gm-karma.cgi

Refactored direct file acesss out of gm-comments.cgi

Search and Replace should now work for the Mood and Music fields

Fixed defect where 'index.' wasn't removed from home and archive links, broken in 1.6.1 - 1.7.2

Fixed issue where some screens had 'Content-type...' at top of.

Updated default templates to use cookie code, entry subjects as page titles, and smartemotions.

Refactored out direct emailing, into Core function

Removed 2000+ lines of deprecated code from gm-library.cgi

Discovered and documented tag Greymatter 1.7.3 is released

Discovered and documented tag 5th

Refactored screens to use CSS and Web functions: Cplog, Ban Ip, Login, front page, authors

Added localization logic functionality to enable translation, not fully propagated

Fixed defect where Preview Does Not Show Preview as Translated

Fixed defect when authors Preview an Entry and then attempt to post it or re-edit it, GM will report an error

Fixed defect where if could edit own entries, listed as 'no' instead of 'own' on edit authors page

Fixed defect where gm-comments.cgi doesn't check for entryid passed in from form

Fixed defect where entrymainbodyfirstwords and entrymorebodyfirstwords didn't work on search results or after commenting.


Fixed defect where Select All on edit entry, didn't select all if there was one item.
add issue to forums and link

Fixed defect where newlines break comments when previewing or doing commenter verification

Fixed defect in gm_DeleteAllSelectedComments where comments where only reduced by 1 on multi-delete of comments


Fixed defect in gm-comments.cgi where forceverify did not follow 'static' preference

Replies: 4 Comments

on Thursday, July 5th, Pete Finnigan said

You could at least make an effort to say what Greymatter *is*. Believe it or not, but not everyone knows your pet-program as well as you do.

on Friday, July 6th, Pete Finnigan said

Sorry, good point. I have updated the post to show a little about what Greymatter is.



on Tuesday, November 20th, Pete Finnigan said

It was good decision to write a little about what Greymatter is. I'm surprised that Greymatter doesn't use a database. It's a little strange...

on Monday, January 7th, Pete Finnigan said

Thanks for your post Robert. Whilst my day job is database security I have always liked Greymatter because of its simplicity of implementation and non use of a database (smaller target). There are however plans to move to a database in the future if the user so wishes.