We’re rewarding the question askers & reputations are being recalculated! Read more.
42

I managed to change my custom module to use the Magento new way as recommended with the patch 6788. So I give here as a reference for other, also answer the question in this thread. Change to router in the config.xml file: Before: <admin> <routers> <adminhello> <use>admin</use> <args> ...


27

My understanding is that CE 1.9.2.2 includes all the changes from the recent-patch SUPEE-6788, one of which was restrict the blocks that can be used in CMS blocks, pages, emails (etc...) by default. Fortunately you can whitelist additional blocks through the admin under System > Permissions > (Blocks | Variables)


20

I used below method: System > Permissions > Blocks Add New Block Block Name: cms/block Is Allowed : Yes This seems to have done the trick for me.


19

Looking at the top of these errors, there is an error showing that the magento_all_lates.txt can't be deleted from /pkginfo. Once you do that manually, it should work.


17

I lost hours figuring this out. Just because the Devs at Magento aren't capable of making an understandable configuration, or yet even documenting their code in a way a human being would be able to read it. Let's have a look at the config.xml first <routers> <adminhtml> <args> <modules> <admin_adminhello ...


17

Delete pkginfo/Mage_All_latest.txt and then from magento connect try to upgrade only mage_all_latest only.. It will upgrade everything successfully without any issues. I did same and it worked. Let me know if you need help.


12

I think it's pretty easy to lull yourself into a false sense of security whith this. Admin routing compatibility mode for extensions: Enabled (=Default) This is the default setting after applying the patch. Your extensions won't break with this setting. Security is limited though. Admin routing compatibility mode for extensions: Disabled Only with a ...


10

Yes, it is possible to migrate 1.9.2.2 from PHP 5.5 to PHP 7. Its not officially supported yet but Inchoo has found the solution to this. They have developed Magento extension to make Magento compatible with PHP 7. http://inchoo.net/magento/its-alive/ As of now from Magento 1.9.3.7 PHP 7.0 and 7.1 are officially supported. PHP 7.2 support is not yet ...


8

Here's an analysis/fix tool for extension and customization conflicts resulting from the Magento SUPEE-6788 patch. https://github.com/rhoerr/supee-6788-toolbox Note: Before applying any patch or patch fix, it is always recommended to make backup of your website and database. You can only analyze what need to fixed. To analyze: Run from SSH: php -f ...


8

You need to enter the block type="cms/block" instead of the block_id="home-news-text" into the permission form for your blocks to show up.


8

First of all: Nice question! I'd say a fully patched 1.7.0.2 is as secure as a new 1.9.2.2. As long as there are still security patches released for 1.7.0.2 you're good to go with it. So I think it makes sense to continue with 1.7.0.2 and use the time to plan and develop your new shop with Magento 2.


7

You can find a list on https://www.nicksays.co.uk/magento-events-cheat-sheet-1-9/ although it's probably not 1.9.2.2. Alternatively you can do a grep on the ./app/code/ directory to generate your own list. grep -Rsn 'Mage::dispatchEvent' . > events.txt


6

To allow the inline translation, Magento uses the isAllowed method of Mage_Core_Model_Translate_Inline class, which basically does the following: check if the inline translation is allowed in the backend for the current area (adminhtml or frontend) check if the inline translation has not been disabled via setTranslateInline(false) In your case, as you seem ...


5

I would recommend using the https://github.com/rhoerr/supee-6788-toolbox tool from Paradox Labs. It scans your codebase for each of the issues listed in your question.


5

Deleting both the Mage_All_Latest.txt folder as well as the text file manually enabled the patch to correctly install from Magento Connect Manager.


5

When you upgraded magento if you have the following files that your have overridden in your theme you will need to add the following for customer registration to work: <input type="hidden" name="form_key" value="<?php echo Mage::getSingleton('core/session')->getFormKey() ?>" /> Files: app/design/frontend/{your_theme}/{your_package}/template/...


5

You must use $this->getResponse()->setBody('your echo');


5

Here is the working example if(file_exists(Mage::getBaseDir('media') . DS . 'import' . DS . $gallery_img)){ $product->addImageToMediaGallery(Mage::getBaseDir('media') . DS . 'import' . DS . $gallery_img, null, false, false); } As you can see here, I have used full image path to the place where you have placed not understanding what to do here. ...


5

I have had the same problem, the answer is that your theme does not supply a variable called form_key. Just as stated above I have to add: <input type="hidden" name="form_key" value="<?php echo Mage::getSingleton('core/session')->getFormKey(); ?>" /> to the following files: /app/design/frontend/default/template-name/template/customer/form/...


4

Admin Routing Compatibility mode works like Compatibility Mode in Internet Explorer. It downgrades the application to function like an older version so the insecure modules will work. When you have all your modules upgraded to work properly in the new security model, you will disable Admin Routing Compatibility mode to restrict access to the admin backend. ...


4

not sure if this will work, but you can try to use addExpressionFieldToSelect and then having on the expression you use. Something like $collection->addExpressionFieldToSelect( 'expression_alias', '{{field1}} - {{field2}}', array('field1' => 'real_field1_name', 'field2' => 'real_field2_name') ); and then $collection->getSelect()...


4

It's most likely that there is a module installed, or a custom theme installed, that has trailing whitespace after the closing ?> in a file or class. Because it's happening with both Mage.php and Config/Options.php, I would look at those two files first. After that, disable all local modules and follow the standard debug process outlined here: ...


4

I've just fixed an issue after this exact error happened to me. Not sure if it was an upgrade or not. Regardless, it was because a big chunk of customers had customer_entity set to 0000-00-00 00:00:00 - which Magento really had trouble parsing. Nevertheless, I ran the following SQL query and it fixed it: (Obviously back it up) UPDATE `customer_entity` ...


4

$total = Mage::getModel('sales/order')->getCollection()->getSize();


4

You can follow below steps for display static block: Step 1)Go to admin. Step 2)Open Top menu System->Permissions->Blocks. Step 3)click "Add New Block". write your "Block Name" and Is Allowed "Yes". Note: Block Name is type of your block for example "cms/block" after Save Block. Step 4)Clear cache and refresh front page. Now Block is showing. ...


3

In the Magento backend "System > Permissions > Variables" and "System > Permissions > Blocks" Add newsletter/subscribe and refreshed cache. More info: There is a new check on the template directive, see Mage_Core_Model_Email_Template_Filter::blockDirective() line 176 if ($this->_permissionBlock->isTypeAllowed($blockParameters['type'])) { ...


3

I believe the newsletter/subscribe block is not on the default whitelist that was introduced with the latest patch and version 1.9.2.2; this means you can not call it from a cms block if you don't add it to the whitelist manually before. See here how to add it: APPSEC-1057 How to add variables or blocks to the white list tables


3

You need to go to System->Config->Web->Search Engine Optimization


3

Seems like you put an error in the template: The URL should be /customer/account/createPost (capital P)


3

First, enable logging from the admin, and see if it produces any files inside "var/log" folder. If not, there might be some permission issues on the folder. Now, back to your problem, your layout file is telling Magento to search for the template file mymodule/mymodule.phtml, so if you are going with the base theme folder, path for your template file will ...


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