#9

@episod ,
I might have figured it out. It might be about the OS architecture. When you try the above link on 64-bit win7 using browsers such as chrome, firefox, opera the buttons will not load. When you click the link in 32-bit Win 7 using the same browsers the buttons will load.

Could you confirm?
serdar

#10

I’ll introduce this notion to the engineering team and we’ll go from there. Thanks for all the details!

#11

So you have confirmed the problem?
I will be looking forward to hear from you guys about this problem.

thanks.
serdar

#12

I don’t have the environmental necessities to personally confirm the problem but we’ll look into it. Have you considered using Web Intents or the Follow Button instead of @Anywhere?

#13

I need @Anywhere to let the visitors login and tweet thru my app if they want to.

#14

@episode,
Have you had any chance to dig into this issue yet?

#15

@episod,
So, you have not?

#16

Still waiting on this :frowning:

#17

The bug is filed but I have no ETA for a fix. I will ask the engineers and developers to prioritize.

#18

I believe It should be quite important for you guys too.

Thanks.

#19

update:

Tried with firefox 6.0.2. still the same problem. If you try to navigate to this page http://aspspider.info/serdaroo/ you can see the buttons loading in 32-bit win 7, but they are not loaded in 64-bit win 7.

In firebug it says “ReferenceError: T is not defined” for the line “twttr.anywhere(function (T) { …” while T is defied with all the functions like signIn(), User(), one() etc. when debugged on Internet Explorer 9.

#20

Seems like issue is fixed and seems it was fixed by making some part of twitter API go SSL. And that was what I was suspicious about anyway.

#21

Apparently the issue is solved. I just checked and everything works just fine in all major browsers. What I believe is issue has been solved by making some part of twitter API go SSL.

#22

Apparently the problem has been solved. I believe issue is solved by making some part of twitter API go SSL.

#23

Apparently the problem has been solved. I believe issue is solved by making some part of twitter API go SSL.

#24

j’ai vu le problem maes pour la soulution j’ai rien compris…

#25

I intercept the Twitter response and in case of errors show, but I get twttr and twttr.errors, as undefined in IE8 and Firefox. Kindly let me know the solution for this.

#26
#27
#28