Jim Henderson wrote:
On Tue, 03 Mar 2020 07:25:58 +0100, Per Jessen wrote:
Looking at the error message, I think Gertjan is on track - this is coming from vBulletin 5. I know we talked about the database needing to be upgraded, and that was the plan - but to confirm, did you install the database on version 4 first and then upgrade to version 5?
This is with vb5 connect - I am expecting the code to spot the back-level database and do the upgrade automagically.
vBulletin hasn't traditionally been that smart. There should be an upgrade script in the installation directory IIRC
Okay, that's a pity, I was expecting something reasonably clever. Still, an upgrade script will do too.
I do have a Docker container that has a fully-running vBulletin instance in it - I can make that available to you if that would help with validating the database dump you got from Jared.
It looks like a plain mysqldump export, and it imported without problems.
The idea of running the existing code on the existing database was before we got our hands on the latest version of vB.
I understand - the thing is that vB just doesn't have the brains to automatically upgrade the database. That has to be initiated by the admin.
Right - I'll have to go do some more reading.
I am expecting to use the authentication scheme we use for e.g. our wikis and progress.o.o - any reason this would not work? I don't know much about it myself, I'll need some help with that.
I believe we use a SAML 2.0 add-on in our current implementation; logging in through the wiki and progress.o.o, I don't see any SAML traffic from my browser. Kim or Jared could confirm what the plugin we use is for SSO currently.
I guess I could have a look myself, Kim sent me a tarball with everything. -- Per Jessen, Zürich (3.9°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org