[@boonebgorges Keymaster 15 years, 1 month ago]

Put the following lines into your theme’s functions.php file:

if ( !function_exists( 'is_site_admin' ) ) :
function is_site_admin() {
return is_super_admin();
}
endif;

[@boonebgorges Keymaster 15 years, 1 month ago]

Glad to hear it

[@boonebgorges Keymaster 15 years, 1 month ago]

@darrenmooney
`Its unfortunate that BuddyPress was set up this way`

I agree. We’re working toward a solution that will allow for both sitewide forums and group-specific forums. This solution has been delayed by the impending release of bbPress 2.0 and the long BP 1.5 dev cycle. Now that both of these milestones have passed, we will be able to work toward a more flexible forum solution. You can follow that development on tickets like https://buddypress.trac.wordpress.org/ticket/3598

[@boonebgorges Keymaster 15 years, 1 month ago]

The problem with this code is that it hooks to ‘wp’ instead of ‘bp_setup_nav’. Use
`add_action( ‘bp_setup_nav’, ‘CubePoints_List_Menu’ );`

[@boonebgorges Keymaster 15 years, 1 month ago]

No need to bump more than once a day. We are all volunteers!

– Dashboard > Pages > the name of the post you want to edit.
– Find and click the “Screen Options” button. Make sure the “Discussion” box is checked.
– A “Discussion” box should appear. Uncheck “Allow comments”. Update the post.

[@boonebgorges Keymaster 15 years, 1 month ago]

There was no BuddyPress 1.3. See https://buddypress.org/2011/07/buddypress-1-5-beta-1/

You can download earlier versions of BuddyPress at https://wordpress.org/extend/plugins/buddypress/download/

[@boonebgorges Keymaster 15 years, 1 month ago]

You’ll have to provide more details. Child themes work in all my tests, and in all the tests that have been run by those participating in development on Trac.

For instance, this minimal child theme works as expected:
`/*
Theme Name: BP Child
Tags: buddypress
Template: bp-default
*/

body {
font-size: 30pt;
}`

That’s the content of wp-content/themes/style.css.

I’m also not exactly sure what you mean by the last part, about the template pack. The plugin itself really doesn’t contain much “theme” at all. It copies templates, and loads javascript, directly from bp-default.

[@boonebgorges Keymaster 15 years, 1 month ago]

Why do you have BP_ENABLE_MULTIBLOG enabled? Do you really need it? (You only need it if you are going to be using a BP theme, with groups, members, etc, on more than one blog on the network.) If you comment that line out, I bet your wizard will start working.

That said, the fact that it doesn’t work for BP_ENABLE_MULTIBLOG could be a bug. I’ve opened a ticket so it can be checked out. https://buddypress.trac.wordpress.org/ticket/3600

[@boonebgorges Keymaster 15 years, 1 month ago]

Is there anything special about your setup? Did your WP installation used to be WPMU? Do you have the following in any of your config files:
`define( ‘BP_ENABLE_MULTIBLOG’, true );`
?

[@boonebgorges Keymaster 15 years, 1 month ago]

The first item by design. It prevents users from being unwittingly redirected to wp-admin.

To get the WP Admin Bar, put the following in your wp-config.php file:
define( 'BP_USE_WP_ADMIN_BAR', true );

[@boonebgorges Keymaster 15 years, 1 month ago]

The top-level slug is now changed by changing the URL of your Groups page. Dashboard > Pages.

[@boonebgorges Keymaster 15 years, 1 month ago]

Maybe @echoman means that comments are enabled on his pages? Not sure why this would differ between BP 1.2.10 and BP 1.5.

[@boonebgorges Keymaster 15 years, 1 month ago]

Have you gone through the BP upgrade wizard? There should be a “BuddyPress has been updated…” message on your Dashboard or your Network Admin panel.

[@boonebgorges Keymaster 15 years, 1 month ago]

Try renaming the folder wp-content/plugins/bp-template-pack to something like `bp-template-pack-backup`. Then try again. That’ll give you a sense of whether the problem is being caused by the template pack. If nothing else, you can do the same thing for the buddypress directory as well.

After upgrading to the latest BP 1.5, did you walk through the installation wizard?

[@boonebgorges Keymaster 15 years, 1 month ago]

Whoop!

[@boonebgorges Keymaster 15 years, 1 month ago]

Sounds like it’s probably a plugin conflict, especially if it’s been happening since before BP 1.5. What are the other plugins? Have you tried looking at a Firebug console during this process to see if you get any JS errors?

[@boonebgorges Keymaster 15 years, 1 month ago]

good call, @qrahaman – what browser are you using @bigbadboy?

[@boonebgorges Keymaster 15 years, 1 month ago]

Are you running any other plugins? Especially ones that would load javascript?

[@boonebgorges Keymaster 15 years, 1 month ago]

Do you have the Profiles component disabled, by chance?

[@boonebgorges Keymaster 15 years, 1 month ago]

> If I manually install 1.5 RC1, will I be notified and be able to update normally/successfully via the dashboard when 1.5 is released?

Yes.

> Since 1.2.11 is in the works, I’m assuming 1.5 isn’t going to be released anytime soon.

Incorrect assumption There may well be a 1.2.11 for security reasons, as not everyone will want to (or be able to) upgrade to BP 1.5 right away.

> A bit confused why BP RC isn’t installable via the dashboard while bbpress RC is.

Usually betas and RCs are not released through the auto-update channels. bbPress 2.0 is a special case, because it’s the first version that is a WordPress plugin. So there’s no risk of someone using a stable version switching to a non-stable version.

[@boonebgorges Keymaster 15 years, 1 month ago]

@valuser Thanks for your patience, and for the kind words

[@boonebgorges Keymaster 15 years, 1 month ago]

Just to be clear, bp-default has been fixed to do automatically what @karmatosed suggests you do manually. This is only an issue for the BP Template Pack.

In the meantime, why not just use more specific selectors?
`body button
body a.button`
etc. The ‘body’ bit essentially does nothing in terms of which element gets selected, but it forces the browser to give your rules priority because they are formally more specific than those in bp.css. Maybe not the most elegant solution, but better than using `!important`

[@boonebgorges Keymaster 15 years, 1 month ago]

It probably means that the stylesheet for bp-template-pack is being loaded after your custom styles. For now, either use !important, or just use a more specific selector. I’ll open a ticket on Github to see if there’s a more general solution.

[@boonebgorges Keymaster 15 years, 1 month ago]

Are you sure that the styles are coming from bp-default, and not from the bp-template-pack CSS? (It would be very strange indeed if it came from bp-default, unless of course your theme is a child theme of bp-default, in which case you don’t need the Template Pack.)

[@boonebgorges Keymaster 15 years, 1 month ago]

2 – You would have to write some javascript that does the refreshing. I don’t know of any ready-made implementations.

3 – There’s no automatic way to filter these out in BuddyPress at the moment. You could write a function that would take them out of $activities_template when hooked to bp_has_activites.