spree_mercado_pago_payment_method 0.1.1 → 0.2.0

data/app/services/mercado_pago/process_notification.rb

@@ -0,0 +1,54 @@
+# Process notification:
+# ---------------------
+# Fetch collection information
+# Find payment by external reference
+# If found
+#   Update payment status
+#   Notify user
+# If not found
+#   Ignore notification (maybe payment from outside Spree)
+module MercadoPago
+  class ProcessNotification
+    # Equivalent payment states
+    # MP state => Spree state
+    # =======================
+    #
+    # approved     => complete
+    # pending      => pend
+    # in_process   => pend
+    # rejected     => failed
+    # refunded     => void
+    # cancelled    => void
+    # in_mediation => pend
+    # charged_back => void
+    STATES = {
+      complete: %w(approved),
+      failure: %w(rejected),
+      void:    %w(refunded cancelled charged_back)
+    }
+
+    attr_reader :notification
+
+    def initialize(notification)
+      @notification = notification
+    end
+
+    def process!
+      client = ::Spree::PaymentMethod::MercadoPago.provider
+      op_info = client.get_operation_info(notification.operation_id)["collection"]
+
+      if payment = Spree::Payment.where(identifier: op_info["external_reference"]).first
+        if STATES[:complete].include?(op_info["status"])
+          payment.complete
+        elsif STATES[:failure].include?(op_info["status"])
+          payment.failure
+        elsif STATES[:void].include?(op_info["status"])
+          payment.void
+        end
+
+        # When Spree issue #5246 is fixed we can remove this line
+        payment.order.updater.update
+      end
+    end
+  end
+end

data/app/views/spree/checkout/payment/_mercadopago.html.erb

@@ -1 +1,15 @@
-<img src="http://imgmp.mlstatic.com/org-img/banners/ar/medios/575X40.jpg" title="MercadoPago - Medios de pago" alt="MercadoPago - Medios de pago" width="575" height="40"/>
+<script>
+  MercadoPago.paymentMethodID = "<%= payment_method.id %>";
+</script>
+
+<div class="row">
+  <div class="twelve rows alpha omega">
+    <img src="http://imgmp.mlstatic.com/org-img/banners/ar/medios/575X40.jpg" title="MercadoPago - Medios de pago" alt="MercadoPago - Medios de pago" width="575" height="40"/>
+  </div>
+</div>
+
+<div class="row">
+  <div class="twelve rows alpha omega">
+    <%= link_to I18n.t(:make_payment, scope: :mercado_pago), mercado_pago_checkout_path(payment_method_id: payment_method.id), method: :post, class: "button primary" %>
+  </div>
+</div>

data/config/locales/en.yml

@@ -1,13 +1,4 @@
 en:
-  mp_authentication_error: "It was not possible to authenticate with Mercado Pago"
-  mp_preferences_setup_error: "Couldn't send order preferences to Mercado Pago"
-  mp_payment_success: 
-    Your payent with Mercado Pago was successful.
-
-    Please take into account that this payment may take some hours to reflect
-    on this site.
-  mp_payment_failure: "Your payment could not be processed by Mercado Pago"
-  mp_payment_pending: 
-    Your order has been placed but your payment is still pending we will ship
-    your order and contact you as soon as the payment is processed"
-  mp_invalid_order: "The specified order is invalid"
+  mercado_pago:
+    make_payment: "Pay with Mercado Pago"
+    authentication_error: "It was not possible to authenticate with Mercado Pago"

data/config/locales/es.yml

@@ -1,14 +1,4 @@
 es:
-  mp_authentication_error: "Hubo un error al realizar la autenticación con Mercado Pago"
-  mp_preferences_setup_error: "Hubo un error al enviar sus pedido a Mercado Pago"
-  mp_payment_success: 
-    Su pago con Mercado Pago se ha efectuado con éxito. 
-
-    Por  favor tenga  en cuenta  que  el estado  de su  pago puede  tardar
-    algunas  horas en reflejarse en este sitio.
-  mp_payment_failure: "Su pago no pudo ser procesado por Mercado Pago"
-  mp_payment_pending: 
-    Su orden fue procesada con éxito aunque su pago aún se encuentra pendiente.
-
-    En cuanto su pago se concrete su pedido será finalizado.
-  mp_invalid_order: "La órden especificada es inválida"
+  mercado_pago:
+    make_payment: "Realizar pago en Mercado Pago"
+    authentication_error: "Hubo un error al realizar la autenticación con Mercado Pago"

