search

JaimeChizavane / magento-w2p

Automatically exported from code.google.com/p/magento-w2p
0 stars 0 forks source link

Send fields for the page only #743

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
At the moment we are sending ALL fields for the template to update just one 
page.
This leads to a mismatch between the order and preview that we cannot track at 
ZP - previews match.

Mage should be sending only the fields for the page. It applied to text and 
images.

Original issue reported on code.google.com by ad...@zetaprints.com on 6 Feb 2012 at 10:51

GoogleCodeExporter commented 8 years ago 
Nope, we send fields per page.
See function serialize_fields_for_page() at 
http://code.google.com/p/magento-w2p/source/browse/trunk/skin/frontend/base/defa
ult/js/zp-personalization-form.js#470

Original comment by Anatoly....@gmail.com on 8 Feb 2012 at 2:01

GoogleCodeExporter commented 8 years ago 
In this case, the problem is with the way you count the image fields, I suspect.
Do you address them the index in an array?

Somehow, somewhere, an image the user uploaded fell into a wrong place and got 
submitted without the user noticing.
Doesn't make sense.

The fact is, ZP processed the data it had correctly.
The question is if the data was submitted incorrectly or got corrupted by ZP.
We'd have this surfacing more often if there was a problem at ZP end.

Original comment by ad...@zetaprints.com on 8 Feb 2012 at 9:03

GoogleCodeExporter commented 8 years ago 
I don't count them at all.

1. I get images xml from ZP and parse it in zetaprints_get_user_images() at 
http://code.google.com/p/magento-w2p/source/browse/trunk/lib/ZetaPrints/zetaprin
ts-api.php#510
2. Then append images to template details xml in add_user_images() at 
http://code.google.com/p/magento-w2p/source/browse/trunk/app/code/community/Zeta
Prints/WebToPrint/Helper/PersonalizationForm.php#430
3. And then output it with XSLT at 
http://code.google.com/p/magento-w2p/source/browse/trunk/lib/ZetaPrints/xslt/com
mon-templates.xslt#367

Original comment by Anatoly....@gmail.com on 9 Feb 2012 at 5:35

GoogleCodeExporter commented 8 years ago 
Atanas, we can't replicate the issue.

This happens on templates with lots of pages, like those calendars on that 
hungarian site. We need you to give it a bash and try to replicate the issue. 
Let's discuss the details first.

Original comment by ad...@zetaprints.com on 12 Feb 2012 at 10:35

GoogleCodeExporter commented 8 years ago 
Ping to explain it to me Max.
I don't follow.

Original comment by agur...@gmail.com on 13 Feb 2012 at 1:51

GoogleCodeExporter commented 8 years ago 
See # 753 on redmine for b/g info.

Original comment by Anatoly....@gmail.com on 14 Feb 2012 at 12:15

GoogleCodeExporter commented 8 years ago 
Could not replicate.

The closest thing I got to this, I reported as a separate issue:
http://code.google.com/p/magento-w2p/issues/detail?id=754

Original comment by agur...@gmail.com on 15 Feb 2012 at 11:09