If you use the site information to select a node page the 301 redirect causes a failure on the landing page for Tweetmeme http://tweetmeme.com/about/fail_redirect . How do we fix this problem?

CommentFileSizeAuthor
#10 tweetmeme-front_page-6.x.patch766 bytesAlexisWilke

Comments

john.oltman’s picture

john.oltman commented
Assigned: Unassigned » john.oltman

I'll take a look this week.

john.oltman’s picture

john.oltman commented
Status: Active » Postponed (maintainer needs more info)

I have the configuration you mentioned above setup here and I'm not seeing any problems:

http://www.openbasin.com/

If you have the site in maintenance mode, or the site is not accessible externally due to DNS not being setup yet, or anonymous users don't have permission to view the site, then you will get the fail notice.

Need more information if you don't think the above applies to you.

AdamJH’s picture

AdamJH commented

It's only on the landing page that this happens. It's totally viewable by random users but it just shows a question mark due to the 301 redirect on the landing page. I've not had this issue on wordpress with similar 301 redirects so it's a bit confusing.

http://www.making8.com/ note the question mark and the error code you get when you click on it. None of the other pages have this issue. Something about the landing page 301 the plugin doesn't like.

john.oltman’s picture

john.oltman commented

I can reproduce this by adding a URL alias from a node page to the front page. Just delete that alias, and use the Site Information page "Default front page" setting to handle that redirect instead of doing it via the alias. That should solve your problem.

john.oltman’s picture

john.oltman commented
Status: Postponed (maintainer needs more info) » Needs review
AdamJH’s picture

AdamJH commented

Is there a way to remove the Tweetmeme from certain pages such as this one?

john.oltman’s picture

john.oltman commented

For your site, you could probably add something like this to your CSS:

#node-1 #tweetmeme_button {display:none;}
AdamJH’s picture

AdamJH commented

That's not going to fix the fact that it's not working properly lol. Works fine on wordpress but not here for the landing page

AlexisWilke’s picture

AlexisWilke commented
Status: Needs review » Active

Note that I have Drupal 6.22 and get the same issue. I had question marks on unpublished nodes. That was fixed a while back.

However, I get a similar problem now.

Adam, have you tested with a brand new site?

I use a URL alias AND the site front page is also indicated in the "Site information" front page (instead of node, I have my aliased node/###).

Could it be that you give TweetMeme the site alias (i.e. mysite.com/alias) instead of the front page? (i.e. mysite.com/) You should test for the front page before sending the page URL anyway and if it is the front page, use the URL base or whatever it's called.

Thank you.
Alexis

AlexisWilke’s picture

AlexisWilke commented
Title: Tweetmeme 301 redirect causes failure » Tweetmeme 301 redirect causes failure on front page
Version: 7.x-1.1 » 6.x-1.x-dev
Status: Active » Needs review
StatusFileSize
new tweetmeme-front_page-6.x.patch766 bytes

There is a patch for D6.

I'm sure it would be easy to port to D7.

Works great for me. 8-)

Thank you.
Alexis Wilke