data/config/routes.rb

@@ -1,8 +1,6 @@
-# -*- encoding : utf-8 -*-
-Spree::Core::Engine.routes.draw do
-  scope "/mercado_pago", controller: :mercado_pago do
-    get :success, as: :mercado_pago_success 
-    get :pending, as: :mercado_pago_pending 
-    get :failure, as: :mercado_pago_failure 
-  end
+Spree::Core::Engine.add_routes do
+  post '/mercado_pago/checkout', to: "mercado_pago#checkout", as: :mercado_pago_checkout
+  get  '/mercado_pago/success', to: "mercado_pago#success", as: :mercado_pago_success
+  get  '/mercado_pago/failure', to: "mercado_pago#failure", as: :mercado_pago_failure
+  post '/mercado_pago/ipn', to: "mercado_pago#ipn", as: :mercado_pago_ipn
 end

data/lib/generators/spree_mercado_pago_payment_method/install/install_generator.rb

@@ -3,13 +3,18 @@ module SpreeMercadoPagoPaymentMethod
     class InstallGenerator < Rails::Generators::Base
 
       def add_javascripts
-        append_file 'app/assets/javascripts/store/all.js', "//= require store/spree_mercado_pago_payment_method\n"
-        append_file 'app/assets/javascripts/admin/all.js', "//= require admin/spree_mercado_pago_payment_method\n"
+        append_file 'vendor/assets/javascripts/spree/frontend/all.js', "//= require spree/frontend/spree_mercado_pago_payment_method\n"
+        append_file 'vendor/assets/javascripts/spree/backend/all.js', "//= require spree/backend/spree_mercado_pago_payment_method\n"
       end
 
       def add_stylesheets
-        inject_into_file 'app/assets/stylesheets/store/all.css', " *= require store/spree_mercado_pago_payment_method\n", :before => /\*\//, :verbose => true
-        inject_into_file 'app/assets/stylesheets/admin/all.css', " *= require admin/spree_mercado_pago_payment_method\n", :before => /\*\//, :verbose => true
+        frontend_css_file = "vendor/assets/stylesheets/spree/frontend/all.css"
+        backend_css_file = "vendor/assets/stylesheets/spree/backend/all.css"
+
+        if File.exist?(backend_css_file) && File.exist?(frontend_css_file)
+          inject_into_file frontend_css_file, " *= require spree/frontend/spree_mercado_pago_payment_method\n", :before => /\*\//, :verbose => true
+          inject_into_file backend_css_file, " *= require spree/backend/spree_mercado_pago_payment_method\n", :before => /\*\//, :verbose => true
+        end
       end
 
       def add_migrations
@@ -17,12 +22,12 @@ module SpreeMercadoPagoPaymentMethod
       end
 
       def run_migrations
-         res = ask 'Would you like to run the migrations now? [Y/n]'
-         if res == '' || res.downcase == 'y'
-           run 'bundle exec rake db:migrate'
-         else
-           puts 'Skipping rake db:migrate, don\'t forget to run it!'
-         end
+        res = ask 'Would you like to run the migrations now? [Y/n]'
+        if res == '' || res.downcase == 'y'
+          run 'bundle exec rake db:migrate'
+        else
+          puts 'Skipping rake db:migrate, don\'t forget to run it!'
+        end
       end
     end
   end

data/lib/spree_mercado_pago_payment_method.rb

@@ -1,3 +1,4 @@
 # -*- encoding : utf-8 -*-
 require 'spree_core'
+require 'spree_frontend'
 require 'spree_mercado_pago_payment_method/engine'

data/lib/spree_mercado_pago_payment_method/engine.rb

@@ -1,4 +1,3 @@
-# -*- encoding : utf-8 -*-
 require 'spree_core'
 
 module SpreeMercadoPagoPaymentMethod
@@ -15,7 +14,7 @@ module SpreeMercadoPagoPaymentMethod
     end
 
     initializer "spree_payment_network.register.payment_methods" do |app|
-      app.config.spree.payment_methods += [PaymentMethod::MercadoPago]
+      app.config.spree.payment_methods += [Spree::PaymentMethod::MercadoPago]
     end
 
     config.to_prepare &method(:activate).to_proc

data/lib/tasks/mercado_user.rake

@@ -1,4 +1,3 @@
-# -*- encoding : utf-8 -*-
 namespace :mercado_pago do
   desc "Creates test user using MP API"
   task :test_user => :environment do

