<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:media="http://search.yahoo.com/mrss/"
> <channel><title>Comments on: Edit Flow Project: Stage 1 beta release</title> <atom:link href="http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/feed/" rel="self" type="application/rss+xml" /><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/</link> <description>Building a Better Technical Ecosystem for Student News Organizations</description> <lastBuildDate>Sat, 27 Feb 2010 09:51:00 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Mo Jangda</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2390</link> <dc:creator>Mo Jangda</dc:creator> <pubDate>Thu, 03 Dec 2009 02:09:08 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2390</guid> <description>@coloradoouting: Glad to hear it worked! And the metabox issue is a known bug but we&#039;ll hopefully have it fixed for the next release.Thanks for using Edit Flow!</description> <content:encoded><![CDATA[<p>@coloradoouting: Glad to hear it worked! And the metabox issue is a known bug but we&#8217;ll hopefully have it fixed for the next release.</p><p>Thanks for using Edit Flow!</p> ]]></content:encoded> </item> <item><title>By: coloradoouting</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2389</link> <dc:creator>coloradoouting</dc:creator> <pubDate>Thu, 03 Dec 2009 02:05:08 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2389</guid> <description>Hey Mo,Thanks for the suggestion! It enabled the metabox for pages and everything seems to be working fine. One thing I did notice since first installing Edit Flow, I&#039;m unable to open/close the other metaboxes in pages, even after applying your function suggestion.The metaboxes work fine in posts, in fact, if I go into any post and open the metabox that I want, it will then be open in pages?? Doable, but not very convenient..haha!</description> <content:encoded><![CDATA[<p>Hey Mo,</p><p>Thanks for the suggestion! It enabled the metabox for pages and everything seems to be working fine. One thing I did notice since first installing Edit Flow, I&#8217;m unable to open/close the other metaboxes in pages, even after applying your function suggestion.</p><p>The metaboxes work fine in posts, in fact, if I go into any post and open the metabox that I want, it will then be open in pages?? Doable, but not very convenient..haha!</p> ]]></content:encoded> </item> <item><title>By: Mo Jangda</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2381</link> <dc:creator>Mo Jangda</dc:creator> <pubDate>Fri, 27 Nov 2009 04:56:34 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2381</guid> <description>Hi coloradoouting,Glad to hear the Edit Flow will come in handy with your workflow. Looks like there was a bit of an oversight on our part and we forgot to enable the Edit Flow metabox for Pages. We&#039;ll try to see if we can add it in with the next version.Until then, if you&#039;re really interested in enabling it for pages try the following: Locate the &lt;strong&gt;add_post_meta_box&lt;/strong&gt; function in edit-flow/php/post.php and replace it completely with &lt;a href=&quot;http://pastebin.com/f41245ca&quot; rel=&quot;nofollow&quot;&gt;this function&lt;/a&gt;. That should work, though we haven&#039;t tested it, so be warned that there may be bugs.</description> <content:encoded><![CDATA[<p>Hi coloradoouting,</p><p>Glad to hear the Edit Flow will come in handy with your workflow. Looks like there was a bit of an oversight on our part and we forgot to enable the Edit Flow metabox for Pages. We&#8217;ll try to see if we can add it in with the next version.</p><p>Until then, if you&#8217;re really interested in enabling it for pages try the following: Locate the <strong>add_post_meta_box</strong> function in edit-flow/php/post.php and replace it completely with <a
href="http://pastebin.com/f41245ca" rel="nofollow">this function</a>. That should work, though we haven&#8217;t tested it, so be warned that there may be bugs.</p> ]]></content:encoded> </item> <item><title>By: coloradoouting</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2380</link> <dc:creator>coloradoouting</dc:creator> <pubDate>Thu, 26 Nov 2009 19:47:06 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2380</guid> <description>This plug-in will really improve our post and page work flow! I have come across one issue that I&#039;m not exactly sure how to resolve. I&#039;m hoping that you can provide me with some ideas on how to proceed. We are currently using WP version 2.8.5.Everything appears to work perfectly in the post area, however, the Edit Flow widget is not appearing in the Page screens. The other issue I noticed, I am unable to open any of the existing widgets in the page area if they are closed.I noticed in the plug-ins edit area the edit-flow/php/post.php file that appears to me to be establishing and controlling the Edit Flow widget in the Post area. Do I need a similar file to handle those items in a page? Or is there a statement missing in my templates page.php that I need to include?Any assistance you could provide would be greatly appreciated!</description> <content:encoded><![CDATA[<p>This plug-in will really improve our post and page work flow! I have come across one issue that I&#8217;m not exactly sure how to resolve. I&#8217;m hoping that you can provide me with some ideas on how to proceed. We are currently using WP version 2.8.5.</p><p>Everything appears to work perfectly in the post area, however, the Edit Flow widget is not appearing in the Page screens. The other issue I noticed, I am unable to open any of the existing widgets in the page area if they are closed.</p><p>I noticed in the plug-ins edit area the edit-flow/php/post.php file that appears to me to be establishing and controlling the Edit Flow widget in the Post area. Do I need a similar file to handle those items in a page? Or is there a statement missing in my templates page.php that I need to include?</p><p>Any assistance you could provide would be greatly appreciated!</p> ]]></content:encoded> </item> <item><title>By: Noel Madali</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2162</link> <dc:creator>Noel Madali</dc:creator> <pubDate>Thu, 10 Sep 2009 07:44:15 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2162</guid> <description>I have gotten it to work with WordPress MU version 2.8.4a and BuddyPress. I am not sure what Jennifer did, but it does what the page shows in the Edit Posts area.</description> <content:encoded><![CDATA[<p>I have gotten it to work with WordPress MU version 2.8.4a and BuddyPress. I am not sure what Jennifer did, but it does what the page shows in the Edit Posts area.</p> ]]></content:encoded> </item> <item><title>By: Jennifer</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2011</link> <dc:creator>Jennifer</dc:creator> <pubDate>Wed, 22 Jul 2009 15:07:37 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2011</guid> <description>Thanks, Daniel. If you need testers at any stage, let me know.</description> <content:encoded><![CDATA[<p>Thanks, Daniel. If you need testers at any stage, let me know.</p> ]]></content:encoded> </item> <item><title>By: Daniel Bachhuber</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2001</link> <dc:creator>Daniel Bachhuber</dc:creator> <pubDate>Mon, 13 Jul 2009 20:20:59 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2001</guid> <description>We haven&#039;t actually tested it or confirmed that it works in WordPress MU yet, although getting it to do so is obviously preferable. We&#039;re still adding features and I&#039;ll make sure that we get it to work in MU in a release for the near future.</description> <content:encoded><![CDATA[<p>We haven&#8217;t actually tested it or confirmed that it works in WordPress MU yet, although getting it to do so is obviously preferable. We&#8217;re still adding features and I&#8217;ll make sure that we get it to work in MU in a release for the near future.</p> ]]></content:encoded> </item> <item><title>By: Jennifer</title><link>http://www.copress.org/2009/06/16/edit-flow-stage-1-beta/comment-page-1/#comment-2000</link> <dc:creator>Jennifer</dc:creator> <pubDate>Mon, 13 Jul 2009 20:03:03 +0000</pubDate> <guid
isPermaLink="false">http://www.copress.org/?p=2081#comment-2000</guid> <description>I was excited to see this plug-in. It&#039;s supposed to do exactly what I need to do. my only problem is that I can&#039;t get it to work with WP MU. Any ideas?I will be using this on stand-alone WP installations, but I&#039;d love to also use it on the sites that are running out of WP MU.</description> <content:encoded><![CDATA[<p>I was excited to see this plug-in. It&#8217;s supposed to do exactly what I need to do. my only problem is that I can&#8217;t get it to work with WP MU. Any ideas?</p><p>I will be using this on stand-alone WP installations, but I&#8217;d love to also use it on the sites that are running out of WP MU.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 5/20 queries in 0.010 seconds using disk

Served from: localhost.localdomain @ 2010-03-11 23:21:37 -->