Pods Fail

Always on the lookout for new tools I thought I’d try and install pods.  Pods claims to be a simple cms tool that allows you to create relatable objects. You can create master > detail pages, calendars, photo albums. Seems to be the simple “relational db” plugin I’ve been looking for.

The install instructions are:

1. Copy the pods .htaccess file and overwrite yours
2. Change the permalink to /%postname%/
3. Activate plugin

I followed those instructions and got the following warnings

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /purpleasphalt/wp-content/plugins/pods/init.php on line 33

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /purpleasphalt/wp-content/plugins/pods/sql/update.php on line 4


Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /purpleasphalt/wp-content/plugins/pods/sql/update.php on line 11


Warning: Cannot modify header information - headers already sent by (output started at /purpleasphalt/wp-content/plugins/pods/init.php:33) in /purpleasphalt/wp-includes/classes.php on line 1569


On I trudged ignoring the errors. I was able to create a new pod, or at least it showed up on the screen, but when I refreshed, it was gone.

I started poking around the comments section of the site and found that the warnings would be cleared up in the next release. I also noted that issues can be cleared up by removing the associated pods tables, and that they would be re-created. However it looks like from my warnings that pods could not determine if it had already installed itself. My suspicions were correct when I checked mysql and found that there were no pods tables found.

I’ll post more when 1.2.1 hits and the warnings go away.