I just added the AJAX YUI mod and I think it is great and works perfect in firefox. I tried it in IE6 though, and I can't seem to select any of the widgets to save once I moved them over to the left or right columns. Any thoughts?
the easiest thing is perhaps to throw out that machine, get a mac and then go on a global 'get firefox or get a mac' type campaign...you'll need to quit your job/school to do this ft, but it may be worth it to get all of the users of your elgg site on board with no problems...
daveinboston on Friday, 27 April 2007, 15:55 UTC # |
Sounds like a plan. Now if I can convince the 20,000 people who I want to get onto our elgg powered site, then it's a good plan. I take it no one else is having this problem?
Mike Holzman on Friday, 27 April 2007, 16:00 UTC # |
Hi Mike,
Do you have the latest code? I was the one who wrote the widget code. I had this problem with IE reported to me and fixed the problem some time ago so far as I know.
I think I do. I pulled it off of the link on the plugins page. I think I even tried pulling it from the SVN. Is there a quick way to dig into this and see which version of code is there?
Mike Holzman on Wednesday, 02 May 2007, 23:36 UTC # |
Hi Mike,
The correct source uses mystring.charAt(0) in the Javascript to access characters in strings. The outdated source uses mystring[0] which does not work in IE.
If you find charAt in your source and the code still does not work in IE 6, then you may have found another bug. In which case, I would need a Javascript error message to figure this out as I do not have access to IE 6 (only IE 7 which seems to work fine).
This must be my problem, I can't find mystring[0] at all in the js file under widget. I do have a couple el.id[0] I can try shifting that to el.id.charAt[0] and see if that does the trick.
Mike Holzman on Thursday, 03 May 2007, 16:34 UTC # |
got it. The code in the widget folder had the el.id[0] and not el.id.charAt(0) which did fix it! I think the elgg base code needs to be updated though.
Mike Holzman on Thursday, 03 May 2007, 16:51 UTC # |
mystring was just an example - there were multiple strings with this problem in a previous version of the code - they all should be fixed and were in my last version of the code so far as I know.
I have emailed Ben and Dave to ask them to check this problem out. Thanks for the alert!
| View blog | Archive | Friends' blogs | View all posts
Comments
Hi Mike,
Do you have the latest code? I was the one who wrote the widget code. I had this problem with IE reported to me and fixed the problem some time ago so far as I know.
Kevin,
I think I do. I pulled it off of the link on the plugins page. I think I even tried pulling it from the SVN. Is there a quick way to dig into this and see which version of code is there?
Hi Mike,
The correct source uses mystring.charAt(0) in the Javascript to access characters in strings. The outdated source uses mystring[0] which does not work in IE.
If you find charAt in your source and the code still does not work in IE 6, then you may have found another bug. In which case, I would need a Javascript error message to figure this out as I do not have access to IE 6 (only IE 7 which seems to work fine).
This must be my problem, I can't find mystring[0] at all in the js file under widget. I do have a couple el.id[0] I can try shifting that to el.id.charAt[0] and see if that does the trick.
got it. The code in the widget folder had the el.id[0] and not el.id.charAt(0) which did fix it! I think the elgg base code needs to be updated though.
mystring was just an example - there were multiple strings with this problem in a previous version of the code - they all should be fixed and were in my last version of the code so far as I know.
I have emailed Ben and Dave to ask them to check this problem out. Thanks for the alert!