It cost me hours to find a workaround, so if you use it, I’d really appreciate it if you refer to this blog.

How I fixed it

Go to:

/app/code/local/Mage/Shipping/Model/Carrier/Tablerate.php

Add the following code at around line 77 (in the collectRates function):

$s_price = $request->getPackageValueWithDiscount();
$request->setPackageValue($s_price);

Now, the shipping rates are calculated on the subtotal minus the discount. I hope this solves the problem (it does in 1.7)

Now, what you need to do is open the file
app/code/core/Mage/Catalog/Model/Convert/Adapter/Product.php
and go to around line 773 and find

$addedFilesCorrespondence = $mediaGalleryBackendModel->addImagesWithDifferentMediaAttributes(
$product,
$arrayToMassAdd, Mage::getBaseDir('media') . DS . 'import',
false,
false
);
and paste the following code right after it
if (isset($importData['media_gallery']) && !empty($importData['media_gallery'])) {
$x = explode(',', $importData['media_gallery']);
foreach ($x as $file) {
$imagesToAdd[] = array('file' => trim($file));
}
$mediaGalleryBackendModel->addImagesWithDifferentMediaAttributes(
$product,
$imagesToAdd, Mage::getBaseDir('media') . DS . 'import',
false,
false
);
}

Source: http://www.magentocommerce.com/boards/viewthread/224928/P45/

Step 1

Find the file app/code/core/Mage/Rss/etc/config.xml and uncomment/remove:

<sales_order_save_after>
<observers>
<notifystock>
<class>rss/observer</class>
<method>salesOrderItemSaveAfterNotifyStock</method>
</notifystock>
</observers>
</sales_order_save_after>
<sales_order_save_after>
<observers>
<ordernew>
<class>rss/observer</class>
<method>salesOrderItemSaveAfterOrderNew</method>
</ordernew>
</observers>
</sales_order_save_after>

Step 2

Find the file app/code/core/Mage/Downloadable/etc/config.xml and uncomment/remove:

<!–sales_order_item_save_commit_after>
<observers>
<downloadable_observer>
<class>downloadable/observer</class>
<method>saveDownloadableOrderItem</method>
</downloadable_observer>
</observers>
</sales_order_item_save_commit_after–>

Magento is a pretty complex program that hasn’t an easy upgrading solution. Because following the standard guides gives quite a lot of errors, I wrote my own upgrade guide with thanks to Duntuk.com and Turnkeye.

For versions lower than 1.4.2, you’d first have to follow the steps from Turnkeye for lower versions.

Pre-upgrading steps

