Tag Archives: theme

Bland and Insipid Firefox 3 RC1 Experience

Upgrade to Firefox 3 Release Candidate 1 was not as smooth or satisfying as I would have expected it to be. Many of the extensions I use were marked as incompatible and there were no updates available to them for Firefox 3 either.

Firefox 3: Incompatible Extensionsfirefox

The following extensions (I use) are as yet incompatible with this new version of Firefox:

The ones that are most essential to my Firefox experience are PicLens and Tab Mix Plus. Other extensions that came in handy now and then are del.icio.us Buttons, Firebug, MeasureIt, Remove It Permanently, Screen Grab! and Web Developer.

Firefox 3: Working Extensions

The extensions that are compatible and working (after updates) are:

StumbleUpon‘s extension is not working perfectly though, as the images displayed in Google search for rating and other stuff appear broken.

Firefox 3 Default Theme: So Bland!

The theme that I had grown used to, iPox, became an outcast, and I had to settle with the bland default Vista theme of FF 3!

There are only a couple of themes available for Firefox 3; none of them suit me. I ended up applying a theme that merely contained icons, though much better ones than the ones available in the default theme for Vista – Azerty III.

Not Feeling at Home

Although I loved the new features, especially live searches through your bookmarks and history as you type in the address bar, the add to bookmarks, site info, and bookmarks being tag enabled (awesome!), but I didn’t feel at home!

With the bland theme and incompatible extensions, this didn’t seem like the Firefox I had become used to.

I wanted my money back! My Firefox 2 back!

The Little Fiasco: Getting Back to Firefox 2

I had made no backups of any sorts (assumed, wrongfully, that everything would go smoothly), and having overwritten the existing installation of Firefox 2, there was no way to use Firefox 2 but to reinstall it … over Firefox 3!

After reinstalling it, Firefox 2 refused to start up! Just great!

Installed Firefox 3 back, which, thankfully, worked.

Hanging on to Firefox 3 RC1

For now, I have adjusted myself with the bland Firefox 3, hoping and checking for extension and theme updates every now and then.

I am sure most developers are already updating their extensions and themes for Firefox 3. So let’s wait for the updates and the final version to enjoy this vastly improved, feature-packed version of Firefox!

WordPress Feed Issue: Blank line before XML declaration

Gosh! Yet another issue in my WordPress!

This is the third time in less than two weeks that I had to troubleshoot my installation of WordPress 2.5.

This time, however, the issue was not with WordPress itself, but this particular theme that I am using – Illacrimo. The feed for this blog was throwing an error:

XML Parsing Error: xml declaration not at start of external entity
Location: http://www.sawantshah.com/feed/
Line Number 2, Column 1:<?xml version="1.0" encoding="UTF-8"?>
^

I learned about the error when I tried to burn my feed through FeedBurner, which informed me that the feed (RSS XML) was not well-formed:

The URL you entered does not appear to be a valid feed. We encountered the following problem: Error on line 2: The processing instruction target matching “[xX][mM][lL]” is not allowed.

It directed me to Feed Validator to check the feed’s validity, and for sure it was not well formed:

line 1, column 1: Blank line before XML declaration

So what now? Google zindabad! On WordPress Support I found this and this, but I didn’t find any concise and to the point answer there.

I found a concise and workable solution on W3C’s site – check it out.

Why does this error occur?

If an XML declaration (<?xml ... ?>) appears in your feed, it must be the first thing in the feed, before any whitespace.

Unfortunately, with WordPress it seems all too easy for a plugin, a theme, or for your configuration file to contain a blank line. Further compounding this problem, some — but not all — feed readers compensate for this common error, allowing the error to go undetected for quite a while.

What’s the solution?

The solution is to trim/delete any blank lines outside of the <? ... ?> in the PHP code of either the theme files (functions.php) or WordPress files (wp-config.php, wp-rss2.php, wp-atom.php).

I had a blank line between two PHP code sections in the theme’s functions.php file. It was not evident at first, but thankfully, I finally got it to work! Now my feeds are working fine.

So go ahead and subscribe! :D