tags: 689639 wontfix tags: 689640 wontfix thanks
This issue is related with BTS #635932 The problem is known to happen when someone manually change the default mantis VirtualHost configuration. Please refer to the following information to know how to deal with this situation. ---------------------------------------------- Virtual Host : mantis and javascript directory ---------------------------------------------- If you are reading this document is because you would need to change your default Web Server configuration for mantis. This action is needed just if you do not run mantis under the default path, and javascript-common is installed on the system: Default: http://host/mantis If you are going to setup a custom Virtual Host for mantis, which is going to run under your Virtual Host parent directory, ie. "http://mymantis";, you will need to verify if the javascript-common package is installed on the system, in that case you will need to add some extra changes on your custom Virtual Host configuration file. When javascript-common is installed and a web application is running under a custom Virtual Host, javascript-common overrides the path of any Alias directory named "javascript" with /usr/share/javascript/. This makes not possible to access other "javascript" directory from a web application (as mantis). To avoid this issue, you will need to add an Alias for mantis "javascript" directory into your Virtual Host custom configuration file. Alias /javascript /usr/share/mantis/www/javascript ---------------------------------------------- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
