You need to look at the other section in dashboard ‘Network Admin’
? Are you sure you have MultiSite enabled ?
Thank you for a reply!
Yes, I am pretty sure that MultiSite is enabled.
I did the following check:
From the ‘Network Admin’ I added new site and called it ‘SubSite1’; the URL of SubSite1 is: xyz.com/SubSite1/.
The SubSite1 has it’s own blog where I can add a post, etc. The blog of SubSite1 is also listed in the top level site: xyz.com/blogs/.
So, there is a capability to have one blog per one sub-site.
The question still remains, how can one blog per one BuddyPress user can be enabled?
I include the contents of wp-config.php for your reference (just in case you wonder what is there):
…
I have some passowrds infor here…
…
define(‘WP_DEBUG’, false);
define(‘WP_ALLOW_MULTISITE’, true);
define( ‘MULTISITE’, true );
define( ‘SUBDOMAIN_INSTALL’, false );
$base = ‘/’;
define( ‘DOMAIN_CURRENT_SITE’, ‘cfbp.dev’ );
define( ‘PATH_CURRENT_SITE’, ‘/’ );
define( ‘SITE_ID_CURRENT_SITE’, 1 );
define( ‘BLOG_ID_CURRENT_SITE’, 1 );
/* That’s all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);
If you configure multisite to allow blog registrations, when a user registers an account on your BuddyPress-powered site, it will ask for/prompt for the name of the site (blog) to be created. BuddyPress then tells multisite to register that new site; there’s very little involvement here as far as BP is concerned.
Thank you for a super fast reply. However, I red documentation, and it is for the previous version of BuddyPress / WordPress.
Site Admin -> Options -> Allow New Registrations > set to: “Only Logged In Users Can Create New Blogs” – is no longer available!!!
Could you guide a BuddyPress/WordPress noob please?
If i need to change the code, I am fine with this – I have a software development background.
== Site Admin -> Options -> Allow New Registrations > set to: “Only Logged In Users Can Create New Blogs” – is no longer available!!! ==
It’s now available at Network Admin > Settings > Settings > Registration Settings – “Logged in users may register new sites.”
Thank you @mercime! I was just able to create a blog. But now I am confused!!!
For example, in my prompt, i entered blog name which appears directly under the root of the site. Ex: xyz.com/MyNewBlog1/ – this is a bit confusing…
Whenever a user is creating a personal blog, he/she really creates a sub-site (with its own template and everything else…) – is this correct?
If yes, then is it possible to force the new blog URLs to follow this patters:
1) /members/username/blogs/MyFirstBlogName/
OR
2) /members/username/blog/MyFirstBlogName/
OR
3) /members/username/MyFirstBlogName/
If one of the above patterns is used, then it is easier to understand that the blog belongs to a user, rather then the top-level site.
Thank you again!
PS: Wow – this community support is awsome. Much better than some of the paid support. Lets not get into names here …. .
All those patterns are possible (i think) and have been asked around here in the forums before. I can’t think of the threads but you could search around and try to find those solutions. From what I understand they do take a lot of working. I think I may have even asked that before (with “members/username/blog” only)…but saw that it was too hard for me to do! hehe.
If I understand your question correctly, “is it possible to have one blog per user” — by default registered users can create as many blogs as they want. There is a plugin that limits users to only have 1 one blog called “Limit Blogs Per User”. BuddyDev.com
hope that helps…
@binary.digits There is no easy way of setting those styles of “patterns” for the blog URLs with the current version of BuddyPress. You may be able to mimic it by using .htaccess 304 redirects but this can be complicated and I’m not sure if it would work well.
It can be done and I’ve seen it done where the blog is more akin to an extended profile and created on the fly per user but it really isn’t trivial and I don’t have the actual detail and even if I did it would take a lot of explaining, it’s very much a bespoke piece of core customisation – one draw back of a site for every user is that with a moderate user base ~800 -1000 you have a pretty large DB in terms of tables and will need to ensure your server DB is tweaked and optimized as much as possible as backups can fail trying to lock tables numbering in the thousands.