https://legacy.forums.gravityhelp.com/topic/duplicate-product-field-javascript-error-unterminated-string-literal-16442 Gravity Support Forums Topic: Duplicate product field javascript error: unterminated string literal, 1.6.4.4.2 en-US Sat, 04 Apr 2026 16:20:23 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/duplicate-product-field-javascript-error-unterminated-string-literal-16442#post-60734 Wed, 30 May 2012 08:34:08 +0000 Rob Harrell 60734@https://legacy.forums.gravityhelp.com/ <p>Sure, go ahead and send me WP Admin credentials to <a href="mailto:rob@rocketgenius.com">rob@rocketgenius.com</a> and reference this post in your email. </p> https://legacy.forums.gravityhelp.com/topic/duplicate-product-field-javascript-error-unterminated-string-literal-16442#post-60718 Wed, 30 May 2012 06:09:15 +0000 lkraav 60718@https://legacy.forums.gravityhelp.com/ <p>Turns out the bug appears when Product field Description box has HTML tags in it. So this seems to be the same as <a href="http://www.gravityhelp.com/forums/topic/duplicate-bug-for-product-field" rel="nofollow">http://www.gravityhelp.com/forums/topic/duplicate-bug-for-product-field</a></p> <p>But over there it seemed to unreproducable. This makes me think maybe it's something to do with locale differences in the price? Good ol "," vs "." issues.</p> <p>Either way I can give someone access to my staging server where the problem is def. reproducable. </p> https://legacy.forums.gravityhelp.com/topic/duplicate-product-field-javascript-error-unterminated-string-literal-16442#post-60717 Wed, 30 May 2012 05:59:30 +0000 lkraav 60717@https://legacy.forums.gravityhelp.com/ <p>--<br /> [12:56:47.879] unterminated string literal @ <a href="http://myserver/wp-includes/js/tw-sack.js?ver=1.6.1:1" rel="nofollow">http://myserver/wp-includes/js/tw-sack.js?ver=1.6.1:1</a></p> <p>I can send the form XML export to Rob or whoever.</p> <p>Noticed first on 1.6.4.2, no improvement with 1.6.4.4 or 1.6.4.4.2. This doesn't mean the bug didn't exist earlier, just that 1.6.4.2 was the first version I'm using. </p>