Shape 5

Joomla Club Extensions => Frontpage Display Version 3 - Club => : crbadbeat May 09, 2015, 01:05:17 PM



: Errors When Published
: crbadbeat May 09, 2015, 01:05:17 PM
Hello,
I have installed this module on this site: http://wallysbilliards.com and I am getting these errors when it is published:

Resource interpreted as Image but transferred with MIME type text/html: "http://wallysbilliards.com/".
(index):814 Uncaught ReferenceError: s5_fd_images_loaded is not defined

I have done a lot of searching but cannot figure this one out. Can you please help?

Thanks!


: Re: Errors When Published
: mikek May 11, 2015, 07:15:57 AM
Hello,

I am not seeing that error on your page and the module is loading. Were you able to correct this already?


: Re: Errors When Published
: crbadbeat May 11, 2015, 03:16:10 PM
Hello,
I was not able to get this corrected. If you load the page in Chrome and hit F12 and look on the console tab, you will see the error. On a desktop computer it appears to acts correctly even though it is showing the error. On my iPhone, when you try to scroll the page, it freezes up up to 20 seconds with this module published. Then when it unfreezes and you scroll again, it will move down the page a bit and freeze again.

Kind of strange.

:)


: Re: Errors When Published
: mikek May 12, 2015, 08:19:48 AM
Hello,

I've checked your site on two different machines and I am not seeing any error messages. I am also checking in Firebug on Firefox. The only error message showing in Chrome is:

Uncaught SyntaxError: Unexpected token o

But that gives no indicator as to what script is causing that, and it's called at line 1. If it was a problem with the module's js it would indicate the exact file name.

I do not have an iPhone to check with, but I checked on an Android and there are no freezing issues, and we don't have any reports of this.

Have you tried on a second machine?


: Re: Errors When Published
: crbadbeat May 12, 2015, 10:04:47 AM
It makes no sense that you wouldn't see the error posted in the screen shot, I see this error on multiple computers. If I unpublish this module, the errors go away, so it is certainly this module.

Whatever, I guess I will use another companies module and scrap this one.


: Re: Errors When Published
: mct2002 June 15, 2017, 01:26:24 PM
I am experiencing the same problem on my website.  When I publish the module I receive the following error message "Uncaught ReferenceError: s5_fd_images_loaded is not defined at HTMLImageElement.onload ((index):640)" although the index number changes for each error message.  I am finding these errors using the Console tool under Google's Developer Tools.  When I unpublish the module these errors go away.  I have 6 images as part of my module and 6 error messages from Google's Developer Tools.

The module itself appears to be working fine on desktop and android devices apart from the error messages.  I have tried doing a fresh install of the module, but it didn't make a difference.

I am including a screenshot of the Google Developer's Tools with and without the module published.  You can view my site at https://www.custominternet.biz.


: Re: Errors When Published
: mikek June 17, 2017, 06:40:56 AM
Hello,

It doesn't appear that you are using the module in the way it's intended. You are using it more as an image rotator and the the boxes below the main image are absent on your site; which are intended to be there and could cause javascript errors without them present. I would suggest using our Image and Content Fader module instead which is designed for image rotation:

https://www.shape5.com/product_details/free_extensions/s5_image_and_content_fader.html


: Re: Errors When Published
: mct2002 June 19, 2017, 12:44:26 PM
I didn't realize the boxes at the bottom of the module were not optional.  I changed to the Image & Content Fader and that resolved the error messages I was receiving.  Thank you!

Just FYI, I did get an error message after the switch to the Image & Content Fader saying that the loading-bar-black.gif could not be found.  I downloaded and installed the module again with the same results.  I was able to fix the problem by copying the image into the module's image folder from and older version of the module.  But I thought you might want to have someone look into this.

Thanks again!