omniture_client 0.1.0 → 0.1.3

data/README.markdown

@@ -38,6 +38,12 @@ As well as the omniture.yml you need to also add the `app/reporters` directory t
       config.gem "omniture_client"
     end
 
+Lastly, you need to specify which of your controllers you want to track. In most cases you will want to track all controllers so add this line to your application controller:
+		# app/controllers/application.rb
+		class ApplicationController < ActionController::Base
+			reports_to_omniture
+		end
+
 ### View
 The view code is straight foward. This is img tag is what actually sends the information to Omniture. It should probably be the last element in the body tag.
     
@@ -54,6 +60,10 @@ The view code is straight foward. This is img tag is what actually sends the inf
 Here is an example of a controller we would like to track:
     # app/controller/movies_controller.rb
     class MoviesController < ApplicationController
+			
+			# Uncomment the next line if it is not in your application controller
+			# reports_to_omniture
+
       def index
         @movies = Movie.all
       end
@@ -174,7 +184,7 @@ You will also need to render the img tag in your views since this is the bit tha
 
 
 ## Javascript Implementation
-A javascript implementation is slightly more obstrusive; however, there are a few extra reports you get access to in the Omniture web tool (ie. click map). So all the server-side code remains the same except for the the variable names. For example, instead of `c1` we use `s.prop1`. To have a javascript implementation, you also have to remove the img tag from your layout and add the reporter variables to the s_code.js.
+A javascript implementation is slightly more obstrusive; however, there are a few extra reports you get access to in the Omniture web tool (ie. click map). So all the server-side code remains the same except for the the variable names. For example, instead of `c1` we use `s.prop1`. To have a javascript implementation, you also have to remove the img tag from your layout and add the reporter variables to the s_code.js. I will use a RJS for this example but you could can handle it a number of ways.
 
     # config/omniture.yml
     development:

data/VERSION

@@ -1 +1 @@
-0.1.0
+0.1.3

data/lib/rails.rb

@@ -27,7 +27,7 @@ module OmnitureClient
 
       def set_reporter
         @reporter ||= begin
-          "#{controller_path.classify.pluralize}Reporter".constantize.new(self)
+          "#{controller_path.classify}Reporter".constantize.new(self)
          rescue NameError
            BasicReporter.new(self)
          end        

data/omniture_client.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{omniture_client}
-  s.version = "0.1.0"
+  s.version = "0.1.3"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Alexandru Catighera"]
-  s.date = %q{2009-12-15}
+  s.date = %q{2010-01-12}
   s.email = %q{alex@patch.com}
   s.extra_rdoc_files = [
     "README.markdown"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: omniture_client
 version: !ruby/object:Gem::Version 
-  version: 0.1.0
+  version: 0.1.3
 platform: ruby
 authors: 
 - Alexandru Catighera
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-12-15 00:00:00 -05:00
+date: 2010-01-12 00:00:00 -05:00
 default_executable: 
 dependencies: []