Opened 3 years ago
Closed 3 years ago
#11506 closed defect (bug) (fixed)
Creation of unnamed option is possible
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | lowest | Milestone: | 3.0 |
| Component: | General | Version: | 2.9 |
| Severity: | trivial | Keywords: | has-patch needs-testing |
| Cc: | ericmann |
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)
- 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.
- 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.
- Keywords has-patch needs-testing added; has_patch needs_testing removed
Patch looks good, but you could loose the comentary since it's obvious what the code does.
You could update the function documentation instead.
Same patch as above, updates function documentation instead of adding commentary.

I agree. If the option name is empty, it should not be inserted into the table.