starred/SuiteCRM-SuiteCRM

Fork 0

mirror of https://github.com/SuiteCRM/SuiteCRM.git synced 2026-03-02 19:16:58 -05:00

[Bug][AOR_Report] Can not export report with date condition as parameter #5317

New issue

Open

opened 2026-02-20 16:59:34 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 16:59:34 -05:00

Owner

Originally created by @BeastMasterGrinder on GitHub (Apr 11, 2025).

Issue

No response is returned from server when exporting report

For a report with date condition, checked as a parameter, it can not be export. As the screen turns blank and a no response is returned from server. This is because of the process being silently killed so you would not get an error in the log files even when your logging level is 'debug'. You may see that after the AOR_Condition is retrieved the mysql_db_manager silently dies.

Verified Bug on Versions

v8.2.0
v8.7.0
v8.8.0

Steps to Reproduce the Issue

Go to the Reports section.
Create a new report.
Choose any fields you want to display in the report.
For Conditions, choose any Date field.
Set the operator to "Greater Than or Equal To".
Set the Type to "Date".
Set the Value to "Today".
Fill out any remaining required fields as you like.
Make sure to check the "Parameter" checkbox.
Save the report.

Triggering the Bug

Go to Actions > Export for the saved report.
Get a blank screen and NO response from server.
...

Context

Image illustration

Creating the report with condition

Saving the report

After clicking on Actions<Export

Blank Screen

Network Tab Dev tools

No response

Version

v8.8.0, v8.7.0, v8.2.0

What browser are you currently using?

Firefox

Browser Version

Same on all browsers

Environment Information

PHP 8.2.12, MYSQL Ver 15.1 Distrib 10.4.32-MariaDB, for Linux (x86_64) using readline 5.1

Operating System and Version

Ubuntu 20.04

Originally created by @BeastMasterGrinder on GitHub (Apr 11, 2025). ### Issue ### No response is returned from server when exporting report For a **report with date condition, checked as a parameter**, **it can not be export**. As the screen turns blank and a _no response is returned from server._ This is because of the process being silently killed so you would not get an error in the log files even when your logging level is 'debug'. You may see that after the AOR_Condition is retrieved the mysql_db_manager silently dies. #### Verified Bug on Versions v8.2.0 v8.7.0 v8.8.0 ### Steps to Reproduce the Issue 1. Go to the **Reports** section. 2. Create a new report. 3. Choose any fields you want to display in the report. 4. For **Conditions**, choose any **Date** field. 5. Set the operator to **"Greater Than or Equal To"**. 6. Set the **Type** to **"Date"**. 7. Set the **Value** to **"Today"**. 8. Fill out any remaining required fields as you like. 9. Make sure to check the **"Parameter"** checkbox. 10. Save the report. ## Triggering the Bug 1. Go to **Actions > Export** for the saved report. 2. Get a blank screen and NO response from server. ... ### Context ### Image illustration Creating the report with condition ![Image](https://github.com/user-attachments/assets/5bd0d267-4de2-41d2-a88b-dfe2a18e43a2) Saving the report ![Image](https://github.com/user-attachments/assets/bc66fbff-f2f9-4d14-8b0d-7852e19cc393) After clicking on Actions<Export ## Blank Screen ![Image](https://github.com/user-attachments/assets/67729702-4cb8-43ab-b9f3-e63f00b86848) ## Network Tab Dev tools No response ![Image](https://github.com/user-attachments/assets/c88ab07d-32ff-45ec-bca9-e48637f594eb) ### Version v8.8.0, v8.7.0, v8.2.0 ### What browser are you currently using? Firefox ### Browser Version Same on all browsers ### Environment Information PHP 8.2.12, MYSQL Ver 15.1 Distrib 10.4.32-MariaDB, for Linux (x86_64) using readline 5.1 ### Operating System and Version Ubuntu 20.04

deekerman added the

labels

2026-02-20 16:59:34 -05:00

deekerman commented

2026-02-20 16:59:36 -05:00

Author

Owner

@BeastMasterGrinder commented on GitHub (Apr 11, 2025):

It is because in AOR_Reports.php the data that is going is unserialized. It should be serialized.

@BeastMasterGrinder commented on GitHub (Apr 11, 2025): It is because in AOR_Reports.php the data that is going is unserialized. It should be serialized.

deekerman commented

2026-02-20 16:59:36 -05:00

Author

Owner

@johnM2401 commented on GitHub (Apr 11, 2025):

Hey!

Thank you for raising this issue.

I've been able to replicate this in both 8.8.0 and 7.14.6, so i've transferred this over to the SuiteCRM7 repository.
This means that, when a fix is found and applied here in SuiteCRM7, the same fix should be pulled into SuiteCRM8 on the subsequent release.

Thank you again for your contribution to the project!

@johnM2401 commented on GitHub (Apr 11, 2025): Hey! Thank you for raising this issue. I've been able to replicate this in both 8.8.0 and 7.14.6, so i've transferred this over to the SuiteCRM7 repository. This means that, when a fix is found and applied here in SuiteCRM7, the same fix should be pulled into SuiteCRM8 on the subsequent release. Thank you again for your contribution to the project!

deekerman commented

2026-02-20 16:59:36 -05:00

Author

Owner

@BeastMasterGrinder commented on GitHub (Apr 11, 2025):

Alright! Thanks. JAZAKALLAH.

@BeastMasterGrinder commented on GitHub (Apr 11, 2025): Alright! Thanks. JAZAKALLAH.