CUNY Academic Commons

Also seeing the same thing.

seems to be back and working again

The theme on the main site changed to twentytwelve. I've changed it back to bp-nelo.

Seems related to #18235. Will take a look.

I had just been starting to crate a new site when I saw it. But the site isn't a clone.

My 'template' DB option logger caught when this occurred:

[20-Dec-2023 19:36:14] bp-nelo switched to twentytwelve for site ID 1:
validate_current_theme,
switch_theme,
update_option,
apply_filters('pre_update_option_template'),
WP_Hook->apply_filters,
{closure}                                                                                                                                                     

Was anyone working on the site around 2:30pm EDT?

I was active around the site then I think, but only updating Redmine tickets and using the CAC team forum. I noticed the issue right after I posted my forum update, but that was more like an hour ago.

Marilyn Weber wrote in #note-9:

Possibly me - phdhistory.commons.gc.cuny.edu

But I see others from today

Hi Marilyn,

From looking at the server access logs, I can see that you visited the Themes admin dashboard page on the main site at around this time.

Whenever someone visits the Themes admin dashboard page, WordPress does a validation check for the current theme. For whatever reason, the check failed this time and whenever this check fails, WordPress will switch to the default theme, which is Twenty Twelve for us.

This is definitely not your fault, Marilyn! Chalk it up to weird WordPress happenstance.

Boone / Jeremy, I'm not sure why the theme validation check failed this time, but I think to safeguard us from this bug in the future, we can make sure to bypass this theme validation check on the main site with the following:

if ( is_main_site() ) {
  add_filter( 'validate_current_theme', '__return_false' );
}

What do you think?

Argh, sorry! I thought I'd match the theme for my new site (but of course that's impossible)

Sorry for my late reply -- I saw the email from Colin come in earlier today and then looked quickly at Redmine to see that Ray was on the case. Huge thanks for reporting this, Marilyn, for raising the alarm by email, Colin, and for fixing things, Ray!!

Ray, thanks for diving in on this.

Your validate_current_theme callback seems OK to me. I wonder if a more general fix would be a pre_option_template and pre_option_stylesheet filter? This would help to avoid other types of cases (aside from failed validation) where the theme might be accidentally switched.

I wonder if a more general fix would be a pre_option_template and pre_option_stylesheet filter? This would help to avoid other types of cases (aside from failed validation) where the theme might be accidentally switched.

I actually did a version of this with the 'option_template' filter during development of v2.2.0: https://github.com/cuny-academic-commons/cac/commit/2582798911a1e990c07fe7194132438c08b696ee, but this caused a fatal error during the site cloning process. See #19118. We could try a similar approach, but omit the check on the site creation page?