TOPIC: joscmyslide error code

I'm getting an error in internet explorer "error on page" and it lists "joscmyslide" I'm not sure how to correct this.

can you give us a link to your page?

Send link via PM, thanks

I wondered if you received my PM, otherwise, here you can see the error has something to do with the comments system.

here is a page with it disabled on:
www.gayfresno.com/content/view/260

And here is a page with it enabled:
www.gayfresno.com/content/view/261

The error is not only in IE, but in firefox too. Did you make some changes to the template?

No, it is as-is. I didn't make any changes to it.

But, comments are working? You can post comments on the web site?

Yes, comments are working, but when joomlacomments is enabled, it breaks another feature on the website. When it is disabled, it doesn't. It is that sliding photos along the top, you'll see they don't appear and the error shows up when the comments are enabled.

Here is what Ajay told me yesterday:

it could be due to some other JS in the code which must be clashing

Now it is sure that the code is clashing with your sliding photos. Would you be so kind to turn them off and check if the JS error is still there?

Do you mean turn off the JS features in joomlacomment?

If you turn the javascript features of !jocomment you will not have the nice publishing of comment without reloading the page. I mean turn of the sliding photos and check if the error is still there.

If it is not there the error doesn't appear, but we had a very difficult time finding the photo rotator and I'd really like to keep it. Maybe the incompatibility could be found out to resolve them? If not I understand.

Well, I too believe that both components should work without these problems. The question is: is !joomlacomment working?
You say it is - this JScrpt error is only relevant for developers and since there is no impact on the user this incomparability is not from big importance.

Please give me the link to the slideshow component so I can work locally.

Priority now is joomla 1.5 native. So don't expect this to be fixed in the next few months.