Strange frontend.js issue after last update

There hasn’t been any change in how the frontend.js file is being loaded, in over two years. I can’t say why the stats show that file as the visited URL, the fact that it appears after the latest update is most likely a coincidence.

I would suggest to check with the authors of the stats tool, they should be able to check why that JS file is tracked, instead of the actual URL.

Hi and thanks for your quick reply.

I have updated the plugin on three different sites and the error is displayed on all three sites after updating the plugin. There seems to be an issue.

Could not the following fix in the latest update have something to do with it:
“Fixed error that could occur when both the Aelia Foundation Classes and the embedded AFC were loaded on a site.”?

Thanks again

Dale

I don’t think that could be an issue. That fix is something that happens behind the scenes, to prevent the embedded AFC framework from causing conflicts with the standalone AFC framework, when the latter is installed. It’s a simple check like “if one framework exists, don’t load the other”. That doesn’t affect the loading of the frontend.js file. That part is unaltered, and the file is loaded like it has always been.

I can’t say why the tracking scripts now see a JS file as the actual visit. If you can find out why that is seen as a visit, we can see if we can help addressing that issue.

It is driving me nuts ?? and I cannot understand what is causing it.

What is really strange is that the url in the stats to js of the plugin does not even exist, it is completely wrong. It does not even point to where the js is stored!

The correct url to the js is /wp-content/plugins/woocommerce-eu-vat-assistant/src/js/frontend/frontend.js

But the url in the stats is
/wp-content/plugins/wc-aelia-foundation-classes-embedded/src/js/frontend/frontend.js

This url is completely wrong and does not exist but it must be generated somewhere most probably the plugin.

Does this give you any clue as what is wrong?

Thanks a lot in advance!

• This reply was modified 6 years, 1 month ago by dalesue74.

The URL /wp-content/plugins/wc-aelia-foundation-classes-embedded/src/js/frontend/frontend.js is indeed incorrect. The correct URL for that file should be /wp-content/plugins/woocommerce-eu-vat-assistant/src/embedded-framework/wc-aelia-foundation-classes-embedded/src/js/frontend/frontend.js.

I can’t see how the visits could be tracked for that file, as opening it would return error code 404. That’s an issue that should be addressed. If you can get in touch using our contact form (https://aelia.co/contact), I can ask to prepare a build with a patch for that error and send it to you as soon as it’s ready, so you can also check if it happens to make a difference with the tracking.

Update
The issue was solved by fixing the incorrect URL in version 1.9.4.190109.