Hello, since the new update (which I do appreciate because of the new features), I'm having a few issues:
1. A field that I have deleted is not truly deleted, in that I'm unable to use the same name as before because it says it's already in use (even though it does not show up in the User Field List).
USER FIELD NAME: 1-1-magic-words-animal
2. One of my fields is not updating properly when I go in as a user on the front end to submit a value. The form is supposed to still be visible which it is, but the radio button previously selected goes away and it's blank again. Also, after submitting a value, this message appears above the form: User Saved
LOG IN TO SEE FORM ON TEST PAGE: [site.com]/game/1-1-observe-the-physical/quest/toolset-test/
3. I can't use Safari 11.1.2 to do my configuring with Toolset anymore, although Firefox seems to work. (In Safari, the Toolset form editing pages don't load at all, or only load halfway. About 1 in 5 times I can get the full page to load on a refresh if I wait long enough.)
Ideally I'd love for you to log in for me to see for yourself, as it's difficult to explain in words and my site is not yet live. Thanks!
Hi Gam,
Deleting the custom field from the custom field group doesn't actually delete the field. It removes the Types control over the field.
To delete the field, please go to Toolset > Custom fields > Scroll down bottom of the fields group table and click (Post field control) button
Search for the field you want to delete and click delete.
I'm checking the field update issue. please keep watching this ticket.
Hi Gam,
About the second issue, This issue is not replicable on a fresh install. So, it's not a bug in our plugins.
I've installed a copy of your website on my localhost to check the issue, deactivated all plugins except for Toolset and activated Twentynineteen to check if it's a compatibility issue with a plugin that you have but the issue existed after this check.
So, it's an exception in your installation.
I've escalated your issue to the second tier support so that they can work on it.
Please keep watching this ticket and I will notify you once I get any updates.
Thanks.
Hi Gam,
I'm sorry for the last message. I'm now able to replicate the issue on a fresh install. So, it seems that we have an issue happens when the radio user field options don't have values in the "Custom field content".
Please keep watching the ticket and I will notify you once I get any updates.
Thanks.
Hi Gam,
After discussing this with the second tier support and the development team.
Here is the development team response:
The user should add different values to the select field options to differentiate between the field options when saving it to the database and when displaying it in the frontend or even in the user profile or the custom posts.
So, the solution for your issue to add different values in the "Custom field content" for each option of the radio field.
This would be the same for the select fields and checkboxes fields.
About your third question, please post a new ticket for it because it needs to be handled in a separate ticket.
Thanks.
Thanks for all your help Mohammed. Great tip for #1, and also the #2 issue resolved by populating the Custom Field Values in my User Radio Field settings. Side note... if this is required to be populated, why does it let you keep it blank? I'm pretty sure I was able to leave these blank before the update, but anyway I'll try to remember to put something in there going forward.
