This is what I get when I try adding my own query as administrator:
Something has gone wrong: the Gibbons have escaped!
An error has occurred. This could mean a number of different things, but generally indicates that you have a misspelt address, or are trying to access a page that you are not permitted to access. If you cannot solve this problem by retyping the address, or through other means, please contact your system administrator.
I downloaded the module today. And see this:
I clicked on the update button a couple times.
It seems that you have updated your Query Builder module code to a new version, and are ready to update your database from v1.10.0 to v1.10.01. Click “Submit” below to continue. This operation cannot be undone: backup your entire database prior to running the update!
And I know I uploaded the v1.10.01 folder.
Hi Tieku, after running the update, the module should no longer appear as green in the Manage Modules table. Can you please confirm whether or not this is happening? Thanks!
To confirm, when “running the update”, are you clicking on the package icon in the green row, and then pressing the submit/update button, and receiving a green confirmation in return? Thanks!
Yes. This is the sequence of actions I am taking.
Hi Tieku, right, I think I know what the issue is: prior to Gibbon v21 (to be released on Jnuary 20th 2021), Gibbon struggles with module versions higher than vX.9.YY. As Query Builder is now v1.10.YY, it is causing issues in your install.
Please can you try and add the following files to your v20 installation, and see if that solves the issue:
In retrospect, using Query Builder v1.9.01 might be better. I’ve marked v1.10.01 as suitable for v21 and above only on the Extend page. Sorry for the confusion!
Should I simply replace the folder I uploaded?
Although there is a commit called v1.10.0, there is no such version of Query Builder: it was a typo. The release is actually called v1.10.01. Yes, you should be able to simply replace the current version of Query Builder with v1.9.01 and run the update script. Let us know if this causes any issues.