tinuviel

Hi, I just installed this plugin and I keep getting this error, depending on my action.
When I click on “Advanced Editing” I get this (nothing else shows up afterwards):
Warning: Cannot modify header information – headers already sent by (output started at /home/intrinz/public_html/sulwyn/wp-content/plugins/ImageManager.php:180) in /home/intrinz/public_html/sulwyn/wp-admin/post.php on line 148
When I click on “Delete post” I get this (my LJ plugin shows up afterwards but that’s all):
Warning: Cannot modify header information – headers already sent by (output started at /home/intrinz/public_html/sulwyn/wp-content/plugins/ImageManager.php:180) in /home/intrinz/public_html/sulwyn/wp-admin/post.php on line 476
Also, when I add a photo, all it does is add a text link, and then takes me to an internal server error.
I have no idea what’s going on ?? Please help?

So you don’t have any theories as to why my post.php is displaying those errors?
Thanks anyway unteins, I really appreciate all the work you’ve done on this.

That’s odd, I looked in that file and it calls everything else EXCEPT what I would assume would be template-functions-calendar.php, and I don’t have a file called that either.
Know where I can get this?

Thanks for your quick reply, unteins.
I have keywords for all my userpics and I have friends groups set up in LJ. My $journals array is set up properly as directed:
$journals[‘trancelife’][‘password’] = ‘pw_is_here’;
(trancelife is my username and pw_is_here is where I put my password). I don’t know what could be wrong.

Unteins – but no, my dropdown list is empty, and a few posts back you mentioned having to enter keyword names into the LJ-userpic config file or something so that WP recognizes them and places them IN the dropdown list… maybe the guy asking the question said that… either way, where do I put those keywords? Cos I think I have the one with support, I downloaded every update you posted, but my list is still empty. Or do you mean the LJ server actually places the keywords into my WP post file for me and I don’t have to customize anything… in which case I guess I don’t have the one that supports it, though I am getting that same “Error on line 50” error message as the previous guy who asked about this…
oh boy, that was confusing. Sorry!

Unteins – Ah, now I get it. Thanks for the clarification! Can you also add support for lj-cut tags with text, or is that also too much?
“You will have to use whatever options WordPress offers to hide the plugin on WordPress though.” -> I’m not really sure what you meant by this…
Also, what about the userpics? How/where do I put my keywords for those in the WP config files?

Also, forgot to ask if there’s a way to post friends-only, only? Or to a specific friends group?
Thanks ??

Am I missing something here… where does it say how/where to add code words for your userpics?
Also, when I posted an entry to my blog & synched with LJ, the [ ] brackets weren’t converted to < > brackets and thus I was left with the full tag on LJ saying [lj user= “trancelife”], yet it linked properly from my blog.
Otherwise, the moods and music are working fine…

Thanks, unteins, that helped.
However, I’m still having problems. Only the Lj USER tag works, not LJ-Cut. This is why, I think – I originally installed your hack posted at https://www.ads-software.com/support/10/5273, the one on Wiki. I removed what I’d added, for that particular hack, but then none of the tags worked.
When I log into my LJ to view the code that WP created, I see the LJ cut tags are coded as:
<\>testing<\>
that’s also what shows up in my LJ, instead of a cut. However, when viewing my WP site, I get a proper “Read more cut” as expected.
Can you help or do I need to describe the problem in more detail?

return $text;
}
add_filter(‘the_content’, ‘parse_lj_tags’);
add_filter(‘comment_text’, ‘parse_lj_tags’);
Lines 46-50, as requested. Thanks!! ??

Shweet. This seems easier than the LJ-user tags hack someone already made… there’s all these instructions for it and mine didn’t even work after going through them. I’m going to try yours out and see if it works instead.
Just one thing though, the plugins folder is called wp-includes, right? I don’t have one called plugins…

Never mind the above post. I’d downlaoded the patched xmlrp file, but for some reason my browser had saved it as an HTML file instead of PHP and so had inserted loads of font tags and such.

I inserted the my-hacks.php part of LJ Autoupdate into post.php, and relinked the require_once (“../wp-includes/class-xmlrpc.php”); line so that it goes to the right folder.
However, now I’m getting the following error and I cannot for the life of me figure out why:
Fatal error: Cannot instantiate non-existent class: xmlrpc_client in /[servername]/wp-admin/post.php on line 59
The line it’s referring to is:
$client = new xmlrpc_client(“/interface/xmlrpc”, “www.livejournal.com”, 80);
There’s nothing relatively linked from there, from what I can tell… I mean, “interface/xmlrpc” mustn’t be on my server cos I don’t have any folders anywhere named that. So it’s ony LJ right? The problem is with xmlrpc_client, but I don’t know why… help please?

Hm. I didn’t have a hack_file row, so I inserted it copying the same attributes as option_can_override (since it’s also a N/Y option). I uploaded that, and check WP Miscellaneous options, and the Use legacy my-hacks.php file support still won’t stay checked after saving.
The problem is that when I try to use LJ-auto update, it tells me Fatal error: Call to undefined function: ljautoupdate() in /[servername]/post.php on line 126. So I’m guessing it’s not reading the hack file… so I’ll do what Davidchait suggested and see if that works. *hopes she doesn’t screw up the post.php file*!!

Davidchait, should I do that? Do I just put it anywhere inside the index.php file? Since for some reason my checkbox next to Use legacy my-hacks.php file support won’t stay checked after I press “update options” – anyone else having this trouble in WP 1.2?
(reposting this here since the other thread I used doesn’t seem to be visible from the main bulletin page).