[@djpaul Keymaster 14 years, 3 months ago]

Moderators are BP experts, and help by sharing their knowledge. They don’t have any control over how the site works. For example, I don’t have access to change the theme on the site, etc. The site is hosted by Automattic.

That said, the core team (John, Boone, and myself) are meeting at WordCamp San Francisco in a couple of weeks — and spending a few hours working together on bporg might be something we do.

[@djpaul Keymaster 14 years, 3 months ago]

I only asked because it wasn’t in your wp-config.php snippet above If 3 is the ID of your “lecabinet” site, that should be correct (assuming you’ve put it in wp-config.php).

After you’ve put that in, you may need to re-assign the pages components in the BP settings.

Have you done this since setting the BP_ROOT_BLOG?

[@djpaul Keymaster 14 years, 3 months ago]

We don’t know until we decide to release it. We do know there will be a 2nd RC today or tomorrow.

[@djpaul Keymaster 14 years, 3 months ago]

13. Please provide a list of any errors in your server’s log files. Please advise how I do this.

Your web host can help you with this.

http://lecabinet.lifestyleelements.com.au

Your BP site is (obv.) running on a site in your multisite network. This won’t have site ID = 1 in your network (http://lifestyleelements.com.au will be site ID = 1).

Did you set BP_ROOT_BLOG in your config file (just like Pali Baacsi’s done)? If not, can you try this please? https://codex.buddypress.org/extending-buddypress/changing-internal-configuration-settings/

After you’ve put that in, you may need to re-assign the pages components in the BP settings.

[@djpaul Keymaster 14 years, 3 months ago]

I’ve edited out your KEYs and SALTs.. those are private, too

[@djpaul Keymaster 14 years, 3 months ago]

BuddyPress comes with a default “Name” field in the Extended Profile components. Are you using the Extended Profile component; have you renamed the default Name field, and what are you using that field for?

[@djpaul Keymaster 14 years, 3 months ago]

Not heard of many people trying to move it. Hopefully we can figure out a few things and document it on codex.BuddyPress.org for the future.

1) If you haven’t already, you’ll need to set BP_ROOT_BLOG in your wp-config.php (see https://codex.buddypress.org/extending-buddypress/changing-internal-configuration-settings/).

2) All and any links inside activity stream items are hardcoded, so you would need to adjust by editing the appropriate records in the wp_bp_activity table in the database.

3) You’ll need to go to the site which you’ll be using as the main BuddyPress site, and create new Pages in the WordPress admin. Afterwards, also in the WordPress admin area, go to the BuddyPress > Pages screen, and pick your newly created pages from the dropdown boxes alongside the list of components which you have active.

You may already have done this, but this is what I think of first.

[@djpaul Keymaster 14 years, 3 months ago]

Please make your own topic. The affect may be similar, but the cause might be difficult. We’ll need all the type of information that Abbie provided in this topic for your site to begin to understand what might happnening.

[@djpaul Keymaster 14 years, 3 months ago]

Er, wow. It certainly shouldn’t be causing problems with the type of usernames that the two users on your site have. The activity redirect is very odd as well. Yes, make a new thread, if only because this one says “resolved” in the title.

[@djpaul Keymaster 14 years, 3 months ago]

Links like these any good? Not sure if we can manipulate the trac download URLs: https://buddypress.trac.wordpress.org/changeset/HEAD/tags/1.5/bp-themes/bp-default?old_path=%2F&format=zip

If anyone wants to talk about issues other than 1.6-RC1 in this thread, please make a new thread. Let’s keep this one on topic from now

[@djpaul Keymaster 14 years, 3 months ago]

Did you try googling the error message?

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

[@djpaul Keymaster 14 years, 3 months ago]

This is why beta/RC testing helps us identify areas that we’ve inadvertently broken, so we can address any regressions.

Other argument: why can’t we make minor changes to the theme? In 1.6, we’ve made some JS and CSS improvements to allow parts of those things to be more easily overridden by child themes. I think that’s the extent of the changes, though I can’t remember until I/we write up the release notes.
Functionality hasn’t changed. The more drastic theme changes in the old 1.5 did cause some upgrade complications, and we’ve learnt from that.

The themes are versioned. I don’t believe CSS/JS tidy up merits a “new” theme. If/until BP-Default is put on WordPress.org’s theme repository, if someone wants to make e.g. a codex page with links to .zip of BP-Default from each BuddyPress, go for it.

At any rate, we all know the pain points in building a BuddyPress theme based off BP-Default at the moment. Future releases of BuddyPress won’t ship with a theme, so this problem will eventually go away.

[@djpaul Keymaster 14 years, 3 months ago]

Need to finish writing the change log too

@mercime We’d have hope theme authors were testing their themes when we were in beta — but if you find any regressions in BP-Default in RC, please raise trac ticket

[@djpaul Keymaster 14 years, 3 months ago]

As people might be know, Web Notifications (http://www.w3.org/TR/notifications/) are similar to how Growl displays its notifications, but are very different in most ways. You can see them in Safari 6 and Chrome today. In OS X Mountain Lion, notifications appear in the new “Notification Center” (http://photos.appleinsider.com/notificationcenter_hero1.jpg — the grey vertical column on the right). I believe they will also appear in iOS 6’s existing notification panel, but I haven’t tested that.

I don’t know if Web Notifications support will be added in the *next* version of BuddyPress, but I’m going to try to get them into a future version of BuddyPress. I’m actually playing with some implementation ideas for another plugin that I am working on, so by the time it comes to BuddyPress, it ought to work nicely.

[@djpaul Keymaster 14 years, 3 months ago]

“Forum Topics” and “Forum Replies” are added by BuddyPress, and work for bbPress 1.x (aka Group Forums).

“Topics” and “Replies” are added by and are work for bbPress 2.x content (aka Site Wide Forums).

If you’re using bbPress 2.1, you don’t need to use Group Forums. Go to your WordPress admin > Settings > BuddyPress, then Components, and disable Group Forums.
Then go to the bbPress Settings page, and if you scroll to the bottom, there will be a “Enable Group Forum integration” box (or similar).

[@djpaul Keymaster 14 years, 3 months ago]

Neither BP or WP comes with a “notify me of new comments by email” by default, so it’s some other plugin. For example, Automattic’s Jetpack plugin’s comments feature adds this.

[@djpaul Keymaster 14 years, 3 months ago]

It’s most probably a PHP fatal error to do with a lack of memory.
Please ask your host to look in your server’s PHP error log, and let us know what message you get.

[@djpaul Keymaster 14 years, 3 months ago]

Please answer this question from Roger

Are you already logged in (if you are, you will be redirected away from registering)?

[@djpaul Keymaster 14 years, 3 months ago]

I’m glad you’ve figured it out — but I can’t see your site (wants me to log in). Please can you share a URL of a member profile that (was) causing the redirect? Just to understand why the compatibility mode toggle made it work.

[@djpaul Keymaster 14 years, 3 months ago]

Current/old versions of BP had this strange quirk where, if something should really 404, it actually redirects you to the home page. We spent some time straightening this out for 1.6.

Can you share a couple of sample links of these members that redirect to the homepage?
Please also confirm that if you create a regular WordPress page, write some content, then publish, you can access it as usual from the front-end — also, please share the URL of this test page.

Just trying to ascertain if your rewrite rules are working correctly for WordPress content, and why BP might be redirecting.

[@djpaul Keymaster 14 years, 3 months ago]

Wow, very useful. Thanks TheBeardedOne

[@djpaul Keymaster 14 years, 3 months ago]

Closing topic.

[@djpaul Keymaster 14 years, 3 months ago]

Sorry, that’s what I meant (I’m not very well-versed in this area, yet). It appears validator users import .po files. From https://translate.wordpress.org/getting-started

Importing external files

There may be the case where a validator needs to import translations from an external file (current supported formats are .po, .android and .rrc). When the file is imported, only untranslated strings will be written. Also, if the imported file contains original strings not present in GlotPress’ list, those strings will be ignored.

[@djpaul Keymaster 14 years, 3 months ago]

You can import .pot files onto GlotPress, so I don’t think that’s a problem. And, yes, of course BuddyPress needs translation.

I am going to pick up this issue and investigate. I will update on here and on bpdevel.wordpress.com in due course.

[@djpaul Keymaster 14 years, 3 months ago]

BuddyPress doesn’t have much to do with this. WordPress requires users to be the ‘administrator’ role to delete user accounts. You could change this with a role changing plugin, by giving the appropriate capabilities directly.

Posting on the front page is a theme issue more than anything (assuming you’re talking about blog post).