So before I get in this, I like the ideas of
1) place a weighted position like the Digg module to position
2) different displays for summary and full node view

So this is installed in the proper place sites/all/modules, yet it seems to run, but not really. It keeps showing a question mark and keeps wanting to dump me off on their error page (http://tweetmeme.com/about/fail).

In the configuration it has my twitter account name, although this is a PERFECT time to state that this needs clarifying...does one put in just your twitter name or http://twiiter.com/twittername or what? Tried all variations and blank, didn't fix the issue

I have 3 different types of content types selected and it does display in each content type.

URL service was left as bit.ly and yes I have an account and I think this module should make allowances for that to add to our bit.ly accounts. (suggestion)

The location is Full View and the style is normal.

So any ideas? It was downloaded today at 5:30 P.S.T.

Comments

sp_key’s picture

Did you manage to get it to work?
I have exactly the same issue

RobLoach’s picture

What is the issue? It seems to be working here: http://www.davidakermanis.com .

sleepingmonk’s picture

Status: Active » Needs review

I was experiencing a similar issue. The widget was only showing "?" and linking to a tweetmeme error page.

The error there told me tweememe was pointing to a page with a redirect, that's why it didn't work. Looking at the generated code I noticed that the url sent to tweememe was https:// instead of http:// which is where the content is viewed.

I assume this has something to do with the secure pages module and how the url() function generates the url in the tweetmeme module.

So essentially tweetmeme is getting a https:// which is redirecting to http:// because of the secure pages module. Since in my case, I'd only ever want tweetmeme to appear on http:// pages, forcing the url being sent to tweetmeme to be http:// solves my problem.

I would think this would be typical for most use cases but hard coding it into the module would break in the case that someone wants to put tweetmeme on a https:// page, what I did is probably not the best solution.

To do what I did, change line 186 in tweetmeme.module:

FROM:

    $url = url('node/' . $node->nid, array('absolute' => TRUE));

TO:

    $url = str_ireplace('https://', 'http://', url('node/' . $node->nid, array('absolute' => TRUE)));

I'd like to see a better fix in the next update so I don't have to hack the next version too. I'm happy to help code if someone has better suggestions.

Thanks!