hideSuperfishUl: function() {
            var e = a.op,
            d = (e.retainPath === true) ? e.$path: "";
            e.retainPath = false;
            var c = b(["li.", e.hoverClass].join(""), this).add(this).not(d).find(">ul").fadeOut('fast',function(){
				jQuery(this).removeClass(e.hoverClass)
			});
            e.onHide.call(c);
            return this
        },

Just replace that part of the file, and it should work.

1 – Dump the database and convert it to YAML using this PHP library by Jonathan Franzone.

2 – In your Rails controller, open the YAML file:

oldDatabase = YAML.load(File.open("pathtofile.yml"))

3 – And bam, you have an object of your whole database that you can iterate through and create new rows from through Active Record!

oldDatabase.clients.each do |client|
    Client.create(:name => client.name)
end

Now, to apply my theory and hope it works.

Now, in Moo Invoicing you have invoices and quotes. They’re effectively the same thing, but with some minor differences (due date, payments, etc.) So, instead of having a heap of duplicate code, it makes sense to use the same controllers, models and views for both quotes and invoices. I did pretty much the same thing in CodeIgniter, but rails does much more magic in the background, so to hack it to do your bidding is usually a bad idea and can cause you to loose quite a few “features” the framework provides. Also, being new with Rails, you frequently come to times where you think that what you’re trying to do will be “too advanced” for the framework to handle, and you’ll need to do some actual coding, and more frequently you realize that you’re wrong. Most of the time, the Rails guys have a SUPER easy way out. This is one of those cases – it just wasn’t in any of the Rails guides. So, for my Invoices, I have the following routes:

➜  bundle exec rake routes | grep invoice
                invoices GET    /invoices(.:format)                         {:controller=>"invoices", :action=>"index"}
                         POST   /invoices(.:format)                         {:controller=>"invoices", :action=>"create"}
             new_invoice GET    /invoices/new(.:format)                     {:controller=>"invoices", :action=>"new"}
            edit_invoice GET    /invoices/:id/edit(.:format)                {:controller=>"invoices", :action=>"edit"}
                 invoice GET    /invoices/:id(.:format)                     {:controller=>"invoices", :action=>"show"}
                         PUT    /invoices/:id(.:format)                     {:controller=>"invoices", :action=>"update"}
                         DELETE /invoices/:id(.:format)                     {:controller=>"invoices", :action=>"destroy"}

So, all the routes generated by having the following in your routes.rb file:

resources :invoices

Now, how would I get it so it instead of invoices, it says quotes? ie:

➜  bundle exec rake routes | grep quotes
                  quotes GET    /quotes(.:format)                           {:controller=>"invoices", :action=>"index"}
                         POST   /quotes(.:format)                           {:controller=>"invoices", :action=>"create"}
               new_quote GET    /quotes/new(.:format)                       {:controller=>"invoices", :action=>"new"}
              edit_quote GET    /quotes/:id/edit(.:format)                  {:controller=>"invoices", :action=>"edit"}
                   quote GET    /quotes/:id(.:format)                       {:controller=>"invoices", :action=>"show"}
                         PUT    /quotes/:id(.:format)                       {:controller=>"invoices", :action=>"update"}
                         DELETE /quotes/:id(.:format)                       {:controller=>"invoices", :action=>"destroy"}

Very easily, apparently. Just specify the controller that resources should point to. In your routes.db file:

resources :quotes, :controller=>'invoices'

Yup, Rails is amazing.

➜  ~  identify

Gave the following output:

dyld: Library not loaded: /ImageMagick-6.7.1/lib/libMagickCore.4.dylib
  Referenced from: /usr/local/ImageMagick-6.7.1/bin/identify
  Reason: image not found

In case you were wondering, the “image not found” it refers to is the library mentioned on the first line, not the image your trying to manipulate with ImageMagick. I actually part of the solution to the problem on StackOverflow here. It that ZSH, and subsequently Rails, has the wrong path to the libMagickCore.4.dylib library – the path in the error does look a bit funky.

So, solution was to add the following to my .zshrc (if case you don’t know, it’s in your home directory)

export DYLD_LIBRARY_PATH=/usr/local/ImageMagick-6.7.1/lib

