LCA Transformer on PHP 7.4 about suma HOT 6 CLOSED

I'm sorry that we didn't respond to this issue. Can you see if this is a still a problem with the latest release?

from suma.

I had upgraded Suma to version 4 a while back and apparently hadn't tried loading any reports for a while (I have it setup to pull stats directly from the database for our monthly stats, so neither I nor my staff are frequently going into the reports view). However, last week I was talking to some staff at area libraries on a Zoom call and wanted to point out how great Suma was (among other things) and I got a 500 error when trying to load the reporting page. I quickly moved on to other things, but today I got back to looking at it, noticed your message, and updated from 4.0.0 to 4.0.1. Unfortunately, that does not seem to have resolved the problem for me.

I'll see if my old fix works still. In any case, let me know if you would like me to test anything on this problem.

from suma.

from suma.

Sure. I've looked in web server logs and haven't found anything. So far I haven't found anything likely super-useful in troubleshooting this, but I have identified this (some of which I'm guessing that you can guess): the error is coming back from a dataResults.php script. If I adjust the id parameter, I can get the error to change from saying that I have no initiatives to saying that there's no data for the initiatives. The initiative id for the initiative with the most data is 8 ("Winnetka Reference"). I'm not seeing an "8" getting passed by the form data to that script when Winnetka Reference is selected (e.g.: https://babbletron.winnetkalibrary.local/suma/analysis/reports/lib/php/dataResults.php?classifyCounts=count&days=mo,we,th,fr,sa,su,tu&edate=2022-06-28&etime=&excludeActGrps=&excludeActs=&excludeLocs=&id=1&requireActGrps=&requireActs=&sdate=2022-02-28&startHour=0000&stime=&wholeSession=no). I am seeing an "id=1" in there and if I change "id=1" to "id=8" the returned JSON is: {"message":"No data found for that combination of filters. Please try a broader search."}

I'll check my config files and look for errors elsewhere. The only errors I've been able to identify so far are in the web developer console (which is how I found the above URL).

from suma.

While troubleshooting this the issue suddenly resolved itself and I'm not sure why. I made a number of minor changes to config files, which I've largely tried reversing to identify the cause, but with no effect. For the record, the changes I can remember making are:
I changed SUMA_DEBUG in ./service/web/config/config.yaml from true to false
I created a session.yaml file and then deleted it (I decided I didn't need to be using that optional feature)
I turned showErrors on and change serverIO: baseUrl to use https in ./analysis/config/config.yaml

Those are all of things I can remember adjusting between the previous time when I saw the error to the point where I reloaded the page and it loaded the graphs.

from suma.

from suma.