• MAKE A BACKUP!
• Install a fresh install of Magento on a subdirectory or other host on a new database (don’t overwrite your own version of course).
• With the db repair tool from Magento you can compare your own database versus the fresh database you just installed. The db repair tool looks for errors in the database and can upgrade them.
• Open SSH and remove your cache:
  rm -rf var/cache/*
rm -rf downloader/pearlib/cache/* downloader/pearlib/download/*

Upgrading steps

• Chmod the mage file: $ chmod 550 ./mage
• Upgrade the site (according to Duntuk and Turnkeye):$ ./mage mage-setup .
$ ./mage sync --force
$ ./mage list-upgrades #(in order to see if there are upgrades)
$ ./mage config-set preferred_state stable
• Start the upgrade
$ ./mage upgrade-all --force
• If the upgrade is finished you'll see rows like:
Package upgraded: community/Mage_Locale_en_US 1.7.0.2
• Remove cache and sessions
$ rm -rf var/cache/* var/session/*
$ rm -rf downloader/pearlib/cache/* downloader/pearlib/download/*

• Visit the homepage which will trigger the upgrade process. It can take up to 30 minutes. By doing it by SSH safes memory:
  $ php -f index.php
• Sometimes it’s safer to trigger the index.php multiple times until it gives a blank return
• Than visit the admin and make sure the version number is the number of the upgraded version

Aftercare

Reindex the website if the upgrade is succesful:

$ php shell/indexer.php reindexall

Set all the permissions back:

$ find . -type f -exec chmod 644 {} \;
$ find . -type d -exec chmod 777 {} \;

$ chmod 755 mage
$ chmod o+w var var/.htaccess app/etc
$ chmod -R o+w media
$ chmod -R 777 var/package var/locks var/report var/export downloader

Hopefully your site is upgraded now! If you’ve any questions respond below!

Issues

Error: Mage registry key “_resource_helper/core” already exists

rm -rf var/session/*
rm -rf var/cache/*

If that doesn’t work restart caching tools like Memcached!

Do you experience the problem of slow Magento reindexing? Tinybrick Lightspeed is a good solution. It’s a plugin that requires a little investment (500 dollar), but is worth all the speed improvements. Try it Lightspeed.

This problem is quite hard to identificate, because it’s hard to seek the right column ‘value’. Here is what I did in order to find out the problem.

• Start the import process and see on which record number the errors occur.
• Locate these record numbers and find the difference between other records in a spreadsheet program.
• In my example I found out that on some rows the meta_robots column was empty instead of INDEX, FOLLOW. This caused the error.
• Fill these rows. This will solve the problem.
  
  

Stap 1: BTW tarief verhogen

Dit kunt u doen bij Verkopen > BTW > Beheer Belastingzones en Tarieven

Stap 2a: BTW in de prijs door laten voeren (prijsverhoging)

Hier komt een technisch verhaal bij kijken. De bedoeling is dat de catalogusprijs met de stijging van het btw-niveau automatisch meegaat. Uitgerekend is dit een prijsstijging van 1,68% (aan de hand van (1/119)*121*100% ). De bedoeling is dus om een negatieve korting te geven op alle producten.

Magento accepteert echter standaard geen negatieve kortingen:

Conform het volgende artikel moeten we dus een paar wijzigingen doorvoeren in de kern:

1. Ga naar: app/code/core/Mage/Rule/Model/Rule.php en vind:
   //check if discount amount > 0
if ((int)$this->getDiscountAmount() < 0) { 3 Mage::throwException(Mage::helper(‘rule’)->__(‘Invalid discount amount.’));
}

2. Vervang deze code door deze uit te 'commenten':
// if ((int)$this->getDiscountAmount() < 0) { 3 //Mage::throwException(Mage::helper(‘rule’)->__(‘Invalid discount //amount.’));
//}
3. Ga nu naar: app/code/core/Mage/Adminhtml/Block/Promo/Quote/Edit/Tab/Actions.php en vind: 'class' => 'validate-not-negative-number',
4. ‘Comment’ deze code ook uit: // 'class' => 'validate-not-negative-number',
5. Herhaal stap 3 en 4 voor het bestand app/code/core/Mage/Adminhtml/Block/Promo/Catalog/Edit/Tab/Actions.php
6. Verander in het bestand app/code/local/Mage/CatalogRule/Model/Observer.php :
   $finalPrice = min($product->getData(‘final_price’), $this->_rulePrices[$key]);
   in:
   $finalPrice = $this->_rulePrices[$key];
7. Vervolgens kunt u deze bestanden uploaden (het veiligste is om de bestanden niet in app/code/core, maar app/code/local op te slaan).

Stap 2b: BTW niet in de prijs door laten voeren (gelijke prijs)

Als het goed is, is hier verder geen wijziging voor nodig.

By default, Magento doesn’t accept negative price rule discount values:

We have to add some changes through the core in Magento conform the article:

1. Go to: app/code/core/Mage/Rule/Model/Rule.php and fin:
   //check if discount amount > 0
if ((int)$this->getDiscountAmount() < 0) { 3 Mage::throwException(Mage::helper(‘rule’)->__(‘Invalid discount amount.’));
}

2. Replace this code, by 'commenting':
// if ((int)$this->getDiscountAmount() < 0) { 3 //Mage::throwException(Mage::helper(‘rule’)->__(‘Invalid discount //amount.’));
//}
3. Go to: app/code/core/Mage/Adminhtml/Block/Promo/Quote/Edit/Tab and find: 'class' => 'validate-not-negative-number',
4. ‘Comment’ this code as well: // 'class' => 'validate-not-negative-number',

1. Repeat step 3 and 4 for the file app/code/core/Mage/Adminhtml/Block/Promo/Catalog/Edit/Tab/Action.php
2. Then you can upload these files, I’ll prefer to save it in the app/code/local directory instead of core.

Fixing the order process getting stuck:

According to the Magento Forum, in MySQL, try:

TRUNCATE `log_customer`;
TRUNCATE `log_quote`;
TRUNCATE `log_summary`;
TRUNCATE `log_summary_type`;
TRUNCATE `log_url`;
TRUNCATE `log_url_info`;
TRUNCATE `log_visitor`;
TRUNCATE `log_visitor_info`;

Of course create a backup first. Doesn’t this fix the problem or do you have a better solution? Comment it!

So you’ve got your webshop with products with different sizes. The ‘add to cart’ button on the category page is sometimes a step too much, because you’ll have to choose a size first.

Changing the button to ‘view product’

Changing the button to ‘view product’ would be a better solution. Open the file list.phtml in: /app/design/frontend/default/{yourskin}/template/catalog/product .

About line 63 and about line 107 replace: <p><button type=”button” title=”<?php echo $this->__(‘Add to Cart’) ?>” onclick=”setLocation(‘<?php echo $this->getAddToCartUrl($_product) ?>’)”><span><span><?php echo $this->__(‘Add to Cart’) ?></span></span></button></p>

With:

<button type=”button” title=”<?php echo $this->__(‘Add to Cart’) ?>” onclick=”setLocation(‘<?php echo $_product->getProductUrl() ?>’)”><span><span>View product</span></span></button>