#5223 closed enhancement (fixed)
Stop offering bp-default on new installations
Reported by: | boonebgorges | Owned by: | boonebgorges |
---|---|---|---|
Milestone: | 1.9 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Templates | Keywords: | has-patch needs-testing 2nd-opinion |
Cc: | mercijavier@… |
Description
As of 1.9, we should no longer offer bp-default as an installable theme for new installations. This will be the first step in the longer-term task of removing bp-default from the BP codebase, and spinning it out into its own theme. See #5212 for more general discussion.
My proposed solution is to bail out of registering the bp-themes
theme directory unless one of the following cases obtains:
- The current theme is bp-default (get_stylesheet())
- The current theme is a child of bp-default (get_template())
If anyone thinks that this is too aggressive, we could do the above *only for new installations*. How can we tell what's a new installation? We could add something to the 1.9 upgrade routine that sets a flag in the database - something like bp_register_bp_default
- to true, while that value would be set to false (or unset) for new installs.
Patch incoming for the simpler, more aggressive option.
Attachments (1)
Change History (9)
#2
@
11 years ago
One edge case not handled is if BP-Default is active on some site in the network (in multisite).
#4
@
11 years ago
One edge case not handled is if BP-Default is active on some site in the network (in multisite).
Thinking about this, and I'm not sure it's much of a problem. The theme directory *would* be registered on sites that are running bp-default, while it would *not* be registered elsewhere. I'll have to run some tests, but it seems like it should just work.
#5
follow-up:
↓ 6
@
11 years ago
- Owner set to boonebgorges
- Resolution set to fixed
- Status changed from new to closed
In 7569:
#6
in reply to:
↑ 5
@
11 years ago
Replying to boonebgorges:
Installations where bp-default is not already in use will no longer see it listed on Dashboard > Appearance.
I just had a case where a client switched away from a theme based on bp-default, couldn't switch back and went into a frenzy.
Not sure if this is a serious issue or not, just some feedback.
See 5223.patch. (Sorry for the crummy function naming - better suggestions welcome.)