I've got this problem. When my page is runnig in Internet Explorer, converter doesn't work. When I hit convert, it spins for a neverending time and nothing. But when my page is runnig in Firefox (or Opera) - everything is OK and converter works well. I can't understand where should be the problem. Can someone help me with it please? Thank you!

Hi,

Can you give me the url so that I can try it? Also, which verison of IE are you using?

Regards,
/kksou

Hi, of course I can. I'll be very glad that you can see it. But the page is not in english language. Your currency converter you can find at the fronpage below in left corner.

url: bpml.sitepages.org

Today I'll go move the site to regular url for client, but still will leave it on at this url I wrote you.

Thank you very much!

And I forgot, it doesn't work with all version of Internet Explorer. I have tested with IE 7 and IE 8 and it was to same. No working.

Hi Robert,

Went to your site and test it. You're right. It works with all browsers but not IE.

I'm not sure what's wrong too on your site.

Interestingly, if you try the following demo:
http://www.kksou.com/php-gtk2/Joomla-samples/Google-Currency-Converter-in-content-item-sample-1.php

It works with IE.

You might want to try it on a fresh install of Joomla first to see if it works at all on your machine.

Regards,
/kksou

Hi Kksou,

did you ever solve this issue? I posted in another branch of the forum as I thought I'd solved this problem, but lo-and-behold I still have the same problem in IE. Works fine in firefox, opera, chrome...

Link to the page on my site: http://www.internchina.org/en/info/prices.

Is there any debugging script I could use, like the script you posted for the google weather widget in another section?

Cheers,

Jamie

Hi Jamie,

I'm using a mac right now. Tried using safari and firefox. Both works fine. Will go and find a machine with IE to test it.

As you can see, the module itself works. It's the browser compatibility issue - an area which I'm not too familiar with.

I will try to write an article to allow you to do some debugging on your side to find out which is the line that causes the problem. Once you know the problem, you might be able to find the solution.

Will let you know once the article is ready, ok?

Regards,
/kksou