"Last Edited by..." duplicate Social Bookmarks

Hi there,

I upgraded to vBulletin 3.7.0 and I noticed that on posts containing "Last Edited by:" notices at the bottom of edited posts, a set of vbSEO Social Bookmarks appears, creating a duplicate appearance.

Example:
[Patch] Aeternium Engine 1.0.0 Beta 1 - Aelyria

Scroll to the bottom of my first post and you'd see.

Any thoughts?

Thanks!

Confirmed. This issue will be resolved in the next vBSEO build. Thank-you for reporting!

Originally Posted by Juan Muriente

Confirmed. This issue will be resolved in the next vBSEO build. Thank-you for reporting!

Great, thanks! Is there any work-around that I can put in to fix this issue in the meantime?

Do not edit your threads

Kidding....

No workaround?

I think to put your bookmarks in the LinkBack DHTML dropdown menu is like a workaround because this is the position I'm using and the Last edited notice doesnt duplicate anything

You should modify functions_vbseo_hook.php file.
FIND:

PHP Code:

$search_for = '".(($post[\'editlink\']'; 


replace with:

PHP Code:

$search_for = '".(($post[\'editlink\'])'; 


ok thanks for the tip

Originally Posted by Oleg Ignatiuk

You should modify functions_vbseo_hook.php file.
FIND:

PHP Code:

$search_for = '".(($post[\'editlink\']'; 


replace with:

PHP Code:

$search_for = '".(($post[\'editlink\'])'; 


Cool.
Is there anything else that needs to be modified for VB3.7?

Other modifications are related to new vB3.7 features that will be supported in the next vBSEO build.

Confirmed: Works Perfectly! I can't wait for the next build of vBSEO.

I cant find vbseo functions_vbseo_hook.php file ? Does it comes with vbSEO 3.1 ?
Additionaly my version is Zended so no file edit is possible.

It is only applied to vBSEO3.1.0 (and it's recommended to upgrade if you are still on an older version)

i fixed the same problem, thx.

But, why i saw this problem because i didnt have this problem on previously theme and vbulletin 3.6.8

When i upgraded to 3.7 beta4 and build a new theme, this problem has seen.

Just FYI,

the above code fixed the same issue I was having on VB3.70 RC1


Thanks,
Jason