wrong PHP path

eware

We complete installation successfully and almost everything looks fine. The only problem we have is ticket refresh button at agent panel. It links to a PHP at wrong path. It links to support.abc.com/scp/scp/index.php instead of support.abc.com/scp/index.php.

Anyone has met this problem before ? and how to fix it ? your help is appreciated. Thanks.

Chefkeks

Check your helpdesk URL setting to make sure to not include /scp at the end:

Admin panel > settings > system > helpdesk URL

Beside, please provide more info about your osTicket installation:

http://forum.osticket.com/d/discussion//please-read-before-requesting-assistance#latest

eware

Thanks for your help.We don't include /scp in the helpdesk URL. All links of all other button are correct ( as far as I checked ), only the ticket refresh button links to PHP with wrong path. It is very strange. Is the path detection for this button different from other buttons ? our server information is as below. osTicket Versionv1.9.6 (9adad36)Web Server SoftwareMicrosoft-IIS/7.5MySQL Version5.1.68PHP Version5.4.23

ntozier

Re: "All links of all other button are correct ( as far as I checked ), only the ticket refresh button links to PHP with wrong path."Can you please provide a sanitized (change domain name) path that works, and the one that does not?

Chefkeks

Can you also please post a screenshot of the link preview (usually visible in the status bar of the browser when your mouse is over the link), since I can't confirm this wrong link with my installation (1.9.7).

eware

For refresh button, its path is wrong as below. blank For elsewhere, its path is correct, like below. blank we also try 1.9.7, but problem is the same.

ntozier

I am unable to confirm a problem with this. It works in my installations.My guess is that your web.config is messed up or that your system is doing something wonky with root_path...

eware

It is only that refresh button interpret a wrong root_path, but no elsewhere. Does the refresh button detect the root_path in a different way ? any workaround to fix this issue ? Thanks.