Comments on: Spotlight: WordPress Pods Plugin

By: ErisDS

ErisDS — Thu, 09 Sep 2010 18:50:49 +0000

If you need specific help, please provide code either here or use the contact form.
If you can write in English, that would help… my German isn’t that great.

Mind you, I guess code is the same in every language :)

By: Homewood

Homewood — Thu, 09 Sep 2010 18:06:56 +0000

Sehr interessant. Kommt hier noch ein weiterer Beitrag? Würde gern einiges mehr darüber erfahren. Kannst du mir per Mail weiterhelfen?

By: Buck Letman

Buck Letman — Wed, 10 Mar 2010 10:22:19 +0000

You made several suitable tips there. I did a search for the subject and uncovered a number of individuals definitely will agree along with your site. Many thanks

By: ErisDS

ErisDS — Wed, 23 Dec 2009 08:18:34 +0000

Absolutely: have to choose the right tool for the job. I find WordPress fits more often than Drupal but that is obviously affected by the type of work I do.

By: Becca

Becca — Wed, 23 Dec 2009 00:45:09 +0000

I would agree that wordpress is more user friendly than drupal, however, it comes as a trade off with what wordpress is capable off. Both systems can be really useful depending on how you need to build your website.

By: Osborne Brook

Osborne Brook — Fri, 11 Dec 2009 13:16:37 +0000

WordPress is so mych neater, cleaner and user friendly compared to Drupal. Drupal’s admin is just horrendous and takes a while to grasp. Pods framework seems very promisssing and I am sure it will get better and better.

By: Toon

Toon — Wed, 09 Dec 2009 21:56:39 +0000

We’ve been investigating WordPress for a few days now as a new CMS platform for our http://www.klasse.be websites. We’ve noticed over the last few years that our sites are moving in the direction of ‘news’ or ‘update’ based sites, ie blogs under a different name. We still have a lot of ‘static’ content in the form of contact lists, archived publications/articles, video content, etc.
I looked at Flutter to create custom content types, but although that plugin is very simple and intuitive to use, it’s basically just a pretty front end for custom fields. Which means all extra fields are stored in the infamous wp_postmeta table, and that’s not a very scaleable or neat way to handle things. Pods handles this a lot better via its own db tables.
The drawback is that -at the moment- pods are a bit isolated from the rest of the blog content. It would be great if the Pod write panels were more like the Post write panel, with the ability to add tags and categories just like with a post.
This ability can probably be hacked in somehow, but it should really be standard functionality.
Great review, and I must say I agree 100% with your remarks, both positive and negative.

By: ErisDS

ErisDS — Sat, 28 Nov 2009 13:29:56 +0000

The view that “Drupal is good for X” and “WordPress is good for Y” is very black and white. It seems a lot of people in the community think that way, but in practice it is a very grey world and you have to approach each project and it’s individual requirements, needs and nuances separately.

There is a lot of debate over whether WordPress is a “CMS” or “Blogging platform”. I would say that a “blogging platform” is a specific case of CMS, and that WordPress is a blog-focused CMS with additional benefits of being intuitive for end-users and being built to be flexible.

I have come across several projects which in the first instance appear to fit the WordPress “Posts and Pages” paradigm perfectly, however as the project evolves new requirement for “data types” emerge. Good examples are any news & information site which also has job listings or testimonials. Moving a whole project to a new CMS just to manage one small section of content does not make sense.

What Pods does is allow you to handle those additional requirements for data management within WordPress very easily. It is an incredibly powerful tool, but it is not a solution for every problem.

What I am trying to get across is that my description of “turning WordPress into Drupal” was just that, a description, to explain to readers the job of the Pods Plugin. Using the right tool for the right job is core to good development. That doesn’t mean the right tools can’t be flexible, particularly when it comes to grey areas and the middle ground where no one tool quite has everything you need.

By: Jowy Hurtado

Jowy Hurtado — Sat, 28 Nov 2009 08:06:38 +0000

“In essence what Pods does is turn WordPress into Drupal. It allows you to define your own content types with multiple fields for adding data so that you can use WordPress’ admin interface and templating system to manage whatever data you want, be it just additional testimonials, or a full-blown product database. It also allows you to define templates for displaying or listing data types & to write helpers and filters to handle the entry and display of complex data.”

Why not just use drupal? It’s a full blow CMS and it seems silly to try an emulate something that’s already been created, tested and proven. Seems like more of people just stretching WP into something it’s not.

By: Tal Galili

Tal Galili — Wed, 11 Nov 2009 18:16:42 +0000

Thank you for this great review article.
I wanted to help others that some of the issues you raised in the end of the post has already been fixed in pods, people can view updates here:
http://pods.uproot.us/version-history/

For example:
As of version 1.7.6 (10/27/2009)
IMPROVED: Brand new file uploader

Cheers,
Tal