Has anyone tackled the changes necessary to get this running on PHP7

[theotherdy]

Currently 500 error during install when hits for 'mysql_' function.

[RotateAt60MPH]

Hi there. Is this for a standalone install, or are you creating an olab instance in a Docker container?

[RotateAt60MPH]

Oh, and is this for olab3 or olab4?

[theotherdy]

It's a standalone install I'm trying on an Ubuntu 18.04 server, which already has various PHP 7 applications on it. Ideally olab3, as it looks as if olab4 isn't ready for production? Although this is really just looking for ways to improve the quality of our medics' education during COVID-19 lockdown so we could put up with everything not being perfect if olab4 is almost there?

[RotateAt60MPH]

The project manager (Dr. Topps) will step in here shortly about OLab3, but OLab4 is near production-ready. Depends on what features and capability you want to take advantage of. Between the two of us, we should be able to steer you in the right direction. Thanks for reaching out.

[topps]

Sorry that install is pretty quirky now. v3.3.1 will install more simply, IIRC, and is happy with PHP v5

We had to move to PHP7 for v3.5 and this introduced some install hassles. The dev team had to beat on it a bit to get PHP7 to play nice. I will see if I can find what they did. In the meantime, you might want to try an earlier version. v3.3.1 has most of most commonly used functionality. Also happy to give you some demo accounts on our demo server if you want to try out various case-authoring things there.

[theotherdy]

Thank you both, and for the offer of demo accounts. A few demo accounts would be very useful but I think I'll need to convince myself that we can get something working on PHP7 before we go too far down this route - my sys admin tells me he wouldn't be happy with PHP5. I don't know enough about Open Labyrinth yet to know what features we need, but the bar is fairly low - the alternatives are reverting to Quandary (Hot Potatoes) or H5P's branching scenarios, neither of which would be ideal. I am a PHP developer but am too short of time with the current crisis to do much at the moment I'm afraid.

[theotherdy]

Hi @topps. Is v3.5, which works on PHP7, available somewhere? Couldn't see it in here. Or is there another version which will work on PHP 7?

[topps]

Sorry, I mispoke. We are running version 3.5 on our demo server but have not released it. However, I just checked phpinfo on that server and found that it is running PHP 5.5.38, not PHP7. I must have been getting confused with the OLab4 instances. Yes, the shift to PHP7 is non-trivial.

[topps]

Apologies also for the less than wonderful support on this. Our own tech teams are also struggling with other issues during Covid so we cannot bang on them much for fixes. OLab4 is reasonably functional at present but still incomplete on the authoring side. One workaround might be to create your cases on our demo server and then export them to your own OLab4 server. The export/import routine works reasonably well and is our current workaround for some of the OLab4 authoring deficiencies. Does that help?

[theotherdy]

Thanks @topps , that sounds very sensible indeed. Do we request demo accounts via https://openlabyrinth.ca/free-trial/?

[topps]

Yup, that's the page to use.

[andyjaffs]

Hello community. I am supporting some work with Open Labyrinth and have a 3.3.2 version running in a dev environment. For production I have to adhere to some internal requirements that necessitate PHP7. I manage to wrestle the installation changes to get an installation on PHP7, this was mainly swapping to mysli, in the hope that the app would be less sensitive when installed. I have discovered that is not the case and there is a lot more to unpick.

Whilst I intend to continue with documenting the changes, my other option is, as is recommended above, moving to Olab4 with the caveats of creation, import and export from the free trial above.

With the limitations of my internal requirement of PHP7, would your opinion at the moment be to proceed with Olab4?