Single Page Quote Character text input parse issue in uStore v17.1 patch 6027 text input

markb

unread,

Sep 10, 2024, 7:59:31 PM9/10/24

to XMPie Interest Group

Hi all,

A client discovered today on a single page product, that entering a quote character in a text input can't be parsed so therefore can't be previewed. uProduce error is Variable "fname": Failed to parse expression In line 1, character 8, token "Mark".

I changed the store / product to legacy multiple pages and that resolved it.

Is there a bug fix for this in 17.2?

Thank you, Mark

couch

unread,

Sep 10, 2024, 8:20:02 PM9/10/24

to XMPie Interest Group

i just tested on my v17.2 and single quote worked fine in single-page mode dynamic product.

It's funny that you mention this on v17.1 - i vaguley remember the opposite problem early on with that version - that the characters were html encoded and worked fine in SPA, but showed the full html code in multi-page mode - eg like: Steve&#39s.

I'm pretty sure it was fixed with a patch on v17.1 but can't confirm it right now since I've upgraded.

markb

unread,

Sep 10, 2024, 11:49:59 PM9/10/24

to XMPie Interest Group

Single quote ' works ok, it's the double quote " character that is generating the error in 17.1 / single page mode. Yes, I have a memory of the multi-page mode bug with full html code that I believe was fixed with a patch.

Christoph

unread,

Sep 11, 2024, 4:24:23 AM9/11/24

to XMPie Interest Group

Hi,

just tested it on 17.2 and I get the same error.

Christoph

unread,

Sep 11, 2024, 4:33:21 AM9/11/24

to XMPie Interest Group

Edit to clarify:

I tested SPA and Legacy, each with same settings. Legacy works. SPA Product fails.

Preview fails only when using Variable. Using ADOR directly works fine.

When escaping the quote character, the preview works:

Hello \"World\" --> works
Hello "World" fails

markb

unread,

Sep 11, 2024, 9:39:35 AM9/11/24

to XMPie Interest Group

Interesting, yes I am using variables. Thank you for confirming!

couch

unread,

Sep 11, 2024, 6:19:35 PM9/11/24

to XMPie Interest Group

Thanks for confirming, sorry I was testing the wrong character.

I see it has been raised to XMPie Support and has also been escalated to R&D.

markb

unread,

Nov 12, 2024, 3:09:45 PM11/12/24

to XMPie Interest Group

Hi all, does anyone know if this was included as a fix in newer version? Support closed the case on my end after they submitted to R&D and mentioned they typically circle back when it's fixed, but haven't hear back yet and thought I'd check here first. Thank you!

couch

unread,

Nov 12, 2024, 3:32:34 PM11/12/24

to XMPie Interest Group

From what I can see BUG-145984 was marked as fixed in v18.0

markb

unread,

Nov 12, 2024, 4:59:22 PM11/12/24

to XMPie Interest Group

Thank you Couch!

Reply all

Reply to author

Forward