Darren Ethier (nerrad)

Michael (satoridork). You’re getting fatal errors with Organize Series? It’d be great if you could post something about your issues on my Support Forums. This is the first time I’ve heard of fatal errors…

The new release of organize series is out. I think I’ve taken care of some of the inefficiency

Just a heads up that I’m working on a release of Organize Series that I hope to have out by the end of August that will fix this issue. I still would like to reduce the number of db queries that orgSeries uses overall, but with the upcoming fix, increasing the number of posts in a series will NOT increase the db queries when rendering (ONE query for all posts instead of a query for each).

Thanks again for pointing this out – it helped me spot where the code could be more efficient!

The problem was actually in the function set_series_order().

misstee,
You’ll have to describe a little bit better what you are wanting to do… Are you talking about the Series Table of Contents page that lists all the series OR just the table of contents page for that particular series?

Yes, as the plugin author I recommend that users of Organize Series do not use the plugin with WordPress 2.6 until I am able to publish a fix. I have identified the source of the problem but my available time to work on Organize Series is short so the fix might be a few weeks coming.

For those wanting the first news of a new version you can subscribe to the Organize Series Feed.

Are you talking about the download link at http://unfoldingneurons/neurotic-plugins/organize-series-wordpress-plugin or the link at http://wordpress.org/extend/plugins/organize-series/ ?

No hostility from me either gestroud. I just didn’t think your title was appropriate based on the scenario you gave for your problem.

Here’s a couple questions I would ask to help troubleshoot your difficulties. Thank for the further details with what happened as you are describing but let me explain a couple of things about how Organize Series works so you’ll understand what happens on the backend.

1. Organize Series 1.6.3 and earlier integrated with categories in pre WordPress 2.3 (i.e. post2cat, and categorie tables) BUT did not do any custom writes to the db. All it did is read the database information and optimized “series” categories for display. So… at worst, if you installed an older version of Organize Series 1.6.3 on a WP2.3+ blog you’ll simply get a query error because the post2cat and categories tables no longer exist).

2. Organize Series 2.0+ integrates with the new taxonomy system of WordPress and reads and writes to the new tables (wp_terms, wp_term_relationships, and wp_term_taxonomy) using the plugin api WordPress provides. It is technically impossible for Organize Series 2.0 to delete any of the post2cat, and categories tables UNLESS there are incorrect WordPress core files in your install (files that did not replaced in the upgrade process from pre 2.3 to 2.3.3 and 2.5). In this case the plugin hooks that Organize Series 2.0 are definitely not functiong as expected because they aren’t the right ones. In this case , it is not the fault of Organize Series but the fault of a bad WordPress upgrade.

3. The import function of Organize Series for people upgrading to a new version simply copies over information from the previous category structure that orgSeries 1.6.3 and lower used to the new taxonomy structure in orgSeries 2.0 and greater. Again, this import procedures uses all the core WordPress plugin api hooks and does not carry out direct custom db queries so on it’s own OrgSeries will not delete any existing WordPress tables.

4. OrgSeries 2.0 does create a new table at activation of the plugin for storage of series icons but that won’t lead to the symptoms you described.

My suggestion and what I think is the root of your problem…
When you upgraded your WordPress install from pre 2.3 to WP2.3 (or imported a pre WordPress 2.3 database file into your WordPress 2.3+ install) there were some core WordPress files that didn’t get copied properly and so you may have thought everything was working properly but in fact you were running some sort of “hybrid” and for some reason it worked fine until Organize Series exposed the problem.
A FIX:

• Make sure you delete all the WordPress core files from your server and then install a fresh copy of WordPress 2.5.
• Import your database backup file and set it up.
• Run the WordPress upgrade script manually (…/wp-admin/upgrade.php)
• Check your database structure and make sure post2cat, link2cat, and categories tables are NOT present (If they are then something is wrong with your WordPress install).
• Check out WordPress admin and front end and make sure everything works as expected
• Install Organize Series and it should work fine

Report back here how things went. BUT in the meantime, can we please have a title change? My suggestion, “Upgrade loop with Organize Series?” – it’s a little less alarming (and not misleading) and still provides a clue as to what the thread is about.

First off, gestroud, did you even read my first reply? The problems you are describing have nothing to do with Organize Series. The database tables you are describing being “killed” by Organize Series are in fact non-existant in WordPress 2.5 databases. So how then, can Organize Series kill something that doesn’t exist?

Before posting any more I really suggest you investigate some of the suggestions I gave you in my first reply – otherwise you simply look foolish. Believe me, I’m trying to help – but your title is NOT accurate based on the problem you’ve described!

Oh, in case it’s not clear. I’ve never said in this thread that Organize Series is not compatible with 2.5 – all I’ve written, is that based on the problem you described – it looked like you have a pre-WP2.3 database. Organize Series 2.0.x only works for WordPress versions 2.3 and up (including 2.5).