Suma Version

[Gavin Spomer]

Is there a way to determine which version of Suma I'm running? I do not see any files in the Suma directory tree that have version information. 

Thanks for your time.

 - Gavin 

[Jason Casden]

Well, this is an embarrassing oversight. If you downloaded the release from GitHub, it should come in a file with the version in the name (e.g. Suma-4.1.0.zip). If you are using a cloned git repository, you can see the current version tag with the command `git describe --tags`. I'll create a ticket to look into storing the version number somewhere else.

Jason

--
You received this message because you are subscribed to the Google Groups "Suma: mobile library assessment toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to suma-mobile-library-asses...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/suma-mobile-library-assessment-toolkit/225ab3d5-676a-4098-84e3-49a773a4ca06n%40googlegroups.com.

[Gavin Spomer]

Welp, I'm guilty of not keeping better documentation. I have pretty good notes from my original install of Suma, but I didn't have the version in those notes. I just successfully upgraded to 4.1.0 from version unknown, LOL. This time I didn't rename the Suma-4.1.0 directory to "suma" like I did originally. I also stuck my own version.txt file in the root directory. 👍 

Great job on 4.1.0! One of our access services staff was getting 500 "IDN conversion failed" error when running reports which was coming from the _idn_uri_convert() function in analysis/reports/lib/php/vendor/guzzlehttp/guzzle/src.functions.php. I thought I was using the latest version, but after doing a test install of 4.1.0, using the same database as my original installation, I noticed it was different. So, then I just migrated / reconfigured and my test install became an upgrade. It fixed the error with the reports (did 4.1.0 update guzzlehttp?) and I noticed the client was now running in my Chrome browser w/o errors too. I understand Web SQL is now quite deprecated. What did you use to reimplement its functionality? 

Thanks for your reply.

 - Gavin 

[Jason Casden]

Gavin,

That's great! The folks at NCSU Libraries developed an entirely new client using the localStorage-based library localForage. There were a lot of other improvements along the way, but their implementation significantly eased the transmission of data between the client and the server. You can see the PR here:

https://github.com/suma-project/Suma/pull/144

Thanks,

Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/suma-mobile-library-assessment-toolkit/5530722d-88b3-4c60-afec-d33e389b6479n%40googlegroups.com.

[Gavin Spomer]

Cool. I'm going to check out localForage.

 - Gavin