WordPress.org

1. stonegauge
   Member
   Posted 3 years ago #

   Hey All --

   I'm posting here as I have already posted on the plugin's page (http://noumenon.roderickrussell.com/myspace-crossposter-v2-released) and haven't gotten a reply yet about the problem. I'm hoping we have people utilizing the plugin here with some tech know-how that might shed light on the issue:

   OK, I’m having consistent issues with this on two sites I utilize it. On one site I use the cross poster for, I get the following error (and note the repetition of the error message):

   sorry but an error has occured, please check your user name and password. If you are sure this is correct this may be due to myspace, please try again later. if you continue to recieve this error please contact the developers with the following information : your name and email, what function you were attempting to use, page that error occured.We’re sorry but an error has occured, please check your user name and password. If you are sure this is correct this may be due to myspace, please try again later. if you continue to recieve this error please contact the developers with the following information : your name and email, what function you were attempting to use, page that error occured.We’re sorry but an error has occured, please check your user name and password. If you are sure this is correct this may be due to myspace, please try again later. if you continue to recieve this error please contact the developers with the following information : your name and email, what function you were attempting to use, page that error occured.
   Warning: Cannot modify header information - headers already sent by (output started at /home/(private)/html/wp-content/plugins/myspacecrossposter_v2_0a.php:236) in /home/(private)/html/wp-includes/pluggable.php on line 770

   BUT the posts actually go through (title only, not the full text posting). So it works, but it doesn’t?

   On the second site I utilize this, I get the same error but without the 3x repetition of the error message before an error code shows up. No cross posting occurs in this instance. I'm also using title only (but, when I first utilized the plugin, I had used the full body posting. It was the only time the cross-post worked).

   can anyone shed light on this? It's not a password issue on the myspace end and I have listed all my DB information correctly from my WordPress end.

   Thanks.

2. RandomRage
   Member
   Posted 3 years ago #

   Yeah...I just noticed this myself. I think 2.6 killed MySpace Crossposter. Don't know if the author is aware (he doesn't have any posts about it on his blog). Anyone with coding experience know how to get it up and running? Anyone successfully running it in 2.6?

3. stonegauge
   Member
   Posted 3 years ago #

   I actually got my personal blog to crosspost to Myspace -- just had to re-enter all my data on the settings. BUT I get that error message (x3 like the above example I posted). I can live with that... but yeah, this has to be tweaked and repaired and I don't know PHP well enough to find the flaw and fix it.

4. stonegauge
   Member
   Posted 3 years ago #

   OK, another interesting bug: I did some editing of old old OLD posts today on my personal blog (after running the Broken Link checker plugin) and this ended up forcing a reset of the Myspace plugin. I didn't notice it until I put up a new post this evening

5. Dgold
   Member
   Posted 3 years ago #

   Took me quite a bit of testing, unfortunately, to realize that: yep, Myspace Crossposter breaks the Write Post submission in WP 2.6

6. funwithtrout
   Member
   Posted 3 years ago #

   Ok, so this isn't pretty. It's only a work around for the error messages. I have not tested it with posting the full posts, only the notifications.

   So, if you want to get rid of the error messages, seeing as the notify works even with them, just comment out the error checking in the myspacecrossposter_v2_0a.php file as shown bellow:

   curl_setopt($this->ch, CURLOPT_URL,$newLoc."".$this->token);
   		$this->page = curl_exec($this->ch);
   		//check for errors
   //		if($this->checkErrors()){
   		//if error try again
   //		$this->page = curl_exec($this->ch);
   //		}
   		//check onelast time for errors before displaying error msg
   //		$this->checkErrors();
   
   //		if($this->errors){
   //		echo $this->stdError;
   //		$this->myHistory=NULL;
   //		curl_setopt($this->ch, CURLOPT_POST, 0);
   //		}else{
   		$this->myHistory[]=$newLoc."".$this->token;
   		curl_setopt($this->ch, CURLOPT_POST, 0);
   //		}
   		}

   If you are having trouble, you start commenting out on line 228 and finish on line 242 (well, skipping lines 240 and 241).

   I make no promises that this won't mess something else up, only that it works on my install, and has been for a little bit now. Please edit at your own risk.

   I hope this helps out, at least until the author decides to update.

7. angelic007
   Member
   Posted 3 years ago #

   I had to disable myspace-crossposter with WordPress update to 2.6.
   It caused a 500 Internal server error every time I tried to edit and save an old post.

   I believe the problem to be in post revisions, but I really don't want to dip into code.

   I'll just let it disabled, fu** MySpace a closed and useless site.

8. stonegauge
   Member
   Posted 3 years ago #

   Angelic, are you SURE you had the DB / settings right? I had to input them fresh in order to get the crossposter to work properly. The plugin is buggy as has been mentioned.

   I want to note on NOTIFICATION blog posting:

   If you want to EDIT the message that gets displayed on new blog posts, you should go to line 519 in the cross poster. It is mostly HTML code that can be edited. I ended up removing the XX-large text that shows up at the bottom of each post and I'm considering other revisions.

   If I could further tweak, I'd change the links to permalinks. Right now they point to generic links on your blog (post id's).

   And if you edit these messages yourself as well, BE CAREFUL! One missing backslash and everything goes kablooie.

Topic Closed

This topic has been closed to new replies.