-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Default report produces error 500 Internal Server Error #13695
Comments
It was introduced in this change: https://github.com/mautic/mautic/pull/13597/files#r1580670957 |
@AlanWierzchonCA is working on a fix for this - thanks for reporting it @juangadiel 🚀 |
I'll deal with it this week. |
We should probably wait with releasing Mautic 5.1.0 for this bug fix. |
@juangadiel please can you test #13708 as this should fix the bug! Thanks @AlanWierzchonCA 🚀 |
@all-contributors please add @juangadiel for bugs |
I've put up a pull request to add @juangadiel! 🎉 |
|
Sure thing, will do :) |
I can confirm the PR #13708 fixes this bug. |
Closing this as it's solved with #13708 |
|
Mautic Version
5.0.x series
Way of installing
Other (please specify if relevant in the bug report)
PHP version
8.2.18
What browsers are you seeing the problem on?
Chrome
What happened?
Way of installing: Gitpod from official Mautic repo on branch 5.x
Browser: Brave
Every time I try to open the default report “Downloads of all Assets” on a newly created Gitpod, I get the error "500 Internal Server Error - Key "id" for array with keys "referer, downloads" does not exist.". It is worth mentioning that the report has not been modified.
How can we reproduce this issue?
– Upload a local file (I tried with both .png and .jpg)
– Do not alter/edit anything else and click on “Save & Close”
– Copy the download URL
– A 500 Internal Server Error is thrown.
Relevant log output
Code of Conduct
Care about this issue? Want to get it resolved sooner? If you are a member of Mautic, you can add some funds to the Bounties Project so that the person who completes this task can claim those funds once it is merged by a member of the core team! Read the docs here.
The text was updated successfully, but these errors were encountered: