Make WordPress Core

Opened 11 years ago

Closed 10 years ago

Last modified 7 years ago

#26410 closed defect (bug) (fixed)

Updating or deleting options via update_option or delete_option leaves blog-details cache object stale

Reported by: codix's profile codix Owned by: wonderboymusic's profile wonderboymusic
Milestone: 4.0 Priority: normal
Severity: normal Version: 3.8
Component: Options, Meta APIs Keywords: has-patch commit
Focuses: multisite, performance Cc:

Description

Updating or deleting 'blogname', 'siteurl', 'post_count' options using update_option or delete_option leaves blog-details cache object stale.

Attachments (4)

patch.diff (1.9 KB) - added by codix 11 years ago.
26410.diff (1.9 KB) - added by kovshenin 10 years ago.
26410.2.diff (1.5 KB) - added by pento 10 years ago.
26410.3.diff (1.9 KB) - added by nacin 10 years ago.

Download all attachments as: .zip

Change History (20)

@codix
11 years ago

#1 @codix
11 years ago

  • Component changed from General to Multisite

#2 @ryan
11 years ago

The *-blog_option cache hasn't existed since 3.4. See [21357].

#3 follow-up: @jeremyfelt
11 years ago

Without the *-blog_option cache portions of the patch, it looks like the intent is to use refresh_blog_details() whenever blog_name, siteurl, or post_count are updated.

Are there specific places in core where these options are updated without refreshing the cache? It seems like we would want to nail that down rather than adding an action on updated_option.

#4 @codix
11 years ago

It was some plugins that were chaging blog_name leaving blog details stale.

Since you can change blog_name, siteurl and post_count with update_option which will leave blog details stale. IMO it makes sense to refresh the blog details when these options are updated.

Thanks!

#5 in reply to: ↑ 3 @uglyrobot
11 years ago

Replying to jeremyfelt:

Are there specific places in core where these options are updated without refreshing the cache? It seems like we would want to nail that down rather than adding an action on updated_option.

Settings->General (blog_name), update_posts_count() in ms-functions.php, and in the "Edit Site" feature where you can change any option.

#6 @jeremyfelt
11 years ago

  • Component changed from Multisite to Options and Meta
  • Focuses multisite performance added

@kovshenin
10 years ago

#7 @kovshenin
10 years ago

  • Keywords has-patch added

Took a stab in 26410.diff. I was also going to remove refresh_blog_details() from update_blog_option() since it'll be triggered anyway, but I'm not sure it isn't going to break anything else, so left it as is for now.

#8 @wonderboymusic
10 years ago

  • Keywords needs-testing added
  • Milestone changed from Awaiting Review to 4.0

#9 @wonderboymusic
10 years ago

  • Owner set to wonderboymusic
  • Resolution set to fixed
  • Status changed from new to closed

In 28881:

In multisite, on the updated_option action, if the option name is one of: 'blogname', 'siteurl', 'post_count' - refresh the blog details cache for the current blog id.

Adds unit test.

Props kovshenin.
Fixes #26410.

#10 @nacin
10 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

This seems unnecessarily slow and complicated. Would it be better to have this?

add_action( 'update_option_blogname', '_wp_refresh_blog_details_on_updated_option' );
add_action( 'update_option_siteurl', '_wp_refresh_blog_details_on_updated_option' );
add_action( 'update_option_post_count', '_wp_refresh_blog_details_on_updated_option' );

@pento
10 years ago

#11 @pento
10 years ago

attachment:26410.2.diff uses the specific action names to run the update function.

This could be cut down even further if we added a get_current_blog_id() call to refresh_blog_details().

ie:

if ( empty( $blog_id ) ) {
    $blog_id = get_current_blog_id();
}

But I'm not sure if that would have any unintended side effects.

@nacin
10 years ago

#12 @nacin
10 years ago

  • Keywords commit added; needs-testing removed

refresh_blog_details() passes its $blog_id argument directly to get_blog_details(), which when given a scalar that evaluates to empty (so, 0) it ends up using get_current_blog_id(). Making it use get_current_blog_id() makes a lot of sense.

I like 26410.3.diff.

This ticket was mentioned in IRC in #wordpress-dev by nacin. View the logs.


10 years ago

#14 @pento
10 years ago

26410.3.diff works for me, too.

#15 @SergeyBiryukov
10 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In 29668:

Simplify the code for calling refresh_blog_details() whenever 'blogname', 'siteurl', or 'post_count' option is updated.

props pento, nacin.
fixes #26410.

This ticket was mentioned in Slack in #core-multisite by jjj. View the logs.


7 years ago

Note: See TracTickets for help on using tickets.