search

Peppermint-Lab / peppermint

An open source ticket management & help desk solution. A zendesk/freshdesk alternative
https://peppermint.sh
Other
1.95k stars 205 forks source link

Ticket submitted via /submit route returns error #356

Closed hiteshdaswani closed 6 days ago

hiteshdaswani commented 2 months ago

Screenshot attached;

Screenshot 2024-07-27 095137

Discussed in https://github.com/Peppermint-Lab/peppermint/discussions/351

Originally posted by **sudo-sein** July 8, 2024 I used /submit route to test the anonymous submitting functionality, and I tried to access the ticket as admin in dashboard I got following error: "initialContent must be a non-empty array of blocks, received: This is ticket content" Here's screenshot of details page. ![image](https://github.com/Peppermint-Lab/peppermint/assets/419502/5e3d319d-6195-4872-9b83-a976d4db168f) Here's log console for that ticket. ![image](https://github.com/Peppermint-Lab/peppermint/assets/419502/91f96c97-146b-456e-8030-93b5443f37a4) Seems to me like new submissions are not escaped correctly.
Spectroxx commented 2 months ago

Discussed also in https://github.com/Peppermint-Lab/peppermint/issues/338

Legomountain14 commented 1 month ago

same issue here.

hiteshdaswani commented 1 month ago

I moved to ESPOCRM, way better than peppermint and easier to setup.

Legomountain14 commented 2 weeks ago

Any update on this?

hiteshdaswani commented 2 weeks ago

i went with ESPOCRM instead, much better than peppermint. i have it working for a month now, no problems, super stable.

Hitesh Daswani IT Consultancy E-ID : @.*** Mobile Personal: +599-96726748

On Wed, Sep 18, 2024 at 9:25 AM Legomountain14 @.***> wrote:

Any update on this?

— Reply to this email directly, view it on GitHub https://github.com/Peppermint-Lab/peppermint/issues/356#issuecomment-2358626140, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFZMGXZGSIG27BTWYWXXTLDZXGEPLAVCNFSM6AAAAABLR6BJDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJYGYZDMMJUGA . You are receiving this because you authored the thread.Message ID: @.***>

potts99 commented 6 days ago

This is now fixed