Archive for the ‘Wordpress’ Category
Hell has frozen over! Blogger is rolling out a new backend. On second thoughts, it is only getting a bit chilly out here, but it certainly ain’t cool enough for things to freeze over. At least not yet. Apparently, the greatest of the changes is in a place where the end user, like you and me, don’t see much of. Blogger is going off the static publishing set up (one where it would pick up content from its database and spit out static HTML and XML files based on the templates and settings you had specified) and moving to a new set up where all the content is served dynamically (the way in which WordPress blogs functions now).
The immediate change you’ll get to see is a top bar, quite similar to wordpress.com once again, that will show you as logged in and also display other useful information, if you are logged in. Behind the scenes, and I am guessing here, the entire operation would now move to an application server (probably the same server that handles the posting/editing backend) from the old set up which was probably serving a directory of files based on the host header. The other significant change is the authentication part, for which you can now use your Google account (for new blogs, not for existing blogs) or your old Blogger account. The logic there is quite mixed up and needs a lot of work.
That said, the new beta is a complete dud compared to WordPress.com. The interface is still the dated, clunky one and true to the beta label, some of the stuff is broken, like the new WYSIWYG layout editor that was spewing out Ajax debug information on to my screen when it was not functioning as intended. Access control is nice, but I did not see the option for controlling access per post and determining access on the blog level is not a fun thing to do.
The good points? Well, the archive links are laid out much better now and there are Atom feeds for posts and comments (per post too) now. There is also something called “labels”, which looks like a bastard child that resulted from a love making session between tags and categories. Pretty nice, but once again it is something they should have had yesterday.
But someone really has to get some new default templates into the system pretty soon. I am sick of seeing the same 10 all over the place. And the upgrade itself is symptomatic of how Google treats Blogger, more like a stepchild than as a product that deserves a whole lot more of attention and resources allocated to it. Yeah, I know, it is not easy to roll out features for a framework that supports a huge number of users, compared to something like wordpress.com that is new and had a clean sheet of paper to start with. But it can’t be that difficult either. After all, it is all just a data, pulled in and out of database servers and presented on web servers.
I had written earlier about how it was impossible for me to change the default post category in WordPress.com. Well, there is actually a way, but it is in the wrong place, if you ask me. To change your default post category, move on over to the Options >> Writing tab and change the settings there.
Okay, I do know that all of you read a lot and I am quite happy about the fact. But please stop polluting your main blog feed with your Delicious subscriptions. I am sick of going through feeds that often have nothing else but endless bulleted lists of “links for blah-blah-blah”. If I want to know what you are bookmarking, I’d subscribe to your Delicious feed, not your blog feed. Thank you.
For a couple of days (or a day?) I had seen the WordPress.com blogs being served out of both the Textdrive/NextLevel San Diego DC and the Layered Tech DC in Dallas and was quite impressed that Matt had stuck to his word in delivering us the dual-pronged solution to WP.com’s availability woes.
Today, I see that the Textdrive/NextLevel DC has disappeared from the IPs that resolve to the generic WP.com blogs. The official WordPress.com blog still resolves to the old block of IPs. I guess they are still working on it, but it was surely nice to seven IPs resolving to your blog URL.
In other WP.com related quirky behaviour, I am getting strange errors in posting to the blog using the Performancing extension. The entries do get posted, even if the error says something to the effect of not being able to find the XML-RPC endpoint to use the WP API. Anyone else is getting the same problems?
Is there some way by which I can change the default category in WordPress? I used to remember that option being there but I can’t seem to change my default one in this installation, which is quite distasteful as I have my default one set to ‘Music’ by mistake and can’t change it now.
I am giving the Performancing extension for Firefox another spin, driven by the fact that I want something easy to post to this new blog and nothing else really worked. Wbloggar is an old friend, but I did not want to run another application just to be able to blog. I have really sold my soul to Firefox. Sob.
Another reason is the fact that they have blocked access to all the Blogspot and Blogger domains and subdomains for reasons that are now widely known, at least in the media circles of India. So it is now a combination of Bloglines and GreatNews all over again and the nightmares of keeping the feeds synced. Yes, the sysadmins do know that I blog and so on, one of the perks of being an eccentric geek, I guess.
What better way to start this off than with a rant against WordPress? I used to have another blog here, into which I made the mistake of importing my old Blogger.com entries. Now, there were some 500 plus of them and I wanted them off it, which was impossible because in WP you have to delete the posts one-by-one. Not a good scenario.
So I deleted the blog and started fresh. I lost a bit of content which was there only on the WP blog. But hey, you learn new things everyday.