Introduce blog-archived.php and blog-spam.php

[johnbillion]

When Multisite is active and an archived or spammed site is loaded, WordPress first looks for a file in the content directory called blog-suspended.php and loads it if it's found.

Two problems:

1. The file name is counter-intuitive because 'suspended' isn't the name of a status that a site can have.
2. It's not possible to serve a different file for spammed and archived sites.

The upcoming patch introduces support for blog-spam.php and blog-archived.php for sites with the respective status. It will fall back to blog-suspended.php for backwards compatibility.

[johnbillion]

Patch

[jeremyfelt]

24061.2.diff​ is johnbillion's patch refreshed against trunk. Adds blog-spam.php and blog-archived.php as possible drop in templates.

Moving to 3.7 for discussion

[Ipstenu]

Would this be appropriate to loop back to #17164 ? We still have the four options, and only having custom pages for two, when they're all hella confusing. I would think maybe dropping some of the options, if we're not going to make them useful, would make sense.

spam
deactivate
delete

Then we can sort out archive, which acts like an almost delete, later.

[nacin]

We should really just fire an action before all of this and forget these files exist. :-)

[jeremyfelt]

Replying to nacin:

We should really just fire an action before all of this and forget these files exist. :-)

24061.3.diff​ goes this route. There's already an ms_site_check filter, so I went with ms_site_check_status for the action. Also removed the unused $wpdb global and replaced blog with site where appropriate.

[DrewAPicture]

If we go the action route, we'll need docs for it.

[jeremyfelt]

24061.4.diff​ introduces the ms_site_check_status action with docs. The new patch avoids the massive green/red caused by my overeager attempts to replace all mentions of blog with site. :)

[DrewAPicture]

Replying to jeremyfelt:

24061.4.diff​ introduces the ms_site_check_status action with docs. The new patch avoids the massive green/red caused by my overeager attempts to replace all mentions of blog with site. :)

• 'Object' should be lowercase
• Can you be a little more descriptive than 'Contains site details' or point somewhere that has that information?

For the descriptive route, something like this:

* @param object $site An object containing the site's ___, ____, and ___.

For the @see route, something like this would work (notice no period with the @see):

* @param object $site Contains site details. @see some_function()

[jeremyfelt]

Refreshed docs for the new action in 24061.5.diff​.

[nacin]

I was kind of kidding about the action, but it actually makes a lot of sense.

Also, blog-suspended.php could also be used to "route" users to a custom blog-archived.php or blog-spam.php.

I'm not sure we need to actually introduce any more files here. They just feel really restricting and hacky, and they have "blog-" in the name, and more commonly would be a theme template (for the main site), or something.

[nacin]

I'll be honest, the existing ms_site_check filter is enough to include and die. It doesn't let you alter the function's return value, but A) neither does the action, and B) the only return value that is valid for this function is true anyway; the alternative is to specifically do something and exit.