redwallhp

Firstly, what version of Tweetable are you running? The latest has a fix that’s supposed to fix the sidebar widget, which causes the blog to hang when Twitter is down.

Second, autotweet should work so long as Tweetable can make contact with the Twitter API at the time of the posting. (The API has been having issues recently, in the aftermath of the DDoS attack.)

I recently installed Tweetable, version 1.1.4, which is tested through WP 2.8.1.

Actually, it’s tested up the latest release so far. Updating the tested field just slipped my mind. Thanks for reminding me…

The bit you’re looking for is in tweetable.php, around line 251. The function name is tweetable_publish_tweet(). It’s hooked at line 35 with add_action('publish_post', 'tweetable_publish_tweet', 100);

GoCodes will not work if you use the ?p=xx permalinks. You need to have a custom one set up. GoCodes piggybacks off WordPress’s .htaccess rules (which only exist when you set up a different permalink structure such as /2009/08/14/my-post/)

What permalink structure are you using? And what sort of server are you running? Is it Apache or IIS?

Well you might want to try contacting Amazon Associates’ support. I imagine they would have someone who would know there.

I’m running Firefox 3.5.2 at the moment, and I don’t see any purple line. However, I think I know what might be happening…

Try adding this to your theme’s CSS file, clear you cache, and see if the problem goes away when you go back to your site:

#wp125adwrap_2c img { border:0; }
#wp125adwrap_2c a { text-decoration:none; }

Well, first you would want to download the image and upload it to either your own server or an image host.

Then you would get the URL. My guess is that something like this would work:

https://www.amazon.com/[some-codes-and-my-amazon-id];linkCode=ur1

I think that the adid=1MY2NVH68MKAWHMDD6WM& part is probably part of some sort of non-essential statistics thing.

It could have something to do with the Denial of Service attack that has been affecting Twitter. Has it started working again today?

To sum it up, Twitter’s been having problems all day from a Denial of Service attack, and Tweetable’s error handling needs improvement.

“Using querystring URLs is very bad for SEO”

No, it isn’t really. It may have been in the mid-1990s, but modern search engines are more than capable of indexing them.

Also, if you turn off click tracking on your ads, it will put the full URL to the advertiser’s site instead of a querystring redirect. (Just edit the ad entry and uncheck the click counting box.)

“it must be possible with this plugin to avoid them because the maker of this plugin uses it on his own web page, and on his web page the ads do not use querystring URLs, they use directly the URL of the advertiser.”

Actually, I’m not using the plugin on my site at this time. I’m using the BuySellAds.com ad network, because I don’t have a lot of time to sell my own ads these days.

Your sidebars sounds like they’re a bit too narrow to hold the ads side-by-side. You can try reducing the padding around the ads (10px on each side). It might make them fit properly. There’s a note in the plugin FAQ on how to do it.

Go to the Ads->Settings menu. There should be a “Widget Title” field.

@jenbaldwin Go to the Ads->Settings menu. There should be a “Widget Title” field.

Here, replace the bit I posted earlier with this:

.custom125ad {
background-color:#191919;
border:3px solid #191919;
display:block;
height:125px;
overflow:hidden;
position:relative;
width:125px;
float:left;
margin:1px;
}

It appears you’re using the single_ad template tag to add the ad slots in, correct?

You want to add this to your CSS:

.custom125ad {
background-color:#191919;
border:3px solid #191919;
display:block;
height:125px;
overflow:hidden;
position:relative;
width:125px;
}

Then you want to take each of your instances of <?php wp125_single_ad(num); ?> and wrap them like this:

<span class="custom125ad"><?php wp125_single_ad(num); ?></span>