Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find old initiatives data #158

Open
davidhietpas opened this issue Dec 18, 2023 · 3 comments
Open

Cannot find old initiatives data #158

davidhietpas opened this issue Dec 18, 2023 · 3 comments

Comments

@davidhietpas
Copy link

I upgraded from Suma 2.0 to the newest version which supports php 8.1. Mainly because I had to migrate from Centos 8 to Oracle Linux 9. I setup Suma (again, have done this multiple times now).

I cannot get any Reports to generate on previously created Initiatives with past data. Get this though... if I submit new data on one of those old initiatives, it will generate a report on that new data just fine. It just won't on older data.

Below is the error that appears. It is odd because the initiative is in the drop down, I select it, it has all the location and activities loaded in. It just won't run the report on old data.

Notice!
There was a problem generating the report. Please try again or contact your system administrator.
Error Code: 500
Error Message: No initiatives found. Please create an initiative in the Suma admin tools.

Also odd, looking at the raw sql data. The data is the same in every aspect from that new data to old data.

I have all the high level debug logs running. Nothing is being logged.

David

@davidhietpas davidhietpas changed the title Cannot find previous initiatives Cannot find old initiatives data Dec 18, 2023
@davidhietpas
Copy link
Author

Just noticed another ticket with the same issue: #143

No way... he was right... this fixed it... by changing the SUMA_DEBUG in service/web/config/config.yaml to SUMA_DEBUG: false
#143 (comment)

There is definitely something odd going on there. FYI.

@ryet0ast
Copy link

Just noticed another ticket with the same issue: #143

No way... he was right... this fixed it... by changing the SUMA_DEBUG in service/web/config/config.yaml to SUMA_DEBUG: false #143 (comment)

There is definitely something odd going on there. FYI.

I just wanted to confirm that I had the same issue and resolution! Very strange indeed. Thanks for sharing.

@cazzerson
Copy link
Collaborator

Nice catch. I think there are some benign deprecation warnings that are throwing things off. We'll try to take a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants