[xeagle]

Originally Posted by Guardian Hope

Ticket ID 2957

Hopefully you all can figure out how to unlock vBSSO on Wordpress for me soon. I've been trying for two days; I even examined the database. For some reason Wordpress thinks it's linked and there's no "Unlink Platform" option. It's actually starting to hold up development and I have no idea how vBSSO is keeping its settings when the files were completely removed from the server at one point.

These lovely codes show up on the configuration page in Wordpress:

Warning: mcrypt_decrypt(): Size of key is too large for this algorithm in /home/fedcomma/public_html/phoenix/wp-content/plugins/vbsso/includes/sharedapi.php on line 331

Warning: mcrypt_decrypt(): Size of key is too large for this algorithm in /home/fedcomma/public_html/phoenix/wp-content/plugins/vbsso/includes/sharedapi.php on line 331

I tried to link it with vBulletin as a shot in the dark to try and unlink it afterwards but it won't link with vBulletin reporting:

Warning: mcrypt_encrypt(): Size of key is too large for this algorithm in ..../vbsso/includes/sharedapi.php on line 326

Warning: mcrypt_encrypt(): Size of key is too large for this algorithm in ..../vbsso/includes/sharedapi.php on line 326

Warning: mcrypt_encrypt(): Size of key is too large for this algorithm in ..../vbsso/includes/sharedapi.php on line 326

Warning: mcrypt_encrypt(): Size of key is too large for this algorithm in ..../vbsso/includes/sharedapi.php on line 326

Warning: mcrypt_encrypt(): Size of key is too large for this algorithm in ..../vbsso/includes/sharedapi.php on line 326

Warning: Illegal string offset 'product' in ..../vbsso/includes/functions_helper.php on line 162

And so Wordpress is totally locked out so I can shorten the key and actually link it.

Both are running the latest available vBSSO.

Thank you for providing us with the details. Our team is still investigating the root cause of this issue. We will inform you about it as soon as possible.