Hello,
I hope you are doing well.
I have installed this module a while back and it has repeatedly worked and not worked without any specific pattern I can determine. Sometimes the button will appear and work well, allowing me to tweet out the node and tracks the number of times it's shown up flawlessly. However randomly, and this is becoming most of the time, the button is not there. Doesn't matter if I use Firefox, IE, or Chrome, it doesn't show up. It's also not invisible -- the text rearranges itself to cover that area.
Has anyone else dealt with this?
Thank you.
Comments
Comment #1
corbacho commentedHi,
Do you use it in nodes (enabling in the settings) as a block, or as a CCK field?
Comment #2
TheProf commentedHello,
I am using it in nodes.
What do you think is happening? Is there more information I can provide you to help assess it?
Thank you.
Comment #3
corbacho commentedCan you check that happens for admin or anonymous users ?
Can you check the source code of the page to see if it's present the html markup of the button *and* the javascripts of topsy present in the page? (it's easier if I can check it, if it's possible put your web here)
Comment #4
TheProf commentedHello,
The problem is both for the anonymous user as well as when I am logged in as administrator. The site is www.bishopangaelos.org -- you'll see another Twitter module that I put in to try to rectify the situation but I would like the Topsy Retweet module to be the one I use instead of that one. Please let me know if you need specific levels of access to the site to help debug. The retweet butto usually shows up directly to the right of that blue twitter button you now see.
Thank you.
Comment #5
corbacho commentedHi, yes, I saw the topsy button the first time.. then not anymore after refreshing. I see that the HTML markup (the placeholder were will be the button) is there, and the Javascript too.. so I guess could be a problem from Topsy ?
I saw that the scripts also has a "pagespeed" key, I suppose you have enabled the apache module of google, I don't know if that could affect. I don't think so.
Sorry I can help you anymore, but it seems that the module does what has to do. I might be wrong, but it's the Topsy scripts (or cdn servers) that are not working properly?
I recommend you to use the official button to avoid problems.
Comment #6
TheProf commentedHello,
Thank you for taking the time to look at the site.
I can try to deactivate the Google module and see if that makes a difference.
If there is a problem with Topsy do you recommend I contact them to see if they can help -- is that something they would do?
I have tried the official button (you can see it next to the Topsy one) but it is having it's own technical problems unfortunately.
Thank you.
Comment #7
corbacho commentedFyi, this module was a port of the Topsy's plugin http://wordpress.org/extend/plugins/topsy, that mainly one of the Topsy's developer created. This developer doesn't work anymore there for one year long and the development seems frozen (it was more or less at the same time that Twitter came out with their own Retweet button). So, I wouldn't expect support for this old widget from them...
Comment #8
corbacho commentedTheProf, if you are using this module still, notice that has been deprecated and Topsy will discontinue the service on 12th of Feb
Comment #9
TheProf commentedSorry I had missed your note. Yes I moved to a different module. Thank you.