8

Magento updates need thorough testing and often adjustments in custom modules and themes. Patches on the other hand should be applied as fast as possible to close the (now public) vulnerabilities. That's why my recommendation is to always apply patches immediatly, even if you plan to update early. You may make an exception if your current version is just a ...


7

Let's say you built your shop in the best-practice way without changing any core classes or base template files definitely go for an upgrade. Patches are just there for urgent security issues, the upgrade will give you a lot more like code improvements and functionalities. Next to that, upgrading minor versions rarely goes wrong, do that every new version ...


6

You probably set up your cronjob to call cron.php via HTTP, which is now forbidden by default. This is the new rule in .htaccess: ########################################### ## Deny access to cron.php <Files cron.php> ############################################ ## uncomment next lines to enable cron access with base HTTP authorization ## http://...


6

Fix from above comment worked. Try this: https://github.com/baconl/Magento-1.9.2.X-duplicate-sku-export-fix Its a temporary fix until the magento core team fixes it, – baconl


6

Try This below Solution Open up the following file: lib/Varien/File/Uploader.php Find this line : chmod($destinationFile, 0640); Replace it with this line: chmod($destinationFile, 0777);


5

Thanks for the replies people, but I have the solution. The new upgrade replaced the .htaccess file in the media folder and the .htaccess file that should have been in the root folder wasn't there anymore. I don't know if other people can use these same files, but in case they can here they are. Media .htaccess contained the following: Options All -...


3

You have several options to do this, each with their own advantages and disadvantages. I always start looking whether the available session objects can be used. You'll find a great write-up of what the different session objects are in this SE topic. The first, core/session, can be used but it isn't recommended. Data stored in this session persists as long ...


2

yes, It's a bug. you need to override this file Mage_SalesRule_Model_Quote_Freeshipping code your logic in collect function. public function collect(Mage_Sales_Model_Quote_Address $address) { parent::collect($address); $quote = $address->getQuote(); $store = Mage::app()->getStore($quote->getStoreId()); $address->...


2

This is an old question, but I'd like to clear some points, after reading previous answers. This is at least the developer point of view, a business manager won't have any doubt: just upgrade! Of course, security patches are important for a live production site. But it's not as easy as it seems. In fact, I am pretty convinced a very high % of upgraded (or ...


2

I don't think this is an issue I'm using a different version of magento but the configurable item will have stock 0 as you don't hold any stock of it, but it will decrement the child products stock when you purchase the configurable correctly, and display those as out of stock in the selector on the frontend if the child product becomes out of stock.


2

the getStoreCategories method returns a collection of Mage_Catalog_Model_Category_Tree which is a collection of categories with the correct hierarchy and a limited number of attributes added like name and URL. This would be more suited for building a menu though. As to why it doesn't work. Make sure your flat categories are on under System > ...


2

PayPal doing the following math: Subtotal + Tax - Discount and receive a Total based on this calculation. While all the figures in Magento sales order are correct there is no way to properly send this amount combinations since PayPal expect calculations made based on prices excluding tax, not including (in your example discount is applied on amount including ...


2

Regardless of how this is broken, we are not in 2008 any more (when Magento was born), and, nowadays there is this thing called HTML5. It comes with placeholders for form elements. You may want to re-factor your theme so that the templates use the HTML 5 placeholder, e.g. <input placeholder="Search entire store here..." ... />


2

The problem comes from a join in the query. I have the same issue, but still didn't resolve it yet. But when I go and export all products I can see that this happens only to products that have many pictures. If we remove this join, the result will be OK or we have to add UNIQUE to the query. You can see on this screenshot what's causing the duplicate rows. ...


2

You need to change the template dynamically. For this you can observe the event controller_action_layout_generate_blocks_after and your observer should somewhat look like this. <?php class Magento_Study_Model_Observer { const NEW_MEDIA_TEMPALTE = 'your/new/media/template.phtml'; public function changeProductImageTemplate(Varien_Event_Observer $...


2

Seems like the Dom library isn't installed on the server. Check http://php.net/manual/en/dom.setup.php for more info


2

Something like this could work (not tested and class names need replacing to match your own) - This method also means that you don't need to have a Form in place: var filters; jQuery('.layered-nav .option').click(function(ev){ ev.preventDefault(); var pathname = window.location.pathname; // Returns path only var url = window.location.href; ...


2

Here is an idea. The filtering is done via $_GET. So you will need a form that is sent via get to the same page. You can edit the app/design/frontend/{package}/{theme}/template/catalog/layer/view.phtml file and add a form around the whole block: <?php if($this->canShowBlock()): ?> <form action="<?php echo $this->getClearUrl() ?>" ...


2

Layered navigation works adding variables to a URL (women/women-new-arrivals.html?color=21&sleeve_length=46). Normally that would be done by links but using a form is also possible You'll need to edit 2 frontend templates: catalog/layer/filter.phtml <ol> <?php foreach ($this->getItems() as $_item): ?> <li> <?php if (...


2

Turns out that in the class Badia_Siteseo_Block_Adminhtml_Sellingpoint_Edit, the constructor method was protected instead of public.


2

You are missing the file 'dev/tests/functional/.htaccess' In order to make the patch finish, you need to have that file (with it's data from 1.9.2.1) so that it can delete it. Weird, I know.


2

As said in this recent thread, in versions above 1.9.2.2 (or previous versions with all security patches applied) Magento requires permission to load specific widgets or blocks. You gotta create this permission in 'System->Permissions->Blocks' menu, as catalog/product_list It worked for me. Good luck!


2

this error is of duplication. If you see in your M1 database then Default attribute set will be duplicated in eav_attribute_set table. So, the solution for this is delete all Default attribute set from your M1 db and then start your migration to new blank fresh Magento2 db. I hope it would help. :-)


2

YOu miss close tag in this line <div id="parallax_01" class="container" style="background: url({{media url=;"> It is typo error or missing?


1

When I load "mydomain.com/cron.php" If you've got a properly set up server, this wouldn't happen anyway, the route for cron.php should be blocked from web traffic. If you have patched recently with SUPEE-6788 then a change to the default .htaccess file means that this URL is now inaccessible. Your cron should only ever be executed using cron.sh by crontab/...


1

You most likely will have to add a new block type to the 'safe' blocks that Magento understands. The most easy way to do this, is by navigating to: System -> Permissions -> Blocks in the Magento backend. You would then create a new block by clicking the button. Set the 'Block Name' to: catalog/navigation And allow it. This should do the trick. ...


1

The block likely uses a non-standard variable, which will need to be added to the whitelist. See this answer for steps on doing so.


1

You did not include the steps taken during uninstallation, so this is only a guess: You forgot to remove the respective entry in the core_resource table. mysql> SELECT * FROM `core_resource` WHERE `code` = 'attributeSplash_setup'; With this entry still present, the (re-)installation process skips the (re-)creation of the extension's database tables.


1

This message is not part of Magento itself, it is probably coming from a payment extension. Search for the message in app/code to see where it is triggered and/or ask your payment provider, they probably know what it means.


1

When you update to Magento 1.9.2.X you will have this problem. If u use the app/code/core/Mage/Catalog/Model/Convert/Parser/Products.php from a older version of magento it will fix your problem. You can try using this link, its a temporary fix that uses a older Products.php file: https://github.com/baconl/Magento-1.9.2.1-duplicate-sku-fix Keep in mind, ...


Only top voted, non community-wiki answers of a minimum length are eligible