This same issue happened in 2.3.3.  I don't think the author is updating this
anymore.  The plugin is very touchy from my experiences.  I had issues with
deactivating it and reactivating it and making any changes within the options menu. 
So what I ended up doing was just never deactivating it when I updated to new
versions of WP.  Good luck.  I can vouch that the plugin does work in 2.5, but there
are various issues if you de/re-activating, or making changes.  I did all my changes
within phpmysqladmin.

Hi. Thanks for the message. I only start using WP myself now, so generally I'd 
prefer going in with WP 2.5 (once it is released as stable that is) ... I am working 
on theming with that in mind.

Still, I'll try to see if I can make it work well enough - any hints/tips on what to 
look for php wise? 

-C.

WP 2.5 (Release)
same issue. it won't activate at all with "Plugin could not be activated because it
triggered a fatal error." message. Did anyone solve it and can share the fix ?

I managed to activate it by commentig out this section:
if(version_compare($wp_version, "2.1", "<")) {
      require_once(ABSPATH . '/wp-includes/template-functions-links.php');
}
i've read that this file is no longer a part of worpress

Thanks to phazeman this plugin now works for me.

I just added two //  marks in front of the lines he specified and the plugin activated.

Thanks phazeman

Thank you soooo much for updating us on this. I don't know what I'd do without my LJ 
Crossposter. =D

(Or the pretty new 2.5 either)

Thank you so very much!!!  I manage blogs for 2 of my friends that use this plugin -
they will both be THRILLED that they haven't lost this functionality!

The weird thing is, even though I took out those few lines . . . when I wrote a new
entry, it gives me some fatal error again.  My blog entry shows up on my site, but it
will not crosspost to LJ.

I have a fix for 2.5!

Replace this...

if(version_compare($wp_version, "2.1", "<")) {
      require_once(ABSPATH . '/wp-includes/template-functions-links.php');
}

With this...

if(version_compare($wp_version, "2.1", "<")) {
      require_once(ABSPATH . '/wp-includes/link-template.php');
}

Oops, here's what you replace it with...

if(version_compare($wp_version, "2.3", "<")) {
	require_once(ABSPATH . '/wp-includes/link-template.php');
}

thanks for the fix works very well, has anyone had problems with stick post plugins?

i was having this problem too.  i made the fix and the plugin activated, but i'm
still having trouble.

when i try to publish an entry immediately, i get a "date out of order" error,
similar to the one LJ gives, but in wordpress.  when i publish a little into the
future, it just doesn't sync at all.  

i never used to have this problem when publishing.  anyone know what i'm doing wrong?

phazeman's instructions worked for me.

Neither fix has worked for me.  They both give me this error:

Fatal error: Cannot instantiate non-existent class: ixr_client [server info redacted]

Thank you so much...  This fix helped to fix the plug in for all of our blogs at
www.livingplush.com.  

LP Kisses and Hugs :-D

Thanks A lot, shellygrrl advice helped.

Thanks so much - I used Phazeman's fix of commenting out (adding the // to each line
of that code) and it worked!

Do we need to get someone else to take over maintenance responsibility for this code?

Well - there hasn't been any update/development in about a year ... so maybe, yes? 

I for once would love to see more features added (but am not a coder :) ) - like ... 
using WP tags rather than categories for LJ tags, possibility to select which 
journal/lj-community to post to, etc.

-C.

hmm.. getting some write_nested_categories() missing function error, whathat?

The plugin works with WP 2.5.1 as of version 2.0.5, hence it should work fine with 2.5

Not fixed! Changing LJXP settings results in
  "Something went wrong - 302 : Client error: Can't edit post from requested journal"

Slamlander, this is not an issue of this plugin's compatibility. If you consider this
a bug, please, open a separate ticket with detailed description of the problem.
Thank you for understanding.

Note for everyone else:
This ticket's status is closed, b/c the options are displayed correctly(which was the
problem described in the first post). Any other bug should be posted separately.

Thank you shellygrrl for the fix! It works!