PS. Don’t forget to also add the MAGICK_HOME path, as well as add the the bin path to your PATH. Your paths in .zshrc should look something like the following:

# Customize to your needs...
export MAGICK_HOME=/usr/local/ImageMagick-6.7.1/
export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin/:/usr/local/ImageMagick-6.7.1/bin
export DYLD_LIBRARY_PATH=/usr/local/ImageMagick-6.7.1/lib

Hope this prevents some hair loss for somebody

➜  locomotive  git
zsh: correct 'git' to '_git' [nyae]?

Fixed it by just adding :/usr/local/git/bin/  back to the export path at the bottom of the file:

# Customize to your needs...
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin/

abort: couldn't find mercurial libraries in [/usr/platlib/Library/Python/2.6/site-packages /usr/local/bin /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python27.zip /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC /Library/Python/2.7/site-packages]
(check your install and PYTHONPATH)

Ruby:

PHP:

Nuff said.

As I was saying new places and new things – by new places I’ll probably look into heading to the US in the next year or so. Althought there’s an insane amount of opportunities here, I’m a bit bored of South Africa and what it has to offer at the moment. I’m hungry to get more external experiences and influences.

And that, ladies and gentleman, was my first personal rant on my blog. I hope to now start a PHP vs Ruby flame war here as to generate lots of traffic.

<script src="//ah8.facebook.com/js/conversions/tracking.js"></script>
<script type="text/javascript">
try {
 FB.Insights.impression({
 'id' : 3546876354,
 'h' : '3bc5e0f'
 });
} catch (e) {}
</script>

STEP 1 – Open the theme footer file

Firstly, we need to edit your theme’s footer file, and add in the Facebook tracking Javascript file. The easiest way to do this is to go to Appearance->Editor in your WordPress admin.

Once you have the theme editor open, look for footer.php on the right sidebar. It’s a good idea just to copy and paste the content of this file and save it on your desktop in case something goes wrong.

STEP 2 – Edit the theme footer code

When footer.php has been loaded up, look for the following piece of code:

<?php wp_footer() ?>

And change it to:

<script src="//ah8.facebook.com/js/conversions/tracking.js"></script>
<?php wp_footer() ?>

This will load up the Facebook tracking Javascript functions, so that we can excute them later from Contact Form 7. The reason I put this in the footer is:

1. Because it’s not priority like the rest of your blog, it’ll only load last. This is also in accordance with the Yahoo Best Practices.
2. Because the footer.php is almost always less cluttered with code than the header, it’ll make it easier for less experienced users to insert the code.

After changing the code, click on ‘Update File’. This will save the footer file.

STEP 3 : Add tracking code to Contact Form 7

Right, now that we have the relevant Javascript file in place, we can get Contact Form 7 to execute the tracking code when a user submits the contact form. To do this, we’ll go the settings page of Contact Form 7. This can be found on the left sidebar of the WordPress admin.

When in the settings page, scroll down to “Additional Settings” and click ‘show’.

You now have to reference the code provided by facebook and get the ‘id‘ and ‘h‘ values:

try {
 FB.Insights.impression({
 'id' : 3546876354,
 'h' : '3bc5e0f'
 });
} catch (e) {}

Take these values and put them in the following code:

on_sent_ok: "FB.Insights.impression({'id' : 'id here', 'h' : 'h here'});"

So it resembles like the following:

on_sent_ok: "FB.Insights.impression({'id' : '3546876354', 'h' : '3bc5e0f'});"

You can then take this piece of code and insert into the Additional Settings area you opened. It will then look something like the following:

You can now click ‘Save’ to apply your changes. You should add the code to each of your contact forms, if you have created more than one. And that’s it, your Facebook ad conversion tracking should now work!

NOTE: If you use any caching plug-ins, you should probably empty the cache to take the changes you made into effect.

Edit:

There are quite a few posts around that goes through this step by step, but you can use the Google Analytics Asynchronous library (not the standard one) and track conversions like this:

on_sent_ok:"_gaq.push(['_trackPageview', '/about/contact/shop-thanks']);"

To combine the two, you could seperate the two trackers with a semicolon:

 on_sent_ok:"_gaq.push(['_trackPageview', '/about/contact/shop-thanks']);FB.Insights.impression({'id' : '3546876354', 'h' : '3bc5e0f'});"