data/spec/controllers/spree/mercado_pago_controller_spec.rb

@@ -1,89 +1,31 @@
-# -*- encoding : utf-8 -*-
 require 'spec_helper'
 
-describe Spree::MercadoPagoController do
-  it "doesn't affect current order if there is one (session[:order_id])"
+module Spree
+  describe MercadoPagoController do
+    describe "#ipn" do
+      let(:operation_id) { "op123" }
 
-  context "Logged out user" do
-    it "redirects to login and back again"
-  end
-
-  context "Logged in user" do
-    let(:user)           { create(:user) }
-    let(:payment_method) { create(:payment_method, type: "PaymentMethod::MercadoPago") }
-    let(:order)          do
-      order = create(:order, user: user, state: "payment")
-      create(:payment, payment_method: payment_method, order: order)
-      order
-    end
-
-    before { controller.stub(:spree_current_user => user) }
-    before do
-      order.payment.should_not be_nil
-      order.payment_method.should_not be_nil
-      order.payment_method.type.should eq("PaymentMethod::MercadoPago")
-    end
+      describe "for valid notifications" do
+        let(:use_case) { double("use_case") }
 
-    describe "#success" do
-      context "with valid order" do
-        before do
-          spree_get :success, { order_number: order.number }
-        end
-
-        it { response.should be_success }
-        it { assigns(:order).should_not be_nil }
-        it { assigns(:order).state.should eq("complete") }
-        it { assigns(:order).id.should eq(order.id)}
-        it { assigns(:order).payment.state.should eq("pending") }
-      end
+        it "handles notification and returns success" do
+          MercadoPago::HandleReceivedNotification.should_receive(:new).and_return(use_case)
+          use_case.should_receive(:process!)
 
-      context "with invalid order" do
-        before { spree_get :success }
-
-        it { response.should redirect_to(spree.root_path) }
-        it { flash[:error].should eq(I18n.t(:mp_invalid_order)) }
-      end
-    end
+          spree_post :ipn, { id: operation_id, topic: "payment" }
+          response.should be_success
 
-    describe "#pending" do
-      context "with valid order" do
-        before do
-          spree_get :pending, { order_number: order.number }
+          notification = ::MercadoPago::Notification.order(:created_at).last
+          notification.topic.should eq("payment")
+          notification.operation_id.should eq(operation_id)
         end
-
-        it { response.should be_success }
-        it { assigns(:order).should_not be_nil }
-        it { assigns(:order).state.should eq("complete") }
-        it { assigns(:order).id.should eq(order.id)}
-        it { assigns(:order).payment.state.should eq("pending") }
-      end
-
-      context "with invalid order" do
-        before { spree_get :pending }
-
-        it { response.should redirect_to(spree.root_path) }
-        it { flash[:error].should eq(I18n.t(:mp_invalid_order)) }
       end
-    end
 
-    describe "#failure" do
-      context "with valid order" do
-        before do
-          spree_get :failure, { order_number: order.number }
+      describe "for invalid notification" do
+        it "responds with invalid request" do
+          spree_post :ipn, { id: operation_id, topic: "nonexistent_topic" }
+          response.should be_bad_request
         end
-
-        it { response.should be_success }
-        it { assigns(:order).should_not be_nil }
-        it { assigns(:order).state.should eq("payment") }
-        it { assigns(:order).id.should eq(order.id)}
-        it { assigns(:order).payment.state.should eq("pending") }
-      end
-
-      context "with invalid order" do
-        before { spree_get :failure }
-
-        it { response.should redirect_to(spree.root_path) }
-        it { flash[:error].should eq(I18n.t(:mp_invalid_order)) }
       end
     end
   end

data/spec/dummy/README.rdoc

@@ -1,261 +1,28 @@
-== Welcome to Rails
+== README
 
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
+This README would normally document whatever steps are necessary to get the
+application up and running.
 
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
+Things you may want to cover:
 
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
+* Ruby version
 
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
+* System dependencies
 
+* Configuration
 
-== Getting Started
+* Database creation
 
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+* Database initialization
 
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
+* How to run the test suite
 
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
+* Services (job queues, cache servers, search engines, etc.)
 
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
+* Deployment instructions
 
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+* ...
 
 
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.
+Please feel free to use a different markup language if you do not plan to run
+<tt>rake doc:app</tt>.