Dare to Dream? » Rails

Getting around the dreaded Operation Aborted error in Internet Explorer with Ruby on Rails

Mayank Jain (makuchaku) — Wed, 16 Jun 2010 17:17:34 +0000

If you have ever experienced this…

…you know how painful it is to debug and rectify.

This error was so common that Microsoft created a knowledge base (KB927917) article for this. It even has a dedicated explanation at the IE Blog. The error basically is – “HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)”.

While building the Social sharing plugins for AdoMado, we were facing similar problems. Anywhere FB share, Orkut share or Digg buttons were being used, IE was complaining of exactly the same problem. Since social share plugins are the backbone of our community building process, fixing this ASAP was high on my agenda.

NOTE – There was no such problem on any version of Firefox or Chrome.

If you notice the IE blog entry, they mention that

Moving the location of your script block to a child of the body (this usually solves most problems, while allowing the most flexibility in terms of scenarios).

can be a possible solution.

Cool! But how do we reach here? My javascripts were spread all over the place!

First things first… I refactored the code in such a way that all possible usage of problem causing scripts was moved to one single partial. Now error was originating from only one location. The fix, as mentioned on the IE blog – was then straight forward.

In your layout, just before closing the BODY tag, use the “yield” block to render any such javascript – and render all such scripts into this “yield” block.

Here are some screen captures from our codebase…

Notice the “yield :delayed_loading” block…

Yield’ing to delayed_loading block.

If you browse over to our offer – Send Ad Free SMS using IE, you will notice that you see no such error. All the social share plugins render in harmony.
I’ve even thrown in a little jQuery fadeIn magic

Authentication using Google Accounts for your Rails App The methodology is very simple. Redirect the user to grant...
AdoMado… the Next Phase!! Hey everyone!! Last week we embarked on the next phase...

Related posts brought to you by Yet Another Related Posts Plugin.

Learning from the best!

Mayank Jain (makuchaku) — Fri, 12 Feb 2010 04:58:47 +0000

Just bought “Programming Ruby 1.9” from Flipkart.

From For Blog

When I joined IBM ISS UI team and my tech lead suggested that we should start doing things in Rails- and I was prompt enough to pop up a suggestion – “that why don’t we use Python based web app frameworks Django or Turbo Gears (as I had some python experience)”.

All he replied was – “when we are looking for the best framework, why not use the one everyone’s trying to become”.

And hence, the awesome journey to Rails began.
Understanding Ruby better will make it so much more fun.

PS: No disrespect meant to the awesome work being put in by the Python community. Python rocks! So does Ruby!

Location of Rubygems in Ubuntu Jaunty With Jaunty, the location of installed gems has been moved...

Related posts brought to you by Yet Another Related Posts Plugin.

An IDE which suggests best code practices, shows a diff and lets you selectively apply…

Mayank Jain (makuchaku) — Mon, 19 Oct 2009 08:28:08 +0000

NetBeans code modification suggestion

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Programmer Happiness – onroad to Rails3

Mayank Jain (makuchaku) — Thu, 08 Oct 2009 14:25:50 +0000

Medium: www.vimeo.com
Link: www.vimeo.com

Rails 3 Update by Yehuda Katz from Wind City Rails 2009

You just can’t ignore his style of explaining things!

Location of Rubygems in Ubuntu Jaunty With Jaunty, the location of installed gems has been moved...

Related posts brought to you by Yet Another Related Posts Plugin.

Authentication using Google Accounts for your Rails App

Mayank Jain (makuchaku) — Sun, 27 Sep 2009 20:02:15 +0000

The methodology is very simple.

Redirect the user to grant access to your app for a particular Google service.
Once access is granted, use the authentication token to retrieve information related to the user.

I demonstrate this with a very simple & idiotic Sinatra app which actually does nothing intelligent – apart from just outputting first 10 contacts from the user’s address book.

require ‘rubygems’
require ‘sinatra’
require "gdata"
client = GData::Client::Contacts.new
get "/" do
next_url = ‘http://127.0.0.1:4567/app’
secure = false
session = true
authsub_link = client.authsub_url(next_url, secure, session, nil)
redirect(authsub_link)
end
get ‘/app’ do
pp request.env
client.authsub_token = request.env["rack.request.query_hash"]["token"]
client.authsub_token = client.auth_handler.upgrade()
contacts = client.get("http://www.google.com/m8/feeds/contacts/default/full?max-results=5").to_xml
puts contacts
end

More information about using GData is available at http://code.google.com/apis/gdata/articles/gdata_on_rails.html

Example scenarios this can be used?

Allowing people to login into your app with their existing google account.
Accessing user data with user’s permission
Signing up for your app using Google account information

Happy Hacking!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Location of Rubygems in Ubuntu Jaunty

Mayank Jain (makuchaku) — Sun, 27 Sep 2009 14:19:49 +0000

With Jaunty, the location of installed gems has been moved to /var/lib/gems while it was /usr/lib/ruby in releases before.
Please follow http://intertwingly.net/blog/2009/04/25/Rails-on-Jaunty for more on how to rectify the problem that might arise.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.