Hi @sunder,

Linking new accounts using the Twitter account is broken right now. So, there is a patch that may work but please tell how used are you to hack the code (detailed instructions will be provided).

Thanks.

I can edit the php, if that is what you are asking.

Is it broken in all versions? I thought I used the stable release 5.22.

I was using an 0.91, but it would not upgrade so I installed 5.2.2 from scratch. Is there any other known help sites for this?

I cant get any info on my other external feed burner problem post. Cant get to feedburner.

here are the url's I entered in the advance tab.

http://feeds.feedburner.com/underwoodlaw/VSxY

http://feeds.feedburner.com/underwoodlaw/nlOQ

I can add a url link to the side bar and feedburner loads, why does it not load when I click the post link under rss.

I guess if you are not a serious php coder you are not going to find a way to fix stuff.

I spent 4 hours messing with the twitter plugin only to find out it was broken and not me that messed it up.

Did I miss the post or sticky that said that, not likely, it was just not there.

@sunder let's keep this post only for the Twitter plugin issue.

I will share a personal solution that I applied to deal with it, so it's not official, maybe not elegant, but it works. Note: all the references to files and line numbers are based on version 5.2.2.

1. Go to inc/plugins/_plugin.class.php, find the function get_htsrv_url and replace all its code (lines 2766 to 2785) with this new one:

	function get_htsrv_url( $method, $params = array(), $glue = '&', $abs = false, $sess_params = false )
	{
		global $htsrv_url, $htsrv_url_sensitive;
		global $ReqHost, $Blog;

		$base = substr($ReqHost, 0, 6) == 'https:' ? $htsrv_url_sensitive : $htsrv_url;

		if( ! $abs && strpos( $base, $ReqHost ) === 0 )
		{ // cut off $ReqHost if the resulting URL starts with it:
			$base = substr($base, strlen($ReqHost));
		}

		$r = $base.'call_plugin.php?plugin_ID='.$this->ID.$glue.'method='.$method;
		if( !empty( $params ) )
		{
			if ( $sess_params )
			{
				global $Session;
				
				$Session->delete( 'params' );
				$Session->set( 'params', serialize( $params ) );
				$Session->dbsave();
			}
			else
			{
				$r .= $glue.'params='.rawurlencode(serialize( $params ));
			}
		}

		return $r;
	}

2. Go to htsrv/call_plugin.php and replace all the content of lines 52 to 59 with this code:

if( is_null($params) && ! $Session->get('params') )
{ // Default:
	$params = array();
}
else
{ // params given. This may result in "false", but this means that unserializing failed.
	if( is_null($params) ) 
	{
		$params = $Session->get('params');
		$Session->delete('params');
	}
	
	$params = @unserialize($params);
}

3. Go to plugins/twitter_plugin/_twitter.plugin.php and replace the line 255 with this:

$callback = $this->get_htsrv_url( 'twitter_callback', array( 'target_type' => $target_type, 'target_id' => $target_id ), '&', true, true );

4. Go to the plugins settings page in the backend and link your twitter account as usual.

I recommend to make a backup of each one of the files that you will modify, that way you can easily roll-back these changes any time you want. Actually, you can roll them back after having connected all the twitter accounts to your users/blogs, because the issue doesn't affect posting to twitter once the account is properly linked.

I guess this issue will be solved soon and included in a future release, so at that moment, these instructions won't be necessary anymore.

Regards!

Thank you worked great. I am now linked

Important: the hack detailed above is not necessary anymore, since a fix for this bug has been included in the version 6.5.0 release (http://b2evolution.net/downloads/6-5-0-stable).

I'm glad I found this post, as I've just discovered the same issue myself with linking to Twitter. I need to move to 6.5.0, but need to do a few things first before I go there. Perhaps the hack might be an option on the meantime - I'm currently running 5.2.2 on my live site..

@chris_of_arabia: give the hack a try and tell us how is it going.

As I said before, this issue is already fixed in version 6.5.0, so you won't need to do anything else after upgrading.