1.1.8 URL in emails occasionally uses example.com
Posted: 11 Aug 2009, 10:05
Hi,
I've recently upgraded from 1.1.1 to 1.1.8. We had been using 1.1.1 for over a year with no issues.
The upgrade went smoothly but since then the notification emails randomly have http://www.example.com and a filesystem path for the view issue URL instead of the correct server name/path. E.g.:
http://www.example.com/usr/local/apache2/htdocs/mantis/core/view.php?id=2161
Instead of:
http://<ourserver>/mantis/view.php?id=2161
At a very rough guess this happens something like 1 in 20 emails and affects the link to the issue plus any links to notes e.g.:
http://www.example.com/usr/local/apache2/htdocs/mantis/core/view.php?id=2161#c8606
It seems to be only in the emails. Viewing the issue via the web front-end so far appears to be fine i.e. any embedded links to other issues in the notes use the correct URL even though those same links are sometimes wrong in the emails.
We have SVN integration via the post-commit hook and checkin.php script. It is possible that this error only occurs when emails are triggered through that mechanism but this normally works OK.
Any ideas?!
Jon
I've recently upgraded from 1.1.1 to 1.1.8. We had been using 1.1.1 for over a year with no issues.
The upgrade went smoothly but since then the notification emails randomly have http://www.example.com and a filesystem path for the view issue URL instead of the correct server name/path. E.g.:
http://www.example.com/usr/local/apache2/htdocs/mantis/core/view.php?id=2161
Instead of:
http://<ourserver>/mantis/view.php?id=2161
At a very rough guess this happens something like 1 in 20 emails and affects the link to the issue plus any links to notes e.g.:
http://www.example.com/usr/local/apache2/htdocs/mantis/core/view.php?id=2161#c8606
It seems to be only in the emails. Viewing the issue via the web front-end so far appears to be fine i.e. any embedded links to other issues in the notes use the correct URL even though those same links are sometimes wrong in the emails.
We have SVN integration via the post-commit hook and checkin.php script. It is possible that this error only occurs when emails are triggered through that mechanism but this normally works OK.
Any ideas?!
Jon