#25705 closed defect (bug) (fixed)
update_option regression in 3.7
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 3.7.1 | Priority: | normal |
| Severity: | major | Version: | 3.7 |
| Component: | General | Keywords: | has-patch |
| Focuses: | Cc: |
Description
The update_option action in 3.7 is triggered after the option was saved to the DB not before as stated in the documentation or as the behavior was prior to 3.7.
Attachments (1)
Change History (6)
#2
@
12 years ago
delete_option and add_option are both before the db query, so update_option should be there too.
calin, how did you noticed this, any plugin which is broken now? Would be nice to know.
#3
@
12 years ago
Not any specific plugin.
I was looking over the code looking for a way to check options before they are commited to the DB.
Note: See
TracTickets for help on using
tickets.
You're right, this hook should have been moved at the same time the DB query was in r25664, and is a regression from 3.6.
See #25015.