Vtiger 5.4 portal url error
When we update our ticket status in vtiger, our users automatically get an e-mail saying their ticket has been updated. In the e-mail they receive they can click on a link that leads them to the portal website. When they click on this link it gives them a "The webpage cannot be found" error. This link used to work in the past, now for some unknown reason it doesn't anymore. The portal itself still works when browsing to it manually.
Some of the things we've noticed:
When clicking on the link we sometimes get https://websiteurl/PORTAL/INDEX.PHP and sometimes https://websiteurl/PORTAL/INDEX.PHP?MODULE=HELPDESK&ACTION=INDEX&TICKETID=1253&FUN=DETAIL in our browser with a "The webpage cannot be found" error" error.
Our webportal url is https://websiteurl/PORTAL/login.php, which works when surfing to it manually.
How can we fix this? Thanks!
Some of the things we've noticed:
When clicking on the link we sometimes get https://websiteurl/PORTAL/INDEX.PHP and sometimes https://websiteurl/PORTAL/INDEX.PHP?MODULE=HELPDESK&ACTION=INDEX&TICKETID=1253&FUN=DETAIL in our browser with a "The webpage cannot be found" error" error.
Our webportal url is https://websiteurl/PORTAL/login.php, which works when surfing to it manually.
How can we fix this? Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would suggest you also use a HTTP header sniffer such as HTTPLiveHeaders add-on for Firefox, you will be able to spot redirect much more easily and most certainly give you the information that will lead to the resolution of your issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sometimes problems go unnoticed for a while, then between the time the typo was made and the time it's addressed some changes on the system could have occurred (new software version, server migration, configuration modifications, ...)
To me, the all caps you provided was already a red flag, so I'm not entirely surprised you had to modify that.
To me, the all caps you provided was already a red flag, so I'm not entirely surprised you had to modify that.
ASKER
Found the problem by the hint jausions gave with the mentioning of CAPS.
ASKER