BuddyPress.org

Did you try googling the error message?

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

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.

@websitevala start off with hardening your WP installation before activating BuddyPress https://codex.wordpress.org/Hardening_WordPress

Hi Auktweena — that plugin is not related to BuddyPress, so you would be better off asking questions on the forum for the plugin, or on the wordpress.org forums.

As for step 3 – that’s standard ‘stuff’ for integrating a plugin’s templates into the theme you’re using for your website. This article gives you an introduction to theme development in WordPress: https://codex.wordpress.org/Theme_Development

Generally, theme work requires PHP development experience. In your case, to get the basics up and running, it looks like you just need to copy some files… you’ll need an FTP client to navigate and copy / move around the files on your website.

There is not difference between WordPress users and BuddyPress users – they are the same thing on a BuddyPress enabled site.

You would be best using WordPress user capabilities, and then some logic in your template code to authorise / reauthorise access based on those capabilities.

Just about anything is possible if you are a good PHP developer.

“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).

Here is an example of how to check a user’s role: http://www.peterrknight.com/get-wordpress-user-role-by-id/

You can also look at this WordPress page for more information on user roles: https://codex.wordpress.org/Roles_and_Capabilities

It would need custom development.

It’s fine integrating with an existing (WordPress) site.

This post while relating to slightly different things may help you get on track.

http://wordpress.stackexchange.com/questions/15633/how-can-i-redirect-user-after-entering-wrong-passowrd

Any plugin in the plugin link above or from WordPress.org must be released under a gpl license. This license grants anyone the right to take and modify, use and redistribute. So yes, you can edit the plugin all you want.

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.

@modemlooper, I don’t know about anyone else but I appreciate the frack out of wordpress, buddypress and automatic!

we’re all friends here and have the same interest: how to make WP+ BP even awesomer!

@frank13 the list mentions one of the most powerful ways to speed up any wordpress install:
https://wordpress.org/extend/plugins/w3-total-cache/

it is a bit of a slog to *properly* select the right features for your particular install but W3 is pretty powerful – just be careful, the plugin is dangerously good – meaning that if you don’t know what you’re doing it can $#&! your site

my suggestion was for two reasons, I don’t understand why testbp.org exists because that functionality can be performed by buddypress.org

also, buddypress.org is for some strange reason very slow

look up your site using this service and see ifyou can find bottlenecks:

http://www.webpagetest.org/result/120720_0E_TC8/ (3.3 second for testbp.org)

http://www.webpagetest.org/result/120720_3N_TDF/ (7 second for buddypress.org)

Is there a reason why you are posting endless duplicates, and typing in capitals… are you a particularly important person, more so than anyone else on this forum?

You can’t delete buddypress.org / wordpress.org (they are the same thing) accounts

I’ve got no idea why Automattic pursue this policy — I’ll agree with you that it seems ridiculous. If you mention it on their wordpress.org forums, quasi-Automattic employees will shout you down (I guess they don’t adhere to the ‘customer is always right’ mode of operating).

Of course, you should be able to delete your account, but you can’t.

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.

Hello,

registration process has nothing to do with BP, it’s WP stuff. For some technical answers to your question, be inspired by reading here:
http://www.esecurityplanet.com/open-source-security/top-5-wordpress-vulnerabilities-and-how-to-fix-them.html

To avoid robot resgistration, there is nothing definitve to do at this time. But to get sure you don’t get a robot in your user list, you can add a mandatory field to your registration via custom profile fields.
For example, “city”. Because this field is custom, no robot will fill it correctly. And most will not fill it at all. Each subscription with “doe” as city name or empty city field can be banned and/or erased from your DB. This will calm down spam activities for a while. The price of this is a constant admin work. But consider that a daily managed site is lesser spammed than a site with randomised webmastering each 31th february… And a site with 50 000 unique visitors will be more attacked that a 70 hits/day site. Just the price of glory, nothing to do with buddypress. [exit]