Displaying Amazon "iframe" Ads Without The Scroll Bar In Scribefire

As I have mentioned previously, a scroll bar will appear when I place an Amazon "iframe" ad in Scribefire Chrome for Opera, resulting in the ad not being displayed as it should while editing, and indeed after publishing, while in "Edit Visually" mode.

After having gathered enough courage to peek at Scribefire's source code, I am glad that I have found a fix to this problem (see Note 1 below on extracting the source code from the Scribefire Extension file "scribefire-4.oex").

This is what I did to remove the scroll bar. I appended additional parameters to line 964 in the file "events.js" - they are actually just parameters found in the code given by Amazon that were not defined in this line. Below is how the line looks before modification:

extended_valid_elements : "iframe[title|width|height|src|frameborder|allowfullscreen]",

My modified line now reads:

Inserting Amazon Affiliate "iframe" Ads With Scribefire

Scribefire Classic Fails With "iframe" Ads

I use Scribefire Classic (version 4.0.0.1) on Firefox (version 3.6.8) to compose my blogs. I tried inserting three Amazon affiliate "iframe" ads into my blog post last week and failed. Not only did the ads not get displayed in the Scribefire's "Rich Editing" tab, but upon publishing and accessing my blog post from Opera desktop and Opera Mini, only one ad was displayed instead of three.

When I looked at the HTML source (by selecting "source" when I right click in Opera desktop), I noticed that the "iframe" tags in my Amazon ads were modified by Scribefire upon publishing. The closing tag "</iframe>" was dropped and the opening tag was modified by making it self-terminating for each inserted ad. For example, the tag code provided by Amazon was:

Revoking Picasa Access Rights From Scribefire

I do not use Scribefire, a free Mozilla Firefox add-on offline blog editor, for uploading my blog pictures to Picasa Web Albums anymore. Instead, I am now using Picasa3 Desktop. Uploading pictures via Scribefire is a little rigid and the pictures' file names do not get set upon a successfully upload. In contrast, Picasa3 Desktop has more options - like selecting a destination web album to upload to for example - and I do not lose my pictures' file names.

The right thing to do, since I do not use it anymore, is to revoke all access rights that I have granted to the website www.scribefire.com previously. After some searching, I finally found the URL for doing this - which is at the Google "Account Overview" page, and not at Picasa Web Albums website. Yes, a little misleading.

Scribefire Can Only Retrieve The Last 25 Posts

It seems that there is a limit to the number of posts that ScribeFire (an offline blog editor) can retrieve from my blog. All that I can see is just the last 25 posts when ScribeFire connects to my blog. For the moment, I will have to use the online blog editor at Blogger for any updates to my older blog posting that ScribeFire does not retrieve. This defeats my purpose of using an offline blog editor in the first place. I have been happily using ScribeFire for about 8 months, but now I am disappointed.

It is a pity really. Although it is no longer supported, I find ScribeFire Classic version 4.0.0.1 for Firefox to be quite a decent offline blog editor - and to be the best among all versions of ScribeFire. I am using ScribeFire on Firefox version 3.6.8.