DanYork

I’m having the same issue. Running Editorial Calendar 1.8 on WordPress 3.3.1 and running WP in MultiSite mode. When I look at the calendar for published posts, I see multiple instances of [inherit] for each blog post. Here is a screenshot:

https://skitch.com/danyork/g33pn/calendar-with-inherit

While my site *does* use custom post types, this is the calendar for just regular old posts. I wondered if this had something to do with revisions, as the “[inherit]” posts all had links on the “View” link that included something like “-Revision-2” and all went to a 404 if you viewed them… but could be edited if you clicked the “Edit” link.

In digging further, I found this example of the process a post goes through and noticed the “inherit” post status:

http://codex.wordpress.org/User:MichaelH/Testing/Revisions

I went looking through the code of the Editorial Calendar plugin and found this section where the list of posts is found:

/*
     * When we get a set of posts to populate the calendar we don't want
     * to get all of the posts.  This filter allows us to specify the dates
     * we want.
     */
    function edcal_filter_where($where = '') {
        global $edcal_startDate, $edcal_endDate;
        $where .= " AND post_date >= '" . $edcal_startDate . "' AND post_date < '" . $edcal_endDate . "'";
        return $where;
    }

I changed that to include AND post_status != 'inherit' as seen here:

/*
     * When we get a set of posts to populate the calendar we don't want
     * to get all of the posts.  This filter allows us to specify the dates
     * we want.
     */
    function edcal_filter_where($where = '') {
        global $edcal_startDate, $edcal_endDate;
        $where .= " AND post_date >= '" . $edcal_startDate . "' AND post_date < '" . $edcal_endDate . "' AND post_status != 'inherit'";
        return $where;
    }

And that is now working fine. I’ll send this in to the email address for the plugin authors to let them know.

I tried to do an upgrade tonight of my WordPress Multi Site install to 3.2.1 but ultimately had to revert to 3.1 because of the *glacial* slowness of 3.2.1.

The automatic upgrade “worked” in that when it was done my admin interface showed I was in 3.2.1… but the interface was so painfully slow that I couldn’t even get over to “Update Network” to update all my sites. Wherever I clicked in the Dashboard, it took literally *minutes* for the page to appear.

I tried the upgrade several times (I have a tarball of the 3.1 install that made it easy to return to the prior state). I de-activated all plugins. I *moved* all plugins to that the plugins directory was empty. Nothing worked.

At this point I went back to 3.1 because I need a site that my users can *use*. 🙁