2

The contractor we hired several years ago installed Magento 1.4.0.1 and ended up modifying several core files. In the attached image, I am showing the diffs between our installation and a fresh 1.4.0.1 installation. Included is a short description of the change in each file that was changed.

From looking at it, how should I fix this situation using either plugins, extensions, module, etc? I have never written a Magento extension or module and not sure how I should do this with the changes involved. Some of them look like they are not going to be able to be done that way.

I'd appreciate any hints on how to tackle this as we have not been able to upgrade and I have not been able to get the USPS module changes installed, so we have to use flat rate shipping, which is costing us a ton.

I would hope that there are some concrete ideas posted and not just links to all the blog posts about writing Magento extensions and overriding Magento core as I've read probably every one of them; I just not sure what needs to be put where.

If you have any questions about the changes listed, please ask. I'll be as forthcoming as possible.

I intend to install a fresh version of 1.4.2 and begin the work there, then upgrade all the way to 1.9.

FYI...
We use Magento as a shopping cart "off the side" of an ExpressionEngine-based site. Essentially all we use is the cart portion. The product listings, etc are all handled by EE. Our authentication is through a web service to our Oracle DB and every Magento customer has the same password, they are automatically logged in by the system when they login to the site using our authentication scheme.

enter image description here

1

at first, get a fresh installation of magento 1.4.0.1 and move your files ( modules, themes, skin etc. ) there. then i would build some modules to keep the functionality of the core-hacks

i made a small list for you, hope it will help:

you should override the changed methods with your own module in the following files:

  • app/code/core/Mage/Checkout/Block/Onepage/Progress.php
  • app/code/core/Mage/Checkout/controllers/OnepageController.php
  • app/code/core/Mage/Checkout/Model/Type/Onepage.php
  • app/code/core/Mage/Checkout/Model/Cart.php
  • app/code/core/Downloadable/controllers/DownloadCrontroller.php
  • app/code/core/Paypal/Model/Api/Nvp.php
  • app/code/core/Paypal/Model/Api/Direct.php
  • app/code/core/PaypalUk/Model/Api/Nvp.php
  • app/code/core/PaypalUk/Model/Direct.php
  • app/code/core/Sales/etc/config.xml
  • app/code/core/Sales/Model/Quote.php
  • app/code/core/Shipping/Model/Carrier/Flatrate.php
  • app/code/core/Usa/Model/Shipping/Carrier/Usps.php

Copy the following files ( with directories ) to app/code/local:

  • app/code/core/Customer/Model/Address/Abstract.php
  • lib/Varien/Db/Select.php

copy these files to your own theme:

  • locale/en_US/template/email/sales/order_new.html
  • skin/frontend/base/default/js/opcheckout.js
  • skin/frontend/default/default/css/styles.css

also you could ignore the changes from app/code/core/Model/App.php

if everything is working like you expect, try to upgrade to a newer version of magento

| improve this answer | |
  • Thanks for the idea, however, I'm kind of confused by this: "you should override the changed methods with your own module" How do I override all of those in one module? – MB34 Jun 2 '14 at 18:23
  • i would not recommend to override all these methods in one module, better group some of them in separate modules. Define your overrides ( or better work with observers if it is possible ) in your config.xml of your module. – Dopamedia Jun 2 '14 at 19:35
  • It looks like we're going to stay with this version of Magento for the near future until we replace it with another package. Thanks for looking into this. – MB34 Jun 5 '14 at 19:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.