FaceBook "Like Button" being killed by VBSEO. Relevant Replacements?

The new "Like Button" functionality in 4.0.4 is not playing nice with VBSEO. I think the problem is in the way Relevant Replacements are done, that is, the new code is being replaced by the relevant replacements. I think. I was able to edit forumdisplay template and they are now back in the forums (though not right-justified as I would prefer), but the blogs are another story. Not sure why the Like button is not working in blogs--all the correct code is there...and there are no RR's in blogs anyways. (Though there should be--is this a planned feature?)

VB forums blamed it on VBSEO, so here I am again.

Well apparently it is not RR's. According to "Pogo" @ VB Germany:

To explain why this is a vBSEO problem:

When you open a blog entry in vBulletin it is done via entry.php so THIS_SCRIPT is set to entry.
When you open a blog entry in vBulletin with vBSEO it is done via blog.php so THIS_SCRIPT is set to blog.

vBulletin shows the like button only if THIS_SRIPT is set to entry.

See includes/functions_facebook.php in function construct_fblikebutton().

Anyone know how to fix this?

Hello,

We are currently looking into the cause and a possible fix on this.

The "publish to FaceBook" functionality is not working either...

All, FYI,
I had 351 upgrade a few hours ago and that fixed my like button on blogs. Thanks
understood et al, prior to upgrade 351, the publish to facebook function on blogs worked for me. Why there is a difference is beyond me, but thought this info might help?

i have upgraded my vbseo to 3.5.1 yesterday and it still does not work. any suggestion?

Originally Posted by understated

To explain why this is a vBSEO problem:

When you open a blog entry in vBulletin it is done via entry.php so THIS_SCRIPT is set to entry.
When you open a blog entry in vBulletin with vBSEO it is done via blog.php so THIS_SCRIPT is set to blog.

vBulletin shows the like button only if THIS_SRIPT is set to entry.

See includes/functions_facebook.php in function construct_fblikebutton().

Well apparently it is not RR's. According to "Pogo" @ VB Germany:

Originally Posted by Your Brand

All, FYI,
I had 351 upgrade a few hours ago and that fixed my like button on blogs. Thanks
understood et al, prior to upgrade 351, the publish to facebook function on blogs worked for me. Why there is a difference is beyond me, but thought this info might help?

Im also using vbseo 3.5.1 + vb 4.0.4 PL1 , and all the facebook services are hampered... in my case ...

Im using custom urls for articles and blogs and if I am browsing custom urls of subdomain type urls then...
If I am connected to forum via facebook login (on the top right) and browse to a custom url like http://articles.dstreetdirect.com, then Im logged out of facebook for those urls .... and if I come back to normal url like http://www.dstreetdirect.com I am be logged in again....

If I try to login to facebook via any custom url page say http://blogs.dstreetdirect.com and click on facebook button , u will be shown an error

The Facebook Connect cross-domain receiver URL (http://static.ak.fbcdn.net/connect/x...xRESULTTOKENxx) must have the application's Connect URL (http://www.dstreetdirect.com/) as a prefix. You can configure the Connect URL in the Application Settings Editor.

Eureka!!!!!!!
I sorted out (at least my problem of custom urls)... just visit the application settings page on your facebook application , from the left click Connect and set the Base Domain as yoursite.com and u r done... in my case I set it to dstreetdirect.com and I can use facebook login on blog.dstreetdirect.com or any other custom urls....

Any news regarding this? vb4.0.4 PL1 + vbSEO 3.5.1 -> No FB like buttons @ Blogs

The fix in vBSEO will be released within next vBSEO version but for temporary fix in functions_vbseo_url.php

Find

PHP Code:

if ($vbseo_arr)
{
$_vsself = ('blog.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr['blog_id']);
} 


Replace With

PHP Code:

if ($vbseo_arr)
{
$_vsself = ('entry.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr['blog_id']);
} 


Find

PHP Code:

if ($vbseo_arr27)
{
$_vsself = ('blog.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr27['blog_id'] . '&page=' . $vbseo_arr27['page']);
} 


Replace With

PHP Code:

if ($vbseo_arr27)
{
$_vsself = ('entry.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr27['blog_id'] . '&page=' . $vbseo_arr27['page']);
} 


Find

PHP Code:

if ($vbseo_arr5)
{
$_vsself = ('blog.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr5['blog_id'] . '&goto=next');
}
else
if ($vbseo_arr6)
{
$_vsself = ('blog.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr6['blog_id'] . '&goto=prev');
} 


Replace With

PHP Code:

if ($vbseo_arr5)
{
$_vsself = ('entry.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr5['blog_id'] . '&goto=next');
}
else
if ($vbseo_arr6)
{
$_vsself = ('entry.' . VBSEO_VB_EXT . '?b=' . $vbseo_arr6['blog_id'] . '&goto=prev');
} 


thanks

Awesome, thanks!

Works good; thanks Mert!

yeah, this fixes the trouble with the blogs ... but unfortunately the suite is too much bugged ... :S anyway thanks Mert