Opened 15 years ago
Closed 15 years ago
#11506 closed defect (bug) (fixed)
Creation of unnamed option is possible
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.0 | Priority: | lowest |
Severity: | trivial | Version: | 2.9 |
Component: | General | Keywords: | has-patch needs-testing |
Focuses: | Cc: |
Description
I just looked into the DB on a wordpress setup and the otpion table contained an option with an empty option_name.
Not shure if this exactly is a bug but I would argue that an option should have a name otherwise it might not be possible to query it.
Attachments (2)
Change History (9)
#2
@
15 years ago
- Priority changed from normal to lowest
- Severity changed from normal to trivial
Just tested this:
update_option('', '');
it does create an option with an empty name.
but it's not really a bug because it can be queried by get_option() properly. so nothing critical I assume.
#3
@
15 years ago
- Keywords has_patch needs_testing added
- Owner set to ericmann
- Status changed from new to accepted
The patch I just added will check to see if $option_name is empty or blank (whitespace) before adding it to the options table. If the $option_name is invalid, update_option() will return false.
Note: See
TracTickets for help on using
tickets.
I agree. If the option name is empty, it should not be inserted into the table.