Opened 15 years ago
Closed 14 years ago
#15220 closed defect (bug) (worksforme)
Post custom fields and metakey starting with _
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.1 |
Component: | Administration | Keywords: | needs-patch |
Focuses: | Cc: |
Description
custom fields with metakey starting with _
should not be in the 'Edit post' page even if hidden !!!
Change History (10)
#2
@
15 years ago
- Keywords reporter-feedback added
Please be a little more descriptive: steps to reproduce etc.
#4
@
15 years ago
Fields starting with an underscore are hidden fields. They're not displayed in the UI at all, such key names are usually used by WordPress Core and plugins to store information about the post which is not useful to the end user.
The current behavior is weird, in the sense that no feedback is given to the user that their field has been inserted.
Not allowing hidden fields from being set via the UI will remove a functionality some people may use (primarily developers)..
#5
@
15 years ago
- Component changed from General to Administration
- Keywords needs-patch added; reporter-feedback removed
Now I get it.
Hidden custom fields = non-public custom fields.
Just like we don't allow users to create non-public post types from the UI, we shouldn't allow creation of non-public custom fields either.
For example, a sneaky user could cause trouble by setting a custom field he's not supposed to set.
#6
@
14 years ago
I also tried to insert a custom field and i have a very strange behavior.
Looks like the ajax stuff is broken
#7
@
14 years ago
- Resolution set to fixed
- Status changed from new to closed
seems to be fixed in 3.0.1 beta 1
btw, weird behavior when trying to insert a new custom field !!