Hi

Thanks for contacting us. Could you please give me a screenshot of it?

-Regards.

see below. Its just a // issue. probably a typo.

Could you please specify it more? I mean if possible give me a screenvideo of this bug.

I can't. Isn't it enough to be shown evidence of the error and to be told specifically which files contain references to a non-existent file and are therefore generating a 404 error for everyone who uses that particular add-on?

I gave you two files which are being called but do not exist: a 404 error, in other words.

Then I gave you 10 examples of pages where the 404 error occurs as a result of the two files being called that do not exist (ie the CSS file and the JS file).

I do not mind which example you use, but if you want only one then let's take the top one.

If you look at the URL https://xxx.com//components/com_sppagebuilder/assets/css/magnific-popup.css, you can see that there is a // between .com and components. My best guess is that whoever coded the add-on simply made a mistake by adding an extra /. It should be really easy to fix.

Perhaps I have not explained it well enough previously?

Perhaps "Bug report" was too strong a term. "Coding typo" might have been a better description

Ok I will inform our team about it but the link you provided does not work. Could you please send me the correct link?

Just to repeat... ask your developers to fix the double backslash in the URL. That is all

Hi

I have informed our team about this bug, they said it will be fixed in our next update.

Thanks.