Comments on:

By: WordPress As a CMS

WordPress As a CMS — Mon, 12 Oct 2009 14:01:48 +0000

[...] out of the box, so NoScope.com discusses it’s shortcomings and some possible improvements:10 Changes To Wordpress That Would Make It A Killer CMSIt would also be nice if you took the time to keep your WordPress CMS somewhat user friendly so [...]

By: Joen

Joen — Mon, 25 May 2009 18:40:22 +0000

Awesome, I’m gonna try that. Thanks.

By: Loren

Loren — Mon, 25 May 2009 18:19:57 +0000

I am using the plugin successfully with the K2 Theme but I had to make the following changes to the code.

I replaced every instance of:

`$page_template_ex_path = TEMPLATEPATH . ‘/page-’ . $post->ID . ‘.php’;`

with the following

`$page_template_ex_path = locate_template( array(‘/page-’ . $post->ID . ‘.php’), true );`

This was based on a suggestion by Eric Marden regarding the use of template in a child theme with current versions of K2.

By: Joen

Joen — Mon, 25 May 2009 13:21:52 +0000

Yes, it’s a nice plugin now that I need it. But like these two in the forum, it’s not working for me, for subpages whose parent page has the default template:

http://wordpress.org/support/topic/253146

By: James John Malcolm

James John Malcolm — Thu, 07 May 2009 20:23:59 +0000

Loren: [..] It is called "Page Template Extended".(http://wordpress.org/extend/plugins/page-template-extended/).However, I think it should be a core capability.[..]

Holy crap! That's an excellent plugin!

By: Paulo Ren

Paulo Ren — Thu, 07 May 2009 18:26:45 +0000

It all would be just perfect!

By: Nate

Nate — Wed, 06 May 2009 16:32:26 +0000

Great round-up, but it seems a lot of your feature requests are already available as plugins. I think WordPress is in a tough spot, needing to be cautious about trying to be everything to everyone. It's following has grown as it added more CMS-like features, but it risks turning people away if it goes too far in the direction of Drupal or Joomla with a custom field and widget overhaul. I certainly agree that the WYSIWYG editors have got to be improved. They should be available for the widgets, and they need to stop murdering code. The use of hr's is a complete disaster. It's been a known issue for quite some time, and I don't think it's gotten enough attention. That's number 1 on my list.

By: Joen

Joen — Thu, 30 Apr 2009 20:44:52 +0000

Thanks for the tip. I’ll look into page template extended when I need it.

I agree it should be a core feature.

By: Loren

Loren — Thu, 30 Apr 2009 20:40:05 +0000

Actually there is a plugin that does this which I have played with a bit. It is called “Page Template Extended”. (http://wordpress.org/extend/plugins/page-template-extended/). However, I think it should be a core capability. That way developers can count on stability and continuity.

By: Karl

Karl — Thu, 30 Apr 2009 11:51:59 +0000

Good list there - I'm also very excited about WordPress' CMS capabilities. Have a look at qTranslate for multi-language - we've used it on a bunch of sites and found it heaps better than gengo or other plugins. Also interesting in relation to custom fields, are the plugins Pods and Flutter, where you can create new content types, rather than just extending posts/pages. We've used Flutter and while it's perhaps not completely stable, these plugins show what might come. Some would argue being able to create varied content types is a hallmark of "proper" CMS system, perhaps that's true?