This thread is resolved. Here is a description of the problem and solution.
Problem:
Display different content for different user role.
Solution:
I suggest you try with Toolset Access shortcode [toolset_access] shortcode to display those custom fields, for example:
[toolset_access role="Administrator,Editor" operator="allow"] Here display the custom fields [/toolset_access]
Relevant Documentation:
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | - |
| - | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Supporter timezone: Asia/Hong_Kong (GMT+08:00)
This topic contains 7 replies, has 2 voices.
Last updated by 4 years, 10 months ago.
Assisted by: Luo Yang.
I integrate the previous post with a screenshot.
As you can see the field in views still appear empty when post saved from a user.
The second row have filed filled because i have edited it in backend and saved again.
Tnx a lot for help
Hi Luo, good morning.
As you can see on the new attacched screenshot i set a default value for my "Select" type field....
but is not saved when frontend form was submitted 🙁
Where is the mistake?
New threads created by Luo Yang and linked to this one are listed below:
https://toolset.com/forums/topic/save-the-default-value-of-this-field-is-not-stored/
