Posts made by Brandon-2021

@peopleinside I am currently only running version 1.0.13 and have made workarounds for most of the bugs in that version, but the team is getting irritated with some of the bugs I cannot fix without rewriting the core packages. Updating the versions right now is just moving around bugs in the system as new features are getting added while bugs are being fixed.

This is why new features need to be pushed to version 2.0 and current bug fixes need to be made on version 1 until they are all worked out.

I like the direction UV-Desk is headed but if things continue as is we may end up switching to something else as end-users don't really care about the why's or processes involved in development.

Is there any plan to create a fully working version 1 that has addressed all of the bugs and any new features being implemented in a beta or version 2?

With this running live with tickets in the database and how easily things are breaking or can become corrupt, I cannot be updating each package each time there is a new error caused by a new feature.

@SCoccia Do you have the cronjob running?

If someone else lands here with something similar. For your Ticket Types make sure you're not hitting enter when completing the description. This is for version 1.13.

Thanks for your help @Sanjeev

@Sanjeev

Nothing is set up with workflows, groups, or teams; the only thing is Type. Reply issue is the same for any member and Admin. The TinyMCE though isn't getting initialized for some reason.

Was there anything found from this as I am having a very similar issue all of a sudden?

Tickets get created but when you go to reply TinyMCE is failing to initialize and the field is null.

Hi @Sanjeev,

What is being stored in the cache?
If I delete the entire folder the project should 100% be fine correct?
Also is there a way to limit the cache? this project is up to 6.1 gb of cache files.

Thanks,

Brandon

@peopleinside Not a problem, I am a programmer and just glad to help out!

I have found and corrected the issue.

In these two files

• vendor/uvdesk/support-center-bundle/Controller/Ticket.php
• vendor/uvdesk/core-framework/Controller/Ticket.php

In the function "public function downloadAttachment(Request $request)", add the this line of code:

• $response->headers->set('Content-Length', $attachment->getSize());

Below

• $response->headers->set('Content-Disposition', 'attachment; filename='. $attachment->getName());

And Above

• $response->sendHeaders();

@peopleinside Thanks again for the help!

@Sanjeev I also just tried the same steps on the UV-Desk demo page and the file is corrupt as well.

@Sanjeev Hi, which file are you referring to? If you are asking for one of the corrupt files any file saved as docx (Word), xlsx (Excel), pptx (Powerpoint) returns corrupt. When you create a simple file with a sentence in it, save, upload, download it is still readable. However, you get this error window when opening. .

Forgive me if I am finding the version in the wrong file (CHANGELOG-1.0.md), but the version is * 1.0.12 (2020-07-27).

Steps taken:

• File uploads as an attachment with no issue.
• When I download the file after uploading it to the server via FTP (file with the new name) no issue.
• When trying to download the file on the ticket page the file is corrupt.
• I tried editing the page HTML to just download the file and not opening a new tab, still corrupt.

Not sure if the issue is with the route URL link for the download or server permissions. I tried this on a CentOS 7 server as well as a Ubuntu 20.04 server, same issue on both.

I also looked for an error log but couldn't see anything, if there is a specific log I should be looking at please let me know.

Any office file with the x extension is downloading corrupted. Has anyone had this issue with CentOS 7?

All Microsoft Office XML versions (docx, pptx, xlsx, etc) when downloaded show an error " Word found unreadable content in 8qqrwPwAl3HRa01d.docx. Do you want to recover the contents of this document? If you trust the source of this document, click Yes. ".

Is this a known issue?