Zack Grossbart

This makes me think there is an issue with the time of day information on your blog. That is often caused by a conflict with another plugin. Do you have any other plugins installed that affect the time of posts? When you view the calendar are there any JavaScript errors?

Thanks,
Zack

Thank you for using the Editorial Calendar. I’m sorry you’re having an issue with it. I need a little more information to help with the problem.

Are you able to see the time of day for any posts? Can you see the time of day on our demo calendar (https://www.zackgrossbart.com/extras/sandbox/wp-admin/edit.php?page=cal)? What browser are you using?

Thanks,
Zack

Thank you so much for your interest in extending the calendar. The “slush pile” feature request is one we’ve heard a few times. We’ve been thinking about creating a multi-author version of the calendar which would include a slush pile and a few other features. We’re still working on the design.

Another issue with this feature is that I haven’t found a good way to support posts without a date in WordPress. It requires that all posts have dates. Some posts are marked as “publish now”, but they still have a date internally. This makes showing posts without a date in the calendar and having them still work in the normal WordPress edit screens very difficult.

We don’t have explicit extension points in the code, but we’ve tried to make it very easy to work with. We do a simple version of extending the code so we can run our unit tests.

You could take a look at the source code and see what you think. I would be happy to answer questions or give you a quick tour.

Before you look at the code you should read Creating a JQuery Powered Posts Calendar for WordPress. It talks about the fundamentals of how the calendar works.

Good luck,
Zack

This issue is resolved for me now. My plugin page is showing the latest version and everything looks fine.

Hello Rob,

That just sucks. We hadn’t tested enough with the more tag. What happens is that the quick edit only gets your post up to that tag and then when you save you lose the rest of it. We’re really sorry this happened.

The good news is that you didn’t lose any data. WordPress saves each revision of your post. Just scroll to the bottom of the full edit page and you can see them.

The better news is that we’ve fixed the problem. We’ve released version 1.3.2 of the WordPress Editorial Calendar and we are now showing the full content of the post in the Quick Edit dialog and not losing any data.

The new version of the calendar has also added extra unit tests to make sure this never happens again.

We hope you give the calendar another chance. We’re trying to live up to all the great press we’ve received.

Thank you,
Zack

Shona and I discussed this issue offline and it turned out to be a conflict between the Editorial Calendar and LiveFyre. LiveFyre was able to resolve this issue with a very fast fix and everything is working now.

Thanks,
Zack

Thank you for using the Editorial Calendar. I’m sorry you’re having trouble with it. Has version 1.3.1 ever worked for you? Have you installed any other new plugins lately?

When you see the problem are there any errors on your JavaScript console?

Thanks for helping me track down this issue.

Cheers,
Zack

The calendar doesn’t have any data by itself. It just edits the posts WordPress uses. For this reason uninstalling the calendar won’t change anything.

If you want to edit or delete published posts you need to find the post you want to edit in the standard WordPress posts menu. Then you can edit it there. You can also access the standard WordPress edit dialog from the calendar by clicking the edit link that appears under a post when you hover your mouse over it.

Good luck,
Zack

Hello Vekica,

I’m a little confused by your latest post. Are you still having a problem? If so, what version of Chrome are you using and what operating system are you on?

Thanks,
Zack

Thank you for giving me access to your blog. I was able to log in and see the issue. There is a bug in the calendar in version 1.3 which will cause it to break on WordPress 2.9.X. This is caused by the support we added for custom post types not degrading gracefully when custom post types aren’t available. This problem doesn’t happen in WordPress 3.0 or higher because custom post types are available.

I have release Editorial Calendar version 1.3.1 to fix this issue. Please let me know if you see any other issues.

Thanks,
Zack

This error indicates that the data about your posts was sent to the browser, but there was an error when we tried to parse it. Is there any chance I can log into your blog and try this out?

Please contact me at [email protected] with more details.

Thanks,
Zack

Thank you for trying using the Editorial Calendar. I’m sorry you’re seeing and issue with it.

What version of Chrome are you using and what version of WordPress? Are there any errors on the Chrome JavaScript console? Does that calendar grid show up and just not have any posts, or is there nothing at all? Have you recently installed any other new plugins?

Thanks,
Zack

The red rectangle is normal. One of the tests is testing what happens if you edit a post at the same time as someone else. In that case you get the error you saw.

It looks like all the tests have passed, but I have no idea why running those tests would fix this issue. You don’t see any issues with Chrome now, right?

It looks like the dev version of Chrome is a bit ahead of the stable release.

I just tried this using Chrome 8.0.552.224 on Windows XP and didn’t see any issues.

There are two more things to try.

The Editorial Calendar comes with a set of unit tests. You can access them by adding the parameter qunit=true to the end of the URL for the calendar. If your normal URL for the calendar is:

https://www.zackgrossbart.com/extras/trunk/wp-admin/edit.php?page=cal

Then the unit test URL is:

https://www.zackgrossbart.com/extras/trunk/wp-admin/edit.php?page=cal&qunit=true

All you need to do is access this page and the unit tests will show up below the calendar. You’ll see the calendar jump around while the tests run. They should take less than 30 seconds. If you could run these tests and see if they all pass that would help us diagnose the problem.

The second place to look is the JavaScript console. If you click on the little wrench and select Tools > JavaScript console a new window will pop up. On the bottom of that window there will be a console. Look for errors in there and let me know what you find.

Thank you very much for helping me debug this issue.

Best,
Zack

Thank you for using the Editorial Calendar. I’m sorry you’re seeing this issue.

I’ve tested the latest version of the calendar using Chrome 10.0.612.3 dev on Windows 7 and everything is working well for me. What version of Chrome are you using and what operating system?

You can find your Chrome version by clicking on the little wrench and selecting About Google Chrome.

Thank you,
Zack