I’m having a bizarre problem, and I’m concerned about it affecting my ability to use Gibbon for the next school year.
I’m getting ready to move to a new school, as our current school will close. The plan was to use Gibbon again in the new program I am helping found. Currently I’m using Gibbon through Lithium Hosting, a shared hosting provider.
Well our school may or may not reopen in a new location. So someone from the current school’s parent company is visiting, because she may be involved in the running of the program next year, should it continue. She wanted to explore Gibbon.
Rather than give her access to our live system, where something could end up edited, I decided to install a clean copy and let her set it up with some fake data, so she can go through the whole process. I created a new test subdomain and installed Gibbon into it.
We are currently running 16.0.01. The new install (via Softaculous) was of 17.0.0 with no ability to install an older version. Upon installing Gibbon 17, I was completely unable to access my new install. Clicking the link provided by the installer, or manually entering the address, I was left with a white, empty browser window and no page loading.
Thinking that was bizarre, I deleted the installation and cloned our existing into the test subdomain. The cloned installation worked fine!
I then decided to try updating the cloned installation to 17. As soon as the update completed, no pages would load in the test subdomain. Same issue; empty, white window and a browser that says it’s done loading!
Is there a new PHP requirement or something else different in 17 that could be causing this? Because with a new school next year, we would also be changing our domain and working with a fresh install of Gibbon. But if I can’t run installs of 17, and I can’t install an older version, I’m not really sure what I’m going to do!