Closed GoogleCodeExporter closed 8 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
Original comment by Anatoly....@gmail.com
on 7 Sep 2011 at 7:06
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
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
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
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
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
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
Original comment by ad...@zetaprints.com
on 10 Oct 2011 at 12:34
Original issue reported on code.google.com by
agur...@gmail.com
on 7 Sep 2011 at 12:33Attachments: