search

Turante / ljxp

Automatically exported from code.google.com/p/ljxp
0 stars 0 forks source link

Error crossposting all wordpress entries #84

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I entered LJ username and password
2. Rest of the settings set to default
3. Click on the "Update options and crosspost all wordpress entries"
4. Got an error that says: "Something went wrong - 302 : Client error:
Can't edit post from requested journal"

What is the expected output? What do you see instead?

What version of the plugin are you using? What version of WordPress?
plugin version: 2.0.5
wordpress version: Version 2.5.1

Please provide any additional information below.

Original issue reported on code.google.com by tricia....@gmail.com on 13 Jul 2008 at 2:24

GoogleCodeExporter commented 9 years ago 
almost the same situation, but the error is 
Something went wrong - 312 : Client error: Not allowed to add tags to entries 
in 
this journal

Original comment by gadget.s...@gmail.com on 18 Jul 2008 at 8:20

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have exactly the same problem: Something went wrong - 302 : Client error:
Can't edit post from requested journal
WP version 2.6.2

Original comment by shubi...@gmail.com on 12 Sep 2008 at 12:08

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Comment 4  by doug.munsinger, Today (moments ago)

I ran into this deleting posts in wordpress AFTER having already removed them 
from
livejournal

"something went wrong - 302 : Client error: Can't edit post from requested 
journal"

wordpress version 2.7.1, plugin version LiveJournal Crossposter Remix 2.1.

Disabling the plugin, deleting the posts and then reenabling the plugin worked 
to
remove the posts.

Original comment by damgoode...@gmail.com on 16 Apr 2009 at 12:04

GoogleCodeExporter commented 9 years ago 
Issue 104 has been merged into this issue.

Original comment by st...@sillybean.net on 29 Jul 2011 at 3:30

GoogleCodeExporter commented 9 years ago

Original comment by st...@sillybean.net on 29 Jul 2011 at 3:30

GoogleCodeExporter commented 9 years ago 
I'm pretty sure this is related to issue #31 
(http://code.google.com/p/ljxp/issues/detail?id=31), and it happens because old 
versions of the plugin would store more than one LJID in the custom fields for 
each WP post. In 2.1+, that field is unique. I don't think that'll solve the 
problem for the older posts, but at least it shouldn't happen in the future.

Original comment by st...@sillybean.net on 31 Jul 2011 at 9:18