Closed GoogleCodeExporter closed 8 years ago
tried it with different sites, problem still happens.
sites also have other CSS feeds that are working properly
Original comment by boris....@gmail.com
on 5 Jul 2011 at 10:59
Hi Boris, have you been able to debug the script at all in IE? See
http://coolwebdeveloper.com/2009/03/fantastic-new-javascript-debugging-tool-with
-ie-8-and-its-list-of-features-hard-to-live-without/.
If you don't already have this turned on you should also enable client-side
JavaScript debugging before using the debugger - see
http://blogs.alfresco.com/wp/kevinr/2010/04/07/developer-tips-for-alfresco-share
-33/
Original comment by will.abson
on 5 Jul 2011 at 1:54
Experiencing the same bug.
Firefox works fine, but IE 8 hangs/freezes
Bug reproduced using:
Alfresco Enterprise v3.4.1 (304) schema 4201
Same bug also reproduced in:
Alfresco Community v3.4.0(d 3370) schema 4113
Original comment by peter.a....@gmail.com
on 6 Jul 2011 at 3:18
@Will, have you tested this against an ie 8 browser?
Original comment by peter.a....@gmail.com
on 6 Jul 2011 at 3:42
@Will , i am not able to start debugging in IE since it friezes the moment i go
to the page that has TwitterFeed.
Any solution?
Original comment by boris....@gmail.com
on 7 Jul 2011 at 10:40
Same here, we get a nasty Browser Not Responding and finally need to force a
close of ie ;)
Looking forward to a fix.
@Will, if I can assist in any testing please let me know.
Original comment by peter.a....@gmail.com
on 7 Jul 2011 at 12:59
Reproduced in my local IE7 install. The dashlet worked previously in this
browser, so obviously something has changed.
Original comment by will.abson
on 7 Jul 2011 at 5:25
That's what I think too.. I had it working previously if I remember correctly.
Btw same behaviour reproduced in the the Twitter search dashlet.
Original comment by peter.a....@gmail.com
on 7 Jul 2011 at 6:49
Fixed in r516 / v0.3.1 file release. The issue was the date format being
returned by Twitter's JSON API is not parseable by Date.parse() in IE (which
operates according to the spec, whereas Mozilla and Chrome are more tolerant).
The client side code now reformats the date strings before parsing them.
This fixes my IE7 install and I assume IE8 as well. It would be great if
someone could verify this as I don't have an IE8 install here.
Original comment by will.abson
on 7 Jul 2011 at 10:57
hmmm... i tried deploying v0.3.1 and still the same happens.
did i need to do something first? remove v.0.3 somehow?
Original comment by boris....@gmail.com
on 8 Jul 2011 at 6:55
No problem..
I'll test it against
Alfresco Enterprise v3.4.1 (304) schema 4201
Alfresco Community v3.4.0(d 3370) schema 4113
Original comment by peter.a....@gmail.com
on 8 Jul 2011 at 8:23
Tested dashlet on personal dasboard and site dashboard.
v0.3.1 fix validated against
Alfresco Enterprise v3.4.1 (304) schema 4201
Alfresco Community v3.4.0(d 3370) schema 4113
Thanks Will! Could you apply this fix for the Twitter Search dashlet too?
@Boris,
1. remove old jar from shared\lib
2. put in the new one.
3. restart your alfresco service.
4. hasta la pasta... it should work.
Original comment by peter.a....@gmail.com
on 8 Jul 2011 at 8:36
Thanks, Peter. I have another issue open for the search dashlet, so I'll deal
with this one at the same time.
Original comment by will.abson
on 8 Jul 2011 at 9:02
Great, its working now, thanks to everyone
Original comment by boris....@gmail.com
on 8 Jul 2011 at 10:48
I cannot reproduce this issue with the Twitter Search dashlet.
Furthermore, if there is an issue there then it is unconnected with this one,
since Twitter's search API DOES return dates in the correct format, and even if
it did not, the Search dashlet renders the tweets markup in the web-tier rather
than in the client-side code.
Note I am currently refactoring the Search dashlet to use client-side
rendering, but based on the latest Twitter Feed dashlet code, so the fix in
this issue will applied here also.
If there is an issue with the Search dashlet, please file a new issue.
Original comment by will.abson
on 8 Jul 2011 at 12:00
Indeed, twitter search has a different behaviour. IE8 doenst stop responding
but throws an error.
Created a new issue:
http://code.google.com/p/share-extras/issues/detail?id=38
Original comment by peter.a....@gmail.com
on 8 Jul 2011 at 12:54
Original issue reported on code.google.com by
boris....@gmail.com
on 5 Jul 2011 at 10:30