The previous developer has provided the following advice as to how I can identify the error, however could someone clarify how I execute the first step he has suggested (creating a test URL string using PAW) as this isn’t something I’ve done before and want to make sure that I’m doing it correctly so I can rely on the output of PAW to be accurate.
His advice is as follows:
"Assuming nothing has been done to the Lucee server that generates the PDFs, I would start by tracing back to identify where the problem lies. I would manually create a test URL string that submits the form on referral[dot]wyfms[dot]co[dot]uk and see what the output is, using the JS that’s in the HTML form submission code. You could use something like Paw to assist you with this if its something you’re not familiar with.
That would be the first port of call as its injecting the homepage HTML into the ‘done’ message via Ajax upon the form submission, suggesting there’s an issue with the output of the form, and rather than showing an error its defaulting to forwarding to the homepage.
Given that the Lucee server has never fallen over before when there’s been no changes to it or the code its executing I suspect its something simple but I would try manual form submission first to try to pin down any error messages first. This would also ensure that no DNS or IIS changes have been made that make the Lucee server on referral[dot]wyfms[dot]co[dot]uk not to function. Ideally you want to trigger a Lucee error to see that its active. These are a distinct mustard colour.
Another useful tool is Charles that acts as a web proxy to see what’s going on with Ajax scripts that are being executed and can decrypt SSL when configured correctly but try the above first."
Any help would be much appreciated.