posting drafts with WP 2.7 and livepress 2.1.8

Turante / livepress

Automatically exported from code.google.com/p/livepress

1 stars 0 forks source link

posting drafts with WP 2.7 and livepress 2.1.8 #44

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Install Wordpress 2.7 and livepress 2.1.8
2. Start writing a post in Wordpress, and save it as a draft.
3. That draft will be posted to Livejournal, even though you haven't
"published" the post yet in Wordpress.

Expected result would be that the draft is not cross-posted to Livejournal
until it is "published" in Wordpress.

Other people have been having this problem, see
http://groups.google.com/group/livepressplugin/browse_thread/thread/611ef4fe4a1c
a98d

Original issue reported on code.google.com by skyfal...@gmail.com on 22 Jan 2009 at 6:41

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 29 May 2009 at 3:48

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 29 May 2009 at 4:18

Added labels: Milestone-Release2.1.9

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 29 May 2009 at 4:18

Changed state: Ready

GoogleCodeExporter commented 9 years ago

I have been having this same issue as well and am just about ready to uninstall 
L+P
because of the headaches it creates. I usually write a rough draft in WP that I 
go
back and clean up before posting. Unfortunately, with L+P, I keep finding my 
drafts
posted to LJ and must manually delete them (unfortunately, this means anyone
subscribed to my journal's RSS feed gets the draft).

Original comment by grey...@gmail.com on 11 Aug 2009 at 10:28

GoogleCodeExporter commented 9 years ago


The latest version of LivePress (2.1.9) corrects this problem.  Are you sure 
you've
got 2.1.9 installed?

thanks!
-Tania

Original comment by tania%digsite.net@gtempaccount.com on 12 Aug 2009 at 12:54

GoogleCodeExporter commented 9 years ago

Definitely v2.1.9. Is there an option that needs to be set or changed if you've
upgraded from a prior version? (Also, I'm running WP v2.8.3)

Original comment by grey...@gmail.com on 20 Aug 2009 at 8:18

GoogleCodeExporter commented 9 years ago

Confirmed this is broken in the current version.

Original comment by tania%digsite.net@gtempaccount.com on 16 Mar 2010 at 6:39

Changed state: Accepted
Added labels: Milestone-Release2.1.12
Removed labels: Milestone-Release2.1.9

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 19 Mar 2010 at 12:41

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 19 Mar 2010 at 3:20

GoogleCodeExporter commented 9 years ago

this is fixed and will be released in 2.1.12 this weekend.

-T

Original comment by tania%digsite.net@gtempaccount.com on 19 Mar 2010 at 3:35

Changed state: Ready

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 20 Mar 2010 at 12:49

Added labels: Milestone-Release2.2.0
Removed labels: Milestone-Release2.1.12

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 23 Mar 2010 at 1:10

Changed state: Released

GoogleCodeExporter commented 9 years ago

Original comment by tania%digsite.net@gtempaccount.com on 26 Mar 2010 at 7:24

Changed state: Verified