vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 4.x Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=245)
-   -   Add-On Releases - vBSSO - vBulletin Single Sign-On (https://vborg.vbsupport.ru/showthread.php?t=270517)

audzilla 11-04-2013 03:45 AM

Hello!

Thanks for this plugin. I have it installed on vb 4.2.2 and Mediawiki 1.21.2 and on the surface it seems to work fine (it doesn't function smoothly with the Quick Account Swap mod, but since that's not a login action, that's not a surprise.)

However, when I have the forum in debug mode, I get the following error string when I try to enter the admincp:

Code:

Notice: Undefined variable: config in /home/[mysite]/public_html/forums/vbsso/vbootstrap.php on line 24
which completely prevents me from getting into the acp.

On the page itself I see the following:

Code:

Notice: Constant THIS_SCRIPT already defined in /home/[mysite]/public_html/forums/vbsso/vbsso.php on line 19

Notice: Undefined variable: config in /home/[mysite]/public_html/forums/vbsso/vbootstrap.php on line 24

These errors don't seem to impede the mod's function, but they do make it impossible to get to my ACP in debug mode, which is a problem. I can disable the mod to get back to the ACP, and then the errors just flicker by too fast to see when a page loads. Any advice?

Thank you all in advance for any help. :)

audzilla 11-05-2013 04:35 PM

Just a note that I submitted this as an issue at http://vbsso.com/report-an-issue/ and was sent a patched version the next day. Thank you very much!

dionak 11-14-2013 03:13 PM

Hello,

I hope someone can offer advice. We are using VBSSO with Wordpress on a production server, after testing it on a development server, and it works fine on both of those.

Now, we have copied that production server--database and all--over to a third server to set up a new staging server. When we copied it, the links between the two systems, vBulletin and Wordpress, were still pointing to the 'www' versions of the blog and forum. We changed the URLs of the system to start with 'staging', but we ended up Removing the link in the vBulletin VBSSO options panel, and deleting the 'vbsso' database entries in the wp_options table, because the links would not work to log in.

Now the problem: when we try to re-establish a connection between the staging forum and the staging Wordpress, we just get an error page, but the space after label 'Error:' was blank. (We know it's connecting, because we have the staging server under basic authentication, and if we don't put the correct username/password in the Connect a Platform panel, we get a "401 Authorization Required" error message in that spot.)

Even though it says there is an error, and no connection is listed on the vBulletin side of vBSSO, options for mapping our custom vB usergroups to Wordpress roles then appear in the Wordpress side settings for vBSSO, and vbsso entries are recreated in the wp_options table. We still can't login to Wordpress through the vBulletin link, either. (We can get to Wordpress admin by going directly to wp-login.php and using a pre-link admin account created in Wordpress.)

Any help would be greatly appreicated.

SirSteve 11-16-2013 02:15 PM

Does this work with vb CMS? I want to replace the CMS portion with WP and just use the vb Forums with it.

TiKu 11-16-2013 02:24 PM

Quote:

Originally Posted by SirSteve (Post 2461118)
Does this work with vb CMS? I want to replace the CMS portion with WP and just use the vb Forums with it.

We're running successfully a WP/vB combination: http://www.planet3dnow.de/cms/
It's Wordpress 3.7.1 for the front page and vBulletin 4.1.12 for the forum. We're using vBSSO successfully.

SirSteve 11-16-2013 02:45 PM

Nice. So then do I upload the files to the CMS (in our case it's root) instead of the forums dir (which is /forums) which is what the install docs state?

TiKu 11-16-2013 02:55 PM

As far as I remember I simply followed the install docs. Note that there is a separate vBSSO Wordpress plugin. So you install the vBSSO vB addon for the vB side and the vBSSO WP plugin for the Wordpress side and then you connect both platforms in the settings.

SirSteve 11-16-2013 03:55 PM

Well I read the docs as I had just the forums and not the CMS. I moved the files from the /forums into the root dir and everything is working. Thanks for the replies!

diretur 11-22-2013 05:54 PM

Quote:

Originally Posted by dionak (Post 2460668)
Hello,

I hope someone can offer advice. We are using VBSSO with Wordpress on a production server, after testing it on a development server, and it works fine on both of those.

Now, we have copied that production server--database and all--over to a third server to set up a new staging server. When we copied it, the links between the two systems, vBulletin and Wordpress, were still pointing to the 'www' versions of the blog and forum. We changed the URLs of the system to start with 'staging', but we ended up Removing the link in the vBulletin VBSSO options panel, and deleting the 'vbsso' database entries in the wp_options table, because the links would not work to log in.

Now the problem: when we try to re-establish a connection between the staging forum and the staging Wordpress, we just get an error page, but the space after label 'Error:' was blank. (We know it's connecting, because we have the staging server under basic authentication, and if we don't put the correct username/password in the Connect a Platform panel, we get a "401 Authorization Required" error message in that spot.)

Even though it says there is an error, and no connection is listed on the vBulletin side of vBSSO, options for mapping our custom vB usergroups to Wordpress roles then appear in the Wordpress side settings for vBSSO, and vbsso entries are recreated in the wp_options table. We still can't login to Wordpress through the vBulletin link, either. (We can get to Wordpress admin by going directly to wp-login.php and using a pre-link admin account created in Wordpress.)

Any help would be greatly appreicated.

same problem here

diretur 11-23-2013 04:41 AM

Quote:

Originally Posted by dionak (Post 2460668)
Hello,

I hope someone can offer advice. We are using VBSSO with Wordpress on a production server, after testing it on a development server, and it works fine on both of those.

Now, we have copied that production server--database and all--over to a third server to set up a new staging server. When we copied it, the links between the two systems, vBulletin and Wordpress, were still pointing to the 'www' versions of the blog and forum. We changed the URLs of the system to start with 'staging', but we ended up Removing the link in the vBulletin VBSSO options panel, and deleting the 'vbsso' database entries in the wp_options table, because the links would not work to log in.

Now the problem: when we try to re-establish a connection between the staging forum and the staging Wordpress, we just get an error page, but the space after label 'Error:' was blank. (We know it's connecting, because we have the staging server under basic authentication, and if we don't put the correct username/password in the Connect a Platform panel, we get a "401 Authorization Required" error message in that spot.)

Even though it says there is an error, and no connection is listed on the vBulletin side of vBSSO, options for mapping our custom vB usergroups to Wordpress roles then appear in the Wordpress side settings for vBSSO, and vbsso entries are recreated in the wp_options table. We still can't login to Wordpress through the vBulletin link, either. (We can get to Wordpress admin by going directly to wp-login.php and using a pre-link admin account created in Wordpress.)

Any help would be greatly appreicated.

I solved it deleting in the database the old users from the previous database. When you log in with your vb users again, it will be ok.


All times are GMT. The time now is 05:29 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02086 seconds
  • Memory Usage 1,759KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (2)bbcode_code_printable
  • (3)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (4)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete