@[deleted] @ bijlHello, we found out that nearly all problems are caused in the server and local pc settings. There are various things that must be correct installed and setup, starting by the used php version and configuration on your server up to javascript version and the used browser on your local PC.For example attached files in DMT Purify on local browsersFirefox Latest / Windows 10:working well > pdf, mp3, mpgnot supported > mov, mp4generating error, but work by downloading > png, jpg, tif, bmpEdge latest / Windows 10: working well > all files are offered as download, nothing is displayed in browserOpera latest / Windows 10: working well > all files are offered as download, nothing is displayed in browserChrome latest / Windows 10: working well > all files are offered as download, nothing is displayed in browserBut depending on your browser and operating system version and settings the result may be completely different.Some more problems are caused in used old libs and extensions by the core code. For example:jQuery v1.11.2 | Release Date:  December 18, 2014 >>> actual stable version 1.12.4 | May 20, 2016 > newest version 3.2.1  | March 20, 2017Redactor 10.2.2 | Release Date: July 15, 2015 >>> actual stable version 10.2.5 |  September 29, 2016 > newest version 2.11 | September 20, 2017fabric 1.4.13 | Release Date: December 4, 2014 >>> actual stable version 1.7.19 | September 17, 2017Select2 4.0.0 | Not available at github >>> official stable 4.0.1 was released November 28, 2015 >>> actual stable version 4.0.5  |  October 20, 2017JSTZ 1.0.4  | Release Date: December 18, 2012 >>> actual stable version 1.0.11 | September 5, 2017Beside compatibility problems with actual servers and libs these old libs can cause errors in newer browsers, security issues and vulnerabilies.More than a third of the websites you visit online may include an outdated JavaScript library that’s vulnerable to one or more security flaws. This is the conclusion of recent research carried out by a team of six scientists from the College of Computer and Information Science at Northeastern University, who scanned over 133,000 domains and found that 37% loaded outdated and insecure JavaScript libraries.http://www.securitynewspaper.com/2017/03/10/third-websites-use-outdated-vulnerable-javascript-libraries/http://www.ccs.neu.edu/home/arshad/publications/ndss2017jslibs.pdfThe inbuild jQuery 1.11.2 in osTicket has known XSS (cross site scripting) vulnerabilities that allows to inject arbitrary web script or HTMLWe remarked, that many osTicket installations are not working correct, even if the installer says "It's all fine". The forum is full of issues of a none correct running osTicket after the installation.To the end of the next week it's planned to release an optimized update of purify for the latest osticket version and a basic responsive version like our free ones, running at over 90% tested isps, without any additional functions.Sorry for the inconvenience, but we wasted weeks of testing and fixing at different isps (internet service providers) and didn't get back a result, that allows us to create an installation and fixing guide, that well result in a well working osTicket at any isp.In our opinion it's absolute necessary to update all outdated libs used in osTicket, enable theming/templates by core and to clean up all "doubled" functions, e.g sanitizing/cleaning html.Best regards, Jürgen

Yesterday we created an account with a separate hosting package on our server, did a clean install of osTicket 1.10.0, generated a customer account, created a ticket to test the attachment types and everything is working fine, all attachments are displayed correctly under Firefox: http://ost1100original.dmt.gmbhTo test the update package of purify live, we cloned the complete account and what should I say, the attachments are no longer displayed correctly under Firefox: http://ost1100purify.dmt.gmbhFeel free to login as customer and check it by your own in both installations:Username: MarkFischerPassword: markfischerWe checked the database, server settings and environment, file transfer - all was identical. It's so frustrating for us, but we are still go on. At the moment we are checking the server logs and do a automated file and database comparison of both installations... The good news: We have an update package for osTicket 1.10 and 1.10.1 that's running correctly on our local development servers. If we have found a solution for the cloning/copy/overwritting problem, the update package is released. Sorry, but it doesn't make sense to release a package that can cause problems by copy or overwriting.Please check both installations above under your common used browser and

Firefox, create a new ticket, tell us your browser version and the result, this will help us fixing the issues. You can create your own account, too. Both installations will be reset on Friday this week.Tomorrow we are doing the same with a clean osTicket 1.10.1 installation and inform you above the result.We remarked that under different server settings, local browser and javascript versions it comes to conflicts with the implemented bootstrap library/functions by osTicket and our added customized one.We have finished a responsive basic theme based on https://getuikit.com/v2/. This responsive framework is working well together with bootstrap under WordPress and Joomla. We plan to send all subscribers the first alpha version via mail this weekend.

@[deleted]: Thanks for testing. At the moment we are only interested in the attachment behaviour. All other things e.g. upload custom logo, translation fields for forms are working fine. At this point nothing in osTicket is modified, but the behaviour is strange only through copy, clone or overwriting.That's the annoying thing: Google Chrome, Opera, Edge, Internet Explorer are all offering any attachment as download and working fine. If you try to open an attachment with Firefox, some mimetypes like images and videos are displayed in the same browser window. The first installation "original" displays all attachments in Firefox, the second generates an error "Damaged File".Please check the ticket and attachment in both installations with Firefox, if possible, and report the result. We often have the problem, that osTicket doesn't behave in the same way in different browsers and with different local installed javascript versions and try to find out the reason.