Comments on: Anyone knows a newspaper CMS?

PacerCMS was built for

Stephen Yeargin — Sun, 04 Feb 2007 15:58:00 +0100

PacerCMS was built for student and non-daily community newspapers. It runs on PHP/MySQL and uses the Smarty template engine.

hey Gerd, look here

3dsl Eugen — Sun, 03 Dec 2006 03:58:55 +0100

hey Gerd, look here http://www.opensourcecms.com/

This is an old thread, but

Eferi — Thu, 05 Oct 2006 18:13:05 +0200

This is an old thread, but Joomla can do this type of differentiation. It's called Author alias.

Yep, fully compatible :-)

Andrew — Thu, 29 Sep 2005 18:54:42 +0200

Yep, fully compatible :-)

No, I am afraid not. There was a plugin that allows to transfer

Sencer — Sun, 11 Sep 2005 21:54:46 +0200

No, I am afraid not. There was a plugin that allows to transfer ownership:

http://compooter.org/article/119/textpattern-plugin-ajw-admin-workflow

But I don't know if it's compatible with the current version of Textpattern.

Hello Sencer, thanks for your reply.

Gerd Riesselmann — Sun, 11 Sep 2005 20:59:08 +0200

Hello Sencer, thanks for your reply.

For a newspaper, not all authors also are users of the CMS. So, from a programmer's perspective, "author" simply is an editable property of an article. Does Textpattern handles it this way?

Hi Gerd, Textpattern makes this distinction. You can set perm

Sencer — Sat, 10 Sep 2005 00:32:49 +0200

Hi Gerd,

Textpattern makes this distinction. You can set permissions (in lib/admin_config.php - this will eventuall move into the db together with an interface), such that one group can only create and edit drafts, and another group can publish this article. However it does not save who is the repsonsible publisher for an article - only who was the last person to edit it - which might be a problem if you have many publishers. If you're still interested and have some more questions just ask (I am subscribing to the comments).

It does meet all other criteria. Templates are only stored in teh database and have to be edited through the interface. Plugin-Hooks are plenty, especially for adding functionality to the admin-side (which is btw not templatable, except for changing css and images); For the templates/front-end it uses a tag based language, which can be equally used to call built-in functions and plugin-functions.