Hi Tim,
Thank you very much for this great mod, we use it all the time!
Only one problem with the path names in the URL:
We have a main domain named for example: www.maindomain.com(www.maindomain.com)
and osTicket is installed in a subdomain called for example: subdomain.com/osticket
When we use the admin pages in osTicket all is fine with the URLs, we see them as for example: www.subdomain.com/osticket/scp/tickets.php?id=95(www.subdomain.com/osticket/scp/tickets.php?id=95)
But when we click anything that is related to the FAQ mod we get something like this in the URLs:
www.subdomain.com(www.subdomain.com)/subdomain.com/osticket/scp/faq_admin.php?fcPath=0_25_2_31&fID=419&action=new_faq_preview&
read=only
So there is something wrong with how the FAQ mod displays the URLs.
The same goes wrong if we use the client pages, anything related to the FAQ mod gives the wrong URLs.
Maybe you have a solution for this problem?
Thank you for your help!
Regards,
Eric
Hi Eric,
I think you should be able to fix it fairly quickly. You will need to manually edit the config.faq.php file.
I would suggest the following changes:
(replace the example parts (underlined) with the actual domain and paths. Dont include any http or https).
----------------
// domain part only. No slashes.
define('SERVER_DOMAIN', 'www.subdomain.com(www.subdomain.com)');
// like the Apache DOCUMENT_ROOT var. No trailing slash.
// in windows it would start with a drive letter
// EG: "Z:/absolute/file/path/osticket" (unix seperators are safest /)
define('OSF_DOC_ROOT', '/absolute/file/path/osticket');
// use a leading and trailing
// or just a single / if its in the public root dir
define('DIR_FS_WEB_ROOT', '/osticket');
----------------
If that doesn't help, start a new tracker artifact and I'll look into it further.
http://sourceforge.net/tracker/?group_id=288518&atid=1221963(http://sourceforge.net/tracker/?group_id=288518&atid=1221963)
(Click the Add new link at the top)
Further down the track:
I'm currently working on v1.1-ST which has some improvements to the dynamic URL system that might also fix your problem. I don't think it will be ready before late February/March though as I'm a bit behind with my day job due to some recent flooding we had (http://www.abc.net.au/news/infographics/qld-floods/beforeafter.htm(http://www.abc.net.au/news/infographics/qld-floods/beforeafter.htm)) with potentially more on the way due to heavy cyclone activity to the north.
Ill put a post in this forum thread as soon as I have v1.1-ST ready.
Regards,
Tim