The FOSSBilling Forum

Hello,
We started using FOSSBilling for one of our projects. I found some issue related to the Support System function. Below, I'm going to describe.

01. From the user side: The reply form doesn't have any functionality to upload images/add any attachements. But the admin side has it which is good. 

Users may need to add screenshot or attach file to get support from Support Ticket. 



Both reply form should be the same.


02. As an Admin after clicking to the Post button, the windows redirects to https://<domain-name>/admin/support?status=open

The window should be refesh and not to redirect to other pages. 

03. Using emoji in the reply form produces the following error.

Quote:01. From the user side: The reply form doesn't have any functionality to upload images/add any attachements. But the admin side has it which is good. 

Actually, neither side allows for file attachments. Such functionality just doesn't exist in FOSSBilling at the moment.
The admin side simply uses a WYSIWYG editor which makes it a bit easier to format the markdown correctly for images to be displayed.

I've been meaning to get the editor loaded in the client area as well, can't remember what roadblock I hit, but I'll revisit the idea again.

Quote:02. As an Admin after clicking to the Post button, the windows redirects to https://<domain-name>/admin/support?status=open

Ah, good catch and thankfully an easy fix.

Quote:03. Using emoji in the reply form produces the following error.

I'm fairly certain the older database character set is unable to store the literal value of those..
But I think I have a potential workaround for this which I will look into as well.

The SQLSTATE[HY000]: General error: 1366 Incorrect string value error typically occurs in MySQL (or MariaDB) when you try to insert or update data that includes characters that cannot be represented in the column's current character set or collation. This often happens when you're trying to insert special characters (such as emojis, accented letters, or non-Latin characters) into a column that doesn't support them.

but, maybe you write directly data base

Possible Causes:
Character Set Mismatch
Incorrect or Missing Collation
Client/Connection Character Set
Insert or Update Data with Unsupported Characters