techmgmt

Update 09/07/2022 – Latest Update 1.18 broke the site yet again. 100% chance of an update breaking at least one form in every update for the past year. Is the QA department on holiday permantently?

Thanks for the follow-up. If only the issues could be caught, or even resolved, just by using a staging server (which we do). When fundamentally code changes the way forms process, some of those changes, especially if not part of your changelogs, would be nearly impossible to determine until they are in production. Case in point, Zapier integrations are turned off on staging. Form submits fine, submission details look normal. On production, it was determined that the information Forminator sends to a webhook completely changed. File type fields (application/pdf for instance) were completely removed from the hook. That is one of many examples, but I will include those in the separate email.

The only enabled option was Optimize JS Code. I’ve disabled that and the error still occurs. I did not delete cache when saving that change though, is that required?

I don’t get a 404 when AO is disabled, only when it is enabled.

Yes and it exists. It’s a live chat JS.

const wplc_assets_guid = 'cgk5myJ9Xxcspsjz';
						const callusElements = document.getElementsByTagName("call-us");
						Array.prototype.forEach.call(callusElements, function (callus) {
							callus.setAttribute('assets-guid', wplc_assets_guid);
						});