Hi,
I am trying to add a custom field and every time I try save it I get this message; "Display Order" and "Field Name" field(s) cannot be kept empty. I just did a plugin update as that option wasn't working for me and I need to be able to add a custom field. Is there a way to fix this error?
Thanks
Well, its telling you what the issue is I think. When you add a custom field there have to be a value in the "Display Order" and "Field Name" fields. Do you have any custom field where any of those fields are empty?
The current version of eMember uses a simplified validation script that checks whether you have something in every single text field on the page. It is likely that you have a search field in the WordPress admin's upper right corner. If you just enter anything into the search field and then try to submit your custom field changes, it will probably work.
eMember should only really check the "Field Name" and the "Display Order" fields. Can you please tell me how you got this search box that you speak of so I can recreate this on my test site?
I may be confused by this then. Is this a custom field to the profile or the a page/post? I want to add a custom field to the registration profile to include website and maybe more.
I do have everything filled out, which is why it seemed odd that I would get that error message. Is this how I add a custom field to profile?
I have requested site access for another of your issue. I will take a look at it at the same time (please make sure you mention this issue when you fill in the form).
Go to Users > your profile > Show Admin Bar > enable/disable the Dasboard option.
When you enable admin bar for Dashboard, it will be displaying the admin bar in the top of the window while administering your site. The admin bar contains a search field.
Besides admin bar you may have a plug-in that does something similar - add an input field somewhere.
The WP eMember's JavaScript/jQuery validation code scans through all input fields of type "text" on the whole page.
The right way to fix this is to scan through only its one fields, perhaps by using GetElementByID.
This has been fixed in eMember's current build also.
You must log in to post.
