Magento Patch SUPEE-6788 breaks custom file option file link on cart page? - magento

When executing file upload on a site with SUPEE-6788 applied, and then adding the product to cart, rather than present a URL to the uploaded file you get a chunk of text similar to this on the shopping cart page and also in the sales email generate. The file itself can be found in the quote folder so looks like the rerendered part of the page that should show the file link is bust.
a:10:{s:4:"type";s:10:"image/jpeg";s:5:"title";s:8:"2849.jpg";s:10:"quote_path";s:68:"/media/custom_options/quote/2/8/16156fb1e8320b06153ee7061a7b5cdf.jpg";s:10:"order_path";s:68:"/media/custom_options/order/2/8/16156fb1e8320b06153ee7061a7b5cdf.jpg";s:8:"fullpath";s:119:"
Has anyone else seen this issue.
** update **
This is still a problem after upgrading to 1.9.2.4.
Interestingly if you update and save the cart the uploaded file link is then rendered correctly. In the sales_flat_quote_item_option table where the product options in the cart are saved, the field holding the file link metadata is updated and it has changed. Some characters present in the value on the original cart submission are removed [see below]
;s:3:"url";a:2:{s:5:"route";s:35:"sales/download/downloadCustomOption";s:6:"params";a:2:{s:2:"id";N;s:3:"key";s:20:"d6e5b846b9f1f6b4298b";}}}
Therefore rather than a rendering issue it looks like a generation issue. Maybe the theme is involved. Will look at difference between writing and regeneration.
** Update **
OK solution found. The Application (Magento Theme + Modules) was, in a Mage_Checkout_CartController type, creating a product in the cart via code like this
$cart = $this->_getCart();
$params = $this->getRequest()->getParams();
$_product = $this->_initProduct();
$cart->addProduct($_product, $params);
This was creating a product that contained the File Upload option which was then stored in an invalid format.
A rework of the code removed the need to use the above code and the problem has gone. So there does seem to be a bug somewhere related to product creation and File Upload options but I've gone far enough on this journey for now.

Same here this problem is encountered within many instances, like product page, checkout page, order page (Magento CMS). First we thought it was about module update issue, but that didn't help, so right now we think it's a 1.9.2.2 bug.

Related

magento broken shopping rule page

I have a problem on magento backend that I am not sure what is happening. Shopping cart price rule was working completely fine, but suddenly the rule page look like this:
screenshoot of shopping rule page
The content of each tab is loaded inside the tab div itself instead of on the content area on the right. Content area is completely empty.
No code was touched in relation with promotions code, or admin/core code at all. I don't see any issue on console or not js code loaded. This is the only page affected (shopping cart price rule page), catalog rule works fine as well as any other with same structure (product page, customer page and such).
I was recently playing around with promotion too much, creating, deleting and editing. And solved a 500 issue on cart page increasing php memory limit. Not sure if related with this issue.
On apache logs it only displays the following when I access that page:
client denied by server configuration: /www/app/etc/local.xml
Could someone help me in where to look in order to solve this issue or have a hint about what could be the issue?
I am completely lost with this one. Magento version 1.7.
Thanks.
I finally found the issue. It was a extension related.
Recently I had some issues on cart page and at some point I disabled a promotion extension (Amasty shipping rules) though magento backend, on system/advanced extensions list.
Seems like the extension is disabled but still used on promotion page, adding the structure for the feature but not showing what is supposed to show (because is disabled) and breaking the layout.
Enabling again the extension or removing the extension on files avoid the issue.
1) clear the cache maybe you made a update and your cache is wrong. you can clear in the admin side clear all the types, or erase all inside /www/var/cache
2) clear the page history in your browser, all is fine but your machime show that weird.
3) after that check the browser console, because is a css problem, maybe a file is lost or change the permitions.

How do I stop Magento from inserting <br> tags automatically in product descriptions?

Whenever you want to add some custom html to product descriptions in Magento you start getting br tags on the frontend that seem to come out of nowhere.
There is a Magento function that's causing this, in order to disable it go to either:
/app/design/frontend/base/default/template/catalog/product/view/description.phtml
OR
/app/design/frontend/base/default/template/catalog/product/view.phtml
The actual file to be modified depends on your version of Magento.
You should find a reference to nl2br in the correct file.
Copy this file in your custom template DO NOT MODIFY CORE FILES
(they will come back to bite you).
Remove 'nl2br'
Clear cache

Blank Page for newly uploaded products in magento

After uploading new products to my existing stockpile (in Magento) I noticed that the product pages were coming up blank. I have reindexed the products, refreshed the cache, ensured that the items are marked as enabled, in stock with a quantity of at least 1. My existing products are working fine so this is a complete mystery to me.
I have found issues such as "Magento shows blank/empty page. How do I solve this?" (http://kb.magenting.com/content/22/38/en/magento-shows-blank-empty-page-how-do-i-solve-this.html) but none that with the same problem as me here.
Ideally someone who's reading this has suffered as I am here and healed the pain - if you have please post the cure. Similarly if anyone can suggest solutions/reasons I'd be most grateful.
_g
Without more information these are just guesses:
Examine your import script against an export script. Did you include all core fields e.g. website, store, sku, name
Check your logs, are any exceptions being thrown on the product page?
Are the products showing up in your catalog? If so you've probably got the core fields imported ok. If not see the first point.
If the products are in the catalog but blank screening on the product page, it's most probably some customer code in your skin thats causing the issue. Try either switching to the default skin and reload. If it works then your import was probably missing an attribute used by your skin on the product page.
If the default skin loads. Go back to your skin and comment out code on your product page until you find the culprit.
Hope that helps.

After magento upgrade prices including tax are displayed as 0 on detail page

I upgraded a magento store from 1.3.x to 1.7.0.0. This caused some bugs which I am fixing now.
I am stuck at this one: the price of products added after the upgrade are displayed correctly in the category page but not on the detail page. For some reason the price including tax on the detail page of a product added after the upgrade is always '0'. The price excluding tax is displayed correctly. You can see this here: http://www.stagefreaks.nl/gedore-scaffhamer.html
Furthermore: the price including and excluding tax is correct in the shoppingcart and during checkout.
Any idea what might cause this problem ? I turned of caching at the moment, so it is not a caching issue (and it has been an issue for over a week now).
Thank you very much for any reply.
in order to solve a bug, the first step is to know where it comes from.
As you already have discarded a template issue, let's focus on the non-core code:
rename app/code/local/ to app/code/local_backup/: this will disable all local modules. Reload your page and check if the price is still wrong.
if it's still wrong, rename app/code/community/ to app/code/community_backup/ and reload the product page
when you've find out which code pool is responsible, undo the folder name's change and disable one module at a time (putting the tag <active> as false in the app/etc/modules/module.xml file or renaming the folder)
Once you know which module is responsible, you'll have to review it to see how it messes with your product detail view.
Oh, also, edit your index.php file to show errors:
comment out the condition around Mage::setIsDeveloperMode(true)
uncomment ini_set('display_errors', 1);
A Specific solution of this problem is....
This Error occur if you install a new custom module and clear the magento cache.
magento creates the Helper,Model,Controller ,Adminahml on installation of your module.
From these files magento knows about your module.
For Ex.
I Create a module name as createform
Module folder is
Createform/Newform/etc/
/Helper/Data.php
/controllers
/Model
/Block/Myform.php
After installation of this module, magento will create a file name as
Createform_Newform_Helper_Data.php in /includes/src/ folder.
Note:- If this file not created in /includes/src/ folder.
Fatal error: Class 'Createform_Newform_Helper_Data' not found in /app/Mage.php on 546
Then this error will occur.
For removing this error Manually create this file in includes/src folder.
Like:-
/includes/src/Createform_Newform_Helper_Data.php
and add code of Data.php file in Createform_Newform_Helper_Data.php file.
Then refresh your site.
This error is removed from your system and it works properly.
Also check your system.log file for other errors.
Just a hunch but could it have something to do with the new VAT options? There are options for vat calculation there you could check out.

Associated products not showing up in frontend in Magento

working with Magento 1.5.1 my grouped products don't show their associated products in the frontend (the list with their prices), however everything is fine on the backend and the other type of products (Simple and configurable) are ok in frontend.
It just don't load the grouped.phtml file, how could I debug the page loading process ? or even better, any ideas how to fix this problem?
Thanks in advance
The problem was an extension that overwrites the grouped product generation file and it created a conflict.
After commenting a code line in its .xml, everything's back to normal.

Resources