Letractively / magento-w2p

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

Multiple fields in a single text frame (deeper) #646

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The problem with "multiple fields in a single text frame" goes even deeper than 
I thought. Here's product has no fields renamed from the frame as explained in:
http://code.google.com/p/magento-w2p/issues/detail?id=645
product on customer setup site has the same bug as in #645 (multi_02.png):
http://d1.zetaprints.com/magedev/index.php/sample-stationery/business-card-02.ht
ml

Same template uploaded on cname:
http://cname.zetaprints.com/?page=template;TemplateID=7494B566-499F-4598-A897-25
6AB7A1FA04
gets the fields highlighted OK (multi_01.png):
http://d1.zetaprints.com/mageimage/index.php/magentot-02/bussines-card-02.html

I don't know what is causing this. Maybe it works on /mageimage/ because I just 
uploaded it and it got processed correctly.

Original issue reported on code.google.com by agur...@gmail.com on 7 Sep 2011 at 12:33

Attachments:

GoogleCodeExporter commented 9 years ago
Shapes have different names. Just check XML for templates.

Shape from /magedev/ has "Name, Role, Phone (optional), Fax (optional), Mobile 
(optional), eMail (optional), Web address" as a name.

Shape from /mageimage/ has "Name; Role; Phone (optional); Fax (optional); 
Mobile (optional); eMail (optional); Web address" as a name.

See names have different delimiters. We are using ; as a delimiter now. 
Templates with comma separator are old and need to be reprocessed.

Original comment by Anatoly....@gmail.com on 7 Sep 2011 at 4:55

GoogleCodeExporter commented 9 years ago

Original comment by Anatoly....@gmail.com on 7 Sep 2011 at 7:06

GoogleCodeExporter commented 9 years ago
What do you mean we're using ; delimiters now? Fields are separated using ; 
delimiter inside CorelDRAW. Maybe this is the conflict.
This is how it is done in the file:
http://www.zetaprints.com/help/web-to-print-fields-2/

Original comment by agur...@gmail.com on 7 Sep 2011 at 7:32

GoogleCodeExporter commented 9 years ago
OK, this was an API issue. No change to how the templates are made.

Original comment by ad...@zetaprints.com on 7 Sep 2011 at 10:14

GoogleCodeExporter commented 9 years ago
Atanas, is this issue still valid?
Check on an up to date template.

Original comment by ad...@zetaprints.com on 3 Oct 2011 at 10:16

GoogleCodeExporter commented 9 years ago
Tested on
web_to_print_store_incl_theme   1.9.2.0alpha5 (alpha)

Looks like "Up to date" templates were not the issue. They worked fine. Old 
templates, however, still have the bug.
Marking it as Test OK since reprocessing is expected for this to work because 
of the latest changes to the code.

Original comment by agur...@gmail.com on 3 Oct 2011 at 5:32

GoogleCodeExporter commented 9 years ago
We got to document it somewhere.
Stick it in the FAQ?
That page is getting bloated, though.

Original comment by ad...@zetaprints.com on 4 Oct 2011 at 2:27

GoogleCodeExporter commented 9 years ago
FAQ updated:
http://www.zetaprints.com/magentohelp/faq-2/

added a "Interactive personalization" section containing a suggestion to 
reprocess the template in case the interactive personalization window freezes.

Note. The FAQ page is getting bloated but it is a good thing to have all them 
FAQs and answers in there rather than have them scattered all over the place. 
We might want to think about having a expandable JS in there for the answers 
part. Show only the questions in a list and have users expand the one troubling 
them.

Original comment by agur...@gmail.com on 7 Oct 2011 at 4:58

GoogleCodeExporter commented 9 years ago

Original comment by ad...@zetaprints.com on 10 Oct 2011 at 12:34