Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
0012998: Hammerjs does not load #6433
Reported by schwigi on 2 May 2017 16:52
Version: 2017.02.3 Community Edition
On my new Windows 10 tablet hammerjs gets not loaded propperly. This results in the calendar and addressbook not working.
On the tablet this is reproducible on the tablet with Chrome, Edge and Firefox on Windows 10 and with Firefox running Ubuntu.
On all other systems I've tested (Windows 7, Windows 10, Ubuntu with Chrome and Firefox) all without a touchscreen.
Since my tablet is the only device with a touchscreen available and hammerjs is supposed to be a touch gesture library my guess is that this is reproducible on other touch screen devices as well.
Steps to reproduce: Use a device with a touchscreen and use the tine20 webinterface.
Additional information: The Server is running tine in a subdirectory
https://<servername>/tine20 on an Ubuntu 16.04 LTS
Comment posted by ingoratsdorf on 3 May 2017 02:56
I can confirm the issue with windows10 on a SurfacePro3 and any browser.
Comment posted by schwigi on 3 May 2017 16:34
I am running the packaged ubuntu version from xenial stable. So no current dev changes should be a problem.
The browsers I used (Desktop Firefox, Desktop Chrome) are all supported and should not result in a load error or strange behaviour without using touch gestures. Using an ASUS T101HA Tablet with Dock attached.
If it helps I can set up an npm version in parallel.
Comment posted by hobbyist on 14 Aug 2017 22:31
Hey, some TInebase/js-libraries, e.g. OpenLayers-f5fc191258fd529b739f-FAT.js or linkify, can't be loaded for me either. In my case, Tinebase/js is linked to the /-docroot-directory, whereas tine 2.0 is installed in a subdirectory-path. Maybe that's also your problem with hammerjs not working?!
Providing a /TInebase/js in the webserver's docroot-directory, is a ugly, but functional workaround. Maybe I try a rewrite.
Comment posted by estradis on 24 Aug 2017 07:11
@hobbyist: Not sure what you want to tell me. What exactly is the problem and what exactly have I to do to fix it?
Comment posted by hobbyist on 27 Aug 2017 08:43
So, if you asked me for an advice or a quick fix, I would recommend you to think about whether you can afford/want (in your environment) to provide that /TInebase/js-directory additionally in https://yourdomain.org/Tinebase/js, cause that's the place your https://yourdomain.org/tine20/-installation is looking for those scripts, or try a rewrite of that paths.
Otherwise you have to wait, till the adressing of that components is fixed by the developers.
So, no offence meant, maybe that will help you to decide or solve your problems.
Comment posted by estradis on 28 Aug 2017 12:07
Now I almost feel a bit ashame because I didn't get it myself. (We had some infrastructure incidents in a HA environment, therefore the whole team had a lot of overload to troubleshoot. Maybe that was the reason.)
Thank you for your recommendation. I appreciate it! Your example looks very good. We should be able to uphold our hardening by using Tinebase as an alternate subpath. We'll investigate this and report as soon as we have the results.