Comments on: Ecto/WordPress Woes http://www.markevanstech.com/2007/08/03/ectowordpress-woes/ Thoughts on Startups, Entrepreneurs and the Web Thu, 09 Feb 2012 17:25:18 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Mark Evans http://www.markevanstech.com/2007/08/03/ectowordpress-woes/comment-page-1/#comment-6546 Mark Evans Mon, 06 Aug 2007 11:38:33 +0000 http://markevanstech.com/2007/08/03/test/#comment-6546 Shaun, Thanks for the help. It took awhile but I figured out the problem: it was a plug-in called SidePost that I recently installed. Once I deactivated it, the problem disappeared. Lesson learned! Shaun,
Thanks for the help. It took awhile but I figured out the problem: it was a plug-in called SidePost that I recently installed. Once I deactivated it, the problem disappeared. Lesson learned!

]]> By: Shaun Rotman http://www.markevanstech.com/2007/08/03/ectowordpress-woes/comment-page-1/#comment-6526 Shaun Rotman Fri, 03 Aug 2007 14:06:51 +0000 http://markevanstech.com/2007/08/03/test/#comment-6526 Two things you might want to try: 1. Upgrade your version of Wordpress. If you're not using the latest version you may not be taking advantage of bugfixes to the XML-RPC function that Ecto interfaces with. 2. If you happen to be future-posting, and it's showing up as 10:07am, you may want to try going into Options and disabling the UTC time code setup. Ecto overrides any Wordpress-based time settings with its own that gets uploaded when you make a post. Good luck! Two things you might want to try:

1. Upgrade your version of WordPress. If you’re not using the latest version you may not be taking advantage of bugfixes to the XML-RPC function that Ecto interfaces with.

2. If you happen to be future-posting, and it’s showing up as 10:07am, you may want to try going into Options and disabling the UTC time code setup. Ecto overrides any WordPress-based time settings with its own that gets uploaded when you make a post.

Good luck!

]]>