WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #18955


Ignore:
Timestamp:
10/15/2011 10:09:19 AM (7 years ago)
Author:
duck_
Comment:

As noted by your steps this bug requires code to ignore the site_option API to be triggered (so the DB and cache aren't in sync) and shouldn't happen in core.

Attached 18955.notoptions.diff example patch for adding a notoptions cache for site-options. I think this is the most sensible option. I'd say that 1 was the least preferable.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18955

    • Property Keywords has-patch added
  • Ticket #18955 – Description

    initial v1  
    88Options for fixing
    99
    10 1- change the get_site_option in update_site_options to not use cache
    11 2- add a notsiteoption cache and cache the non-existence of the site option
    12 3- don't cache the default value in get_site_option
     10 1. change the get_site_option in update_site_options to not use cache
     11 2. add a notsiteoption cache and cache the non-existence of the site option
     12 3. don't cache the default value in get_site_option
    1313
    1414Option 1 is quick & easy