Search found 4 matches
- 14 Aug 2009, 15:08
- Forum: Help
- Topic: 1.1.8 URL in emails occasionally uses example.com
- Replies: 3
- Views: 6074
Re: 1.1.8 URL in emails occasionally uses example.com
Just found this: http://www.mantisbt.org/bugs/view.php?id=9463
- 14 Aug 2009, 14:46
- Forum: Help
- Topic: 1.1.8 URL in emails occasionally uses example.com
- Replies: 3
- Views: 6074
Re: 1.1.8 URL in emails occasionally uses example.com
Thanks!
I looked through the code and it seems that just setting $g_path in config_inc.php to http://<ourserver>/mantis is sufficient and it certainly seems to have fixed it.
The problem looks like this code in config_defaults_inc.php fails to find the correct URL when called from command line ...
I looked through the code and it seems that just setting $g_path in config_inc.php to http://<ourserver>/mantis is sufficient and it certainly seems to have fixed it.
The problem looks like this code in config_defaults_inc.php fails to find the correct URL when called from command line ...
- 13 Aug 2009, 16:12
- Forum: Help
- Topic: Unable to filter using custom fields after upgrade
- Replies: 3
- Views: 3016
Re: Unable to filter using custom fields after upgrade
I hit this problem too on 1.1.8 (having upgraded from 1.1.1), thanks for posting your fix, really helped me out!!
I fixed it in a slightly different way as I was a bit concerned about changing db_helper_like() as it is used elsewhere and I wasn't sure of the consequences. So I went with:
filter ...
I fixed it in a slightly different way as I was a bit concerned about changing db_helper_like() as it is used elsewhere and I wasn't sure of the consequences. So I went with:
filter ...
- 11 Aug 2009, 10:05
- Forum: Help
- Topic: 1.1.8 URL in emails occasionally uses example.com
- Replies: 3
- Views: 6074
1.1.8 URL in emails occasionally uses example.com
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 ...
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 ...