BuddyPress.org

Do you have WordPress Single-User or Multi-User installed?

^
I did this and my base wordpress installed blog added to the blog directory and become a blog by everyone who have registered. How can I remove the main site in the directory and how can I not make this as everyones blog

Hi modemlooper, I tried what you said. Actually in my theme it was exactly like you stated. However, after editing in wordpress theme editor, nothing changes…. what can be the problem?

This currently isn’t possible.

Such a feature has been mentioned before and is on a list of requested features, so hopefully something will materialize in the next few months.

I would check in the BP plugin repository: https://buddypress.org/extend/plugins/

Is this plugin what you’re looking for? https://wordpress.org/extend/plugins/buddypress-real-names/

And this plugin does the exact opposite: https://buddypress.org/community/groups/buddypress-usernames-only/

Howdy. I’m experiencing the same problem. Not only group creation is involved. After not being able to continue to the select group avatar step whilst creating a group. I go back to the groups page index and the group is there. However if I try to create a topic I get the error: “There was an error when creating the topic”.
Though I only have one group created, the group count says 4!.
Regarding the discussion capabilities for groups I have installed bbpress through the built in installer in buddy press. bb-config.php looks okay. All the involved directories have the right permissions.

I deleted all the files from the server, dropped the db, re-installed from ground without any additional plugins and it still produces the same error.

I wonder if any of the developers can give us a hint on what to check.

Regards!

Martin

PS: I’m running WordPress 3.0, Buddypress 1.2.5.2.

BuddyPress 1.2.5x hasn’t really been built with the WordPress 3.0 menu system in mind. I know we’ve got some page title bugs on a WordPress network/WPMU install which I hope to get time to fix in a couple of weeks so this might clear up then.

If you’re using a child theme of the BP default theme, you’ll have to alter the index.php and archive.php files in your template.

Thumbnails require a plugin or using WP’s post thumbnail feature:
http://markjaquith.wordpress.com/2009/12/23/new-in-wordpress-2-9-post-thumbnail-images/

The layout is more of a general issue. Look up grid based layouts on Google and fool around with floats in CSS to do what you want.

I’ve gone through all the BuddyPress files and inserted ‘/index.php/’ after each of the root_domain elements and that fixed it.


. clean_url( $bp->root_domain . '/index.php/' .


Someone else could probably suggest a better way of doing it that links into WordPress’s permalink structure.

@sadr
https://wordpress.org/extend/plugins/buddypress-restrict-group-creation/ does this already.

You can set whatever defined wp_cap/role levels assigned to:
Create group capability
Create group forum capability
Create private group capability
Create hidden group capability

Hi dpolant. I’m also from the jMonkeyEngine project. We’re happy to see you’re extending this neat plugin.

We were up late working last night, so in case Normen didn’t make perfect sense about the forum restriction, I’ll reiterate:

What we’re looking for is a way to restrict users from creating a forum once we’ve assigned them a group. I think at its simplest, we’d want site admins to be the only ones who can enable a forum on a group. That way if group admins really think their group needs a dedicated forum, they’d just have to ask us (naturally we’d clarify the process to our users).

Our site doesn’t have open group creation, so we can easily estimate no more than 1 group every week, meaning enabling-by-request would be perfectly manageable at least in our case.

Now for something more advanced, you could consider playing with the Role Scoper plugin:
https://wordpress.org/extend/plugins/role-scoper/
It’s definitely the most comprehensive permissions-plugin I’ve tested, and it’s actively developed. What you could do is make your plugin integrate with his, so that if both plugins are present, a simple group is created, like ‘forum creator’. Now all we as users would have to do is associate the WP usegroups that should have access to forum creation with the custom ‘forum creator’ group.

Maybe this would be easier just added directly to the role-scoper plugin though, so I’ll suggest it ^^

So yeah, enabling-by-request would suit us just fine!

You should be able to export your DB from GoDaddy using phpMyAdmin. I have done this and it works fine. You have to follow the instructions posted by mercime on the WordPress Codex.

Now, if you are trying to IMPORT your DB the same way on a new host DB, hosts like 1and1 limit your MySQL upload to 2MB only. This means you have to use the command line with linux commands to perform a “mysqldump”. Performing this action, will backup your DB file to a folder. Then, you FTP it down to your desktop. Upload it to the folder on your new server and dump it into the new DB by performing a “mysql” action. You can find the commands in both links provided by mercime.

We just exported and imported in this way from GoDaddy to 1and1. Took me a minute to figure out how to perform a mysql action, but once I learned how to do it, it was a breeze.

What you might find, is that on your new host you don’t have enough php memory. That may be an issue. I’m facing that right now.

These will help you
https://codex.wordpress.org/WordPress_Backups#Backing_Up_Your_WordPress_Site
https://codex.wordpress.org/Backing_Up_Your_Database
https://codex.wordpress.org/Restoring_Your_Database_From_Backup

It’s one of or a combination of two issues: the folder permissions may not be set correctly (these can normally be corrected via a decent FTP client folders generally need 755 and files 644)

Check the WordPress codex for the correct permissions required

The other issue and more likely the problem here is that the server group hasn’t got the correct permissions to create and write to directories, if you are on shared hosting you may need to contact your host to get this sorted out and also ensure that PHP ‘Safe Mode’ is turned off.

You should create a network of wordPress sites.

https://codex.wordpress.org/Create_A_Network

during the process you have to add some code in your .htaccess files.

Is your original database intact but just associated with a different domain now? If so, maybe you just need to change the siteurl in the database itself by going into Cpanel > myPHPadmin > your wordpress database > wp_options table (or whatever prefix you gave it if you changed it from the default wp). The siteurl field is the first row. Changing it to the right siteurl should allow you to log in to the dashboard again.

Beyond that, I’m not sure what you’re asking, but if my suggestion isn’t too off-base, maybe you’ll know how to proceed from there.

Marian

I’m getting a different result. Never fear, you can download BuddyPress Template Pack from wp.org – https://wordpress.org/extend/plugins/bp-template-pack/

A plugin’s readme.txt file is your friend. It can answer many of the common questions you may have about a given plugin. Your question is answered on the first sentence of the Installation section.

From the Installation section of the readme.txt file for BuddyPress Links: “Notice: This plugin is under heavy development, and is not recommended for production environments!“

This is the same information that is displayed on the plugin’s page here on BuddyPress or within the WordPress Plugin Repository.