Timeline for can i limit editing specific custom fields to certain roles?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 18, 2013 at 0:40 | comment | added | brasofilo | @PETER, thx, added the link to the Answer. | |
| Jan 18, 2013 at 0:39 | history | edited | brasofilo | CC BY-SA 3.0 |
Added Codex reference.
|
| Jan 17, 2013 at 23:49 | comment | added | schpet | i found it after reading your answer: codex.wordpress.org/Function_Reference/… | |
| Jan 17, 2013 at 23:47 | vote | accept | schpet | ||
| Jan 17, 2013 at 23:34 | comment | added | brasofilo | I'm not finding the documentation about this feature, but I'd risk to say that yes, you don't have to worry about users messing with it. | |
| Jan 17, 2013 at 23:31 | comment | added | schpet | very cool thanks! and your update suggests a user cannot update this field even with a special request, so i don't have to worry about users being able to write their own XSS-y scripts in that field | |
| Jan 17, 2013 at 23:24 | history | edited | brasofilo | CC BY-SA 3.0 |
This kind of field is only for dynamic use.
|
| Jan 17, 2013 at 23:13 | history | answered | brasofilo | CC BY-SA 3.0 |