https://legacy.forums.gravityhelp.com/topic/js-bug-in-admin-for-select-fields Gravity Support Forums Topic: JS bug in admin for select fields... en-US Sun, 10 May 2026 14:15:50 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/js-bug-in-admin-for-select-fields#post-184345 Mon, 25 Mar 2013 17:43:32 +0000 Chris Hajer 184345@https://legacy.forums.gravityhelp.com/ <p>If you are using WordPress 3.5.1 and Gravity Forms 1.6.12, please begin troubleshooting by checking for theme and plugin conflicts using these tips <a href="http://rkt.gs/testing" rel="nofollow">http://rkt.gs/testing</a></p> <p>If you don't find anything there, I will bring this to the attention of the development team. </p> https://legacy.forums.gravityhelp.com/topic/js-bug-in-admin-for-select-fields#post-184139 Mon, 25 Mar 2013 13:16:45 +0000 Contexture 184139@https://legacy.forums.gravityhelp.com/ <p>After the last update I noticed this problem popping up while trying to edit a select/dropdown from my WordPress admin.</p> <p>The problem:<br /> In the WordPress admin, while editing a form, clicking on the "Edit" link for a select field which contains numeric option values was throwing this error:</p> <p>Object 43 has no method "replace"</p> <p>As a result, the edit options do not appear and the element cannot be edited.</p> <p>Expected behavior:<br /> Clicking on "edit" for the dropdown should have opened the dropdown's customization options. Clicking "edit" should not have generated any JS errors.</p> <p>Detail:<br /> The dropdown contained a list of options with numeric values and separate text. The first option contained a value with the integer "43", and the JS was assuming ( by virtue of calling <code>value.replace()</code> ) that the "value" variable would be a string. This causes an error because the .replace() method only exists for strings, not for integers.</p> <p>Solution:<br /> The problem file is <code>js.php</code> in the <code>GetFieldChoices()</code> function. I was able to solve the error for now by adding <code>value = value.toString();</code> at around line 869, after the value variable is defined. </p>