Search Results for 'Create an Account'
-
AuthorSearch Results
-
August 4, 2009 at 9:58 pm #50607
In reply to: Sign in with Twitter?
Eric Wood
Participantyes, full integration… I’ve noticed however that it creates a SECOND account if the member already has one, so it’s either log in with Twitter credentials, or with WordPress credentials…. site seems to consider them as separate accounts.
I explain this to my users at http://outgaylife.com/wp-login.php
July 30, 2009 at 5:23 am #50323In reply to: Live Chat for BuddyPress
ajonesma
ParticipantJust go to http://ww2.toksta.com and create an account and setup your chat the way you want it and click ‘Create Script’ and choose ‘WordPress’, upload it to the /wp-content/plugins dir and follow the readme file directions. It does work because I have it working on my site right now.
July 30, 2009 at 1:51 am #50316In reply to: BuddyPress and Shared Hosting
Jeff Sayre
ParticipantThere is more overhead with WPMU, but the biggest issue is whether a site allows its members the option to create blogs and how many active blogs the site has. So, running single-version WP could help reduce the load in theory.
But, BuddyPress can also be a bandwidth, memory, and harddrive-space intensive plugin suite. It all depends on a site’s user activity and what additional BP-dependent plugins a site installs and activates.
For instance, if a site uses a media plugin that allows users to upload photos, mp3, and video files, then a low-powered hosting account could get swamped even if it is “just” running single-version WP.
July 26, 2009 at 10:35 pm #50069In reply to: Forum Integration: HELPING HINTS
David Lewis
ParticipantLooks good Rohan. It’s kind of a pain that we have to create three themes for a consistent look… a BP home theme… BP member theme… and bbPress theme… but I guess there’s really no way around that.
How did you get the BuddyPress bar to show up on the forums page? Copy/Paste? I haven’t played with that yet. I found that I had to hard code my main nav bar in the forums header template as well. Which kinda bugs me… but that nav will rarely (if ever) change.
Thanks for the answer about the account. I was pretty confused about that.
July 21, 2009 at 8:11 pm #49732In reply to: 1 email address, mutiple accounts?
thebloghouse
ParticipantI have just come across sub-addressing myself yeah – looks like the perfect temporary fix

My own domains email accounts don’t allow it easily but I will just create 1 gmail account per user that needs multiple accounts.
Thanks for your help guys.
July 20, 2009 at 2:25 pm #49638In reply to: 1 email address, mutiple accounts?
John James Jacoby
KeymasterThere are plugins to allow easy user switching, and I think that would be your safest bet. This way they can just create users in the admin area with new email addresses, and switch to being that user without logging in or out.
Because WordPress uses email addresses for verification and authentication purposes, it can’t really have the same email address multiple times safely.
July 16, 2009 at 5:35 am #49413Mohit Kumar
ParticipantRequire help….
I have almost implemented the sliding box..But i am having some problems..
I used<?php do_action( 'bp_adminbar_logo' );?> <?php do_action( 'bp_adminbar_menus' );?>to implement the menu..and it shows menu like this—
My Account* Activity
o Just Me
o My Friends
* Profile
o Public
o Edit Profile
o Change Avatar
* Blogs
o My Blogs
o Recent Posts
o Recent Comments
o Create a Blog
* WireHow can i implement different menus at different place??
and how can i call the register page .into the box…
thanks for helpJuly 13, 2009 at 5:55 pm #49209In reply to: Blog registration drops data fields at signup?
r-a-y
KeymasterIf anyone could tell me how to remove the blog registration part from the mysite.com/register so that all the visitor can do at that point is to create a user account, I’d be thrilled!
Hi mlemberg, read this:
https://buddypress.org/forums/topic/default-to-just-a-username#post-14828
Requires hacking a core file and a little bit of CSS to hide the “Create A Blog” block.
If anyone knows a better way, let us know.
July 13, 2009 at 10:15 am #49189In reply to: Blog registration drops data fields at signup?
mlemberg
ParticipantBump!
Is there anyone who can help me?
If anyone could tell me how to remove the blog registration part from the mysite.com/register so that all the visitor can do at that point is to create a user account, I’d be thrilled!

I do not want to completely switch off the blog functionality from Buddypress. All I want is to prevent the option from occuring at the registration stage.
Please help me – it’s kinda urgent!
July 10, 2009 at 11:06 am #49012In reply to: Unable to post on my website in forum discussion
gen-superman
Participant$bb->bb_xmlrpc_allow_user_switching = true;
TheEasyButton
Oh, thank god you exist in this world

You were right…
I actually made several mistakes, that I wanted to point out, and then my final post on this topic will lead to the url to where I found out how to fix my issues.
But, thanks to TheEasyButton and John James Jacoby for their help. As it truly helped.
Also a big thanks to Trent Adams for writing up that helpful tutorial found sticky on these buddypress forums.
I had forgotten several steps
– Add the code to the bottom of the bb-config file, that TheEasyButton mentioned above.
– Disable forum discussions on new or existing group forums, and then re-enable them after they are created or working.
– Needed to be signed in to both WPMU and BBPRESS as the administrator and not the key master. I had forgotten to set up my new admin account to have admin priviledges on the bbpress side. Woops… like big woops.

There are two MAJOR things I wanted to point out.
– If you tried to intall bbpress 1.0.1 by itself as fresh install, then I kept getting a major error that said, “Could not create new forum” during installing. I had to install bbpress 1.0 first to a new SQL database, then I removed all the files from the BBPRESS folder, and then uploaded the new bbpress 1.0.1 files. Which once I installed this new version, the SQL database was already set up for bbpress, so it just treated it as updating. Someone at BBPRESS really needs to fix that, as I’m sure many people are running into that problem.
– The last thing I would like to mention, is that I didn’t really see on the tutorial article about helpful forum integration on the buddypress forums, about the cookies. I probably just missed that part, but it is very important that even when you overwrite your bbpress files, that when you over write your bb_config file, that you make sure the cookies are set and match wp_config cookies, of course with the bb_ prefix within the cookie parameters. Such as:
define( ‘BB_AUTH_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’ );
define( ‘BB_SECURE_AUTH_KEY’, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
define( ‘BB_LOGGED_IN_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’ );
define( ‘BB_NONCE_KEY’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’ );
define(‘BB_AUTH_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
define(‘BB_LOGGED_IN_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
define(‘BB_SECURE_AUTH_SALT’, ‘XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX’);
define( ‘WP_AUTH_COOKIE_VERSION’, 1 );
If you forget that last line, then it will definitely mess up everything too. But, the plugins placed into the right directories are the most important. This also doesn’t include that some buddy press plugins require that you move certain files from those plugins into your default buddy press theme. You also have to have a default buddy press theme in order to see everything properly too.
One more thing,
Hopefully, one day, someone will create an easier way to do all of this. Everything is so scattered all over the place, and right now, it can take a newbie several hours to get everything set up the way it is suppose to be. So, hopefully, somebody might create a program or something that will just automatically do everything for you or done through a central area at least.
Thanks again for the help,
my problem is solved.
July 9, 2009 at 3:34 pm #48935Jeff Sayre
ParticipantBrian-
You should ask this question as well in the WPMU forums as it is the WPMU registration functions that allow usernames to be created with a space in them and it is the authentication functions (when a user logs in) that then has an issue with the space.
I do not know if this has already been addressed in a newer version of WPMU, but Andy is aware of this issue and I assume that he has communicated it to Donncha.
You are limited in what you can do, but deleting the username is not advisable.
You could manually edit each user account that has this issue. If you do so, you’ll of course first want to make sure you have a backup of your database. But, if you go this route, you’ll need to tell each of those affected users that you have changed their login credentials. Otherwise, they will not be able to log in.
As far as changing the display name, that will have no affect on the username. Those are two different pieces of data.
July 8, 2009 at 8:21 pm #48840In reply to: Different user account types
peterverkooijen
ParticipantThere are several commercial plugins that create membership levels. You’d probably need custom code to connect the levels to the functionality you describe.
If you figure it out, let me know.

Or contact me if you want to pool resources.
July 6, 2009 at 12:15 am #48607In reply to: Disable name change in Profile?
gen-superman
ParticipantYour right, I tried this again and it worked fine… See, what I thought was that with this code, that the display name would be grayed out completely, which I don’t think it is for Admins, but regular users might see the box empty. Currently, users can still edit their display name from the bppress profile with this code, BUT when they go to save it, the changes won’t actually take place, which is a very good thing. I understand the purpose of having a login username and a display name, which I guess is fine for security purposes. But, for old school people like me, I prefer one username and one login name combo in one.
Now, the user can still change their display name by going to the wp-profile area, and then choose which display name they want to go by. Which I guess is not that bad. But, I guess, I would still prefer to find a way to shut that off in the near future.
But, then again, WP is so picky about using duplicate e-mails. I have not found a way to allow for users to register a new account with the same e-mail address. That can be a real pain in the rear, especially if you are testing the user registration process yourself. So, that leaves users that want to change their display name in the future with the option to change it in the WP-Profile area. Although, I prefer to find a way to shut that off entirely. But, I can’t just get rid of the WP-Profile link, because it has the ability for users to change their password and so far I don’t see a way for BP to allow users to change their password in the BP areas? Unless someone knows a way to add that option in the users BP-profiles or knows a link that leads directly to the option for a user to change just their passwords?
I want to say that I am impressed that by adding this code to either its own blank .php file and placing it into the mu-plugins, that it worked so nicely. I did try it in the regular plugins directory and it did not take effect. I also had embedded it as you ‘Jeff Sayre’ had stated in the bp-themes template functions.php and that worked fine too.
I then did one more test with this. I registered a new user through the registration process, and of course the Username field comes up due to WP requesting it and the BP-Display Name field comes up due to BP requesting it. Luckily, because of the code, it didn’t matter what the user entered in the BP Display Name, it would only recognize the username from the WP Username field in the registration. Which, yes I know, they are two totally different things, but I feel more at ease that this actually worked.
Although, now users that register will be confronted with both of these questions, and I guess if they think their entering a display name for the BP-Field they will be very disappointed to find that their username will take default.
So, for now, I guess the only remedy is by changing the label ‘display name’ that BP profile uses to ‘username’. Because, although a person enters a display name in the registration part of the BP display name field, it doesn’t show up in the WP-profile area as a nickname option. Either because of the code conflicts or BP wasn’t made to do that. Not sure. OR I guess you could just relabel to inform that display names can only be changed or created in your WP-Profile area… Oh… So confusing…
My hats off to ‘Jeff Sayre’ and ‘Andy Peatling’. I truly hope that this might become an actual option in the newer bp press versions.
July 5, 2009 at 6:33 pm #48586In reply to: Disable name change in Profile?
Jeff Sayre
ParticipantI tried very hard to get this to work, and I can not get that code to work, even in the default template or even by creating a blank .php with pasting in the code listed above to upload to the mu-plugins directory.
First of all you should not be placing the code in mu_plugins. Either place it in your bp-custom.php file, create your own plugin that resides in /wp-content/plugins/, or put the code in your member theme’s functions.php file.
But, in the BP Profiles section, the users can simply change their login username to anything they want. This will obviously lead to database errors and people changing their usernames to cause conflicts.
Where do you see the option in BuddyPress to change your login username? The only option you have is to change your display name. This is an entirely different piece of datum.
Yes, when a user registers for a new account, if they choose to enter the exact same datum in the username field as the “Full Name” field, then that is their choice. But, this data is stored and used in different ways. The datum from the “Full Name” field gets placed in two different tables: it populates the display_name field in the wp_users table and it is recorded in the wp_bp_xprofile_data table corresponding to the meta field entitled “Full Name” in the wp_bp_xprofile_fields table.
When a user decides to edit their “Full Name” field via BuddyPress, the changes to that piece of datum have no affect on the login username field stored in the user_login field of the wp_user WordPress table.
So, on the same registration page, you have two questions requesting for what their username is going to be. This is quite ridiculous, and so far their is no way to shut that part off. Does anyone have any ideas?
This is not correct. These fields serve different purposes as detailed above. One field is the user_login, the other is the user’s display name.
July 5, 2009 at 3:48 pm #48572In reply to: BuddyPress – 'Create Group' PROBLEM
boonika
ParticipantOK. Here’s what happened:
I created a group called ‘Extraordinary Video Work’. I also invited friends… we had some Wire activities… and so on.
Than I clicked My Account/Groups/Create a Group to create a new, ‘Fonts’ group. Did everything as I did for the first group. I clicked Groups from the main menu and realized that the previous group was transformed into this new group. List of members and Wire posts were the same but name of the group (‘Extraordinary Video Work’ was changed to ‘Fonts’) and description were changed. I tried several times. If You want I can create a profile for you so you ca try it yourself. Just give me your email. Mine is pinkforrest[at]gmail[dot]com.
July 5, 2009 at 6:23 am #48558In reply to: can a user enter his own password at registration?
gen-superman
ParticipantSince nobody has figured this out yet, I was wondering, maybe there might be a different way. Such as when people signup, it automatically logs them in upon signup. Then while it automatically logs them in, it leads them to the change the password/profile page.
Although, it would be great to see buddypress profile section to actually have the option to change passwords, as right now we have no other choice but to edit the passwords in the wp profile area.
Hopefully, somebody will get this figured out, as it is a horrible idea to send out e-mails in this manner, because most of the time the e-mail could get lost or placed into the spam areas or the e-mails can become delayed and users never check for it, or they just don’t bother to login because they are concerned that they may not have the option to change their passwords so readily.
Time will tell. But, there needs to be a way to automatically log people in upon them creating their own account, then they can change their passwords as they like. Otherwise, if they don’t change their password right there upon auto login, they will still be e-mailed the password that the website created for them by default.
July 3, 2009 at 10:31 pm #48491In reply to: bbPress 1.0 released!
gen-superman
ParticipantI got the discussion forums for bp press working fine after updating to bbpress v1.0:
Instead of fully installing fresh the bbpress v1.0, I decided to take a different route and just updated the bbpress directory from bbpress v-1.0-rc-3 to v1.0.
That went very smoothly. I followed the update instructions that are listed on the bbpress website for the old 0.9.0.2. Those update instructions still work, but the bbpress v1.0 seems to update much more smoothly then that.
The Steps I followed for upgrading(Keep in mind I have WPMU):
– Make sure WordPress is updated to fullest version, mine is currently WPMU 2.7.1
– Make sure you already have the following plugins installed, updated and configured:
a) BuddyPress 1.0.2
b) bbPress Integration 1.0
– Now follow the directions listed on the bbpress website, which is the old upgrade/update procedures for bbpress 0.9.0.2.
(Although my current version was bbpress v-1.0-rc-3)
– Make sure that you have the following:
a) I had to create a separate bbpress keymaster account for it to work, so I have the admin account for my wordpress mu and a separate keymaster account for my bbpress. That was the only realistically way of getting this to work for me, it kept erroring on me if I didn’t.
b) While in your keymaster bbpress account make sure that you have the plugin BuddyPress Support Plugin installed (You might check for an update version.)
c) Now begin the documentation upgrade/update stuff. You don’t have to turn off the plugins as I didn’t and it worked fine.
d) You will want to follow the instructions and remove the directories through FTP in your bbpress that need removed.
Here is it word for word from the bbpress website:
To upgrade bbPress from a previous version takes just a few minutes.
These instructions cover upgrading to version 0.9.0.2
First, you should always back up your files and your database in case something goes wrong.
Second, deactivate all plugins.
Third, keep the following files and directories.
1. Rename your existing config.php file to config.old.php (and keep it)
2. my-plugins/ (if you have it)
3. my-templates/ (if you have it)
and delete everything else.
Fourth, upload the newest version of bbPress to your server.
Fifth, visit your bbPress site and run the installer which appears. On step one of the installer, enter the database details for the same database you had been using for the previous version. The installer will either create a new config file or show you the contents to paste into a file manually. Then complete the rest of the installation process.
Sixth, log in and visit your bbPress admin panels. If you see an upgrade link instead of the normal screens, click it. If you don’t see an upgrade link (it would have been really obvious), continue to the next step.
Seventh, visit the new “Settings†area of the admin and edit any details or settings in the “General†section. Also reactivate your plugins one by one (some may need to be upgraded as well).
Eighth, sit back and relax; you’re done!
e) Now, just upload your new bbpress v1.0 files to the directory. Go, to the url of your installed bbpress and insert the bbpress sql database information that you created.
f) At this point it will politely yell at you once you click next, informing you that the database is already created and that a bbpress is already installed.
g) Now, keep in mind that your bb-config.php file is brand new now. So, you will need to copy your old “KEYS” from the bb-config.old.php back to the new bb-config.php. Otherwise the discussion group forums check box won’t appear in the buddypress group creations.
* @since 1.0
*/
define( 'BB_AUTH_KEY', '###########################' );
define( 'BB_SECURE_AUTH_KEY', '##################################' );
define( 'BB_LOGGED_IN_KEY', '#####################################' );
define( 'BB_NONCE_KEY', '###########################################' );
define( 'WP_AUTH_COOKIE_VERSION', 1 ); // Because it is wordpress mu v2.7.1
/**#@-*/h) Make sure that you in your new bbpress v1.0 on your website, that you login with the keymaster account that you created, as the bbpress keymaster has the access to the bbpres plugins sections. In the settings section, check the wordpress integration settings. Make sure all the keys are correct, next you will want to click on the box at the bottom that reads :
Show advanced database settings
If your bbPress and WordPress site do not share the same database, then you will need to add advanced settings.
Make sure you input your wordpress mu 2.7.1 sql database configuration settings into those fields. Otherwise, all of this will be for nothing and it would integrate and the users wont show up correctly. BTW, user database host is typically ‘localhost’.
Now click Save changes at the bottom of that page.
i) Back at the wordpress mu portion of your site, you will want to login back in with your admin account. Then go to your buddypress settings and click on forums Setup. You will want your bbpress username and passwords field to match your wordpress admin account only in this section. I couldn’t get the keymaster account to work with this part.
j) Now go to the groups section of the buddy press, you should see the “Group Forums discussion enable” box now there.
k) Lastly, don’t forget to check your wp-config.php settings, to make sure that the keys are properly set up there too.
For example:
* @since 2.6.0
*/
define('AUTH_KEY', '###################################');
define('SECURE_AUTH_KEY', '######################################');
define('LOGGED_IN_KEY', '#######################################');
define('NONCE_KEY', '##########################################');
define('AUTH_SALT', '##########################################');
define('LOGGED_IN_SALT', '############################################');
define('SECURE_AUTH_SALT', '#######################################');
define( 'COOKIE_DOMAIN', '.yourwebsiteurl.com' );
define( 'SITECOOKIEPATH', '/' );
define( 'COOKIEPATH', '/' );
define( 'COOKIEHASH', '##############################' );
/**#@-*/Hope that helps.
July 3, 2009 at 12:13 pm #48466John James Jacoby
KeymasterEveryone is always very quick to advertise the benefits of a single-sign on service, or a go-between to allow users to sign into your website using any number of different credentials, but there are a few major flaws with this idea, and they are going to become extremely apparent very soon.
The first MAJOR flaw I see in this design, is that all it takes is one website to put up password stealing/sniffing code, and now you’ve given your twitter password to anyone with access to the sites malicious intentions.
The second MAJOR flaw I see from a developers standpoint is that you as a site administrator no longer have control over the user data that is using your website. This means tracking down a problem user that creates an account with their facebook, you ban them, their google, you ban them, their open_id, you ban them, etc… That, along with the fact that these user registrations tend to add their own cryptic names into your database fields; now you’re forced to try to know who “fb8288373” really is, when had they registered the normal way, you could see they are “johnjamesjacoby.”
From a user perspective, I don’t plan on using Facebook for the rest of my life, so when I delete my account in a few years, that means I can no longer use your site without creating a new profile.
Also, if I’m logged into facebook on my computer, and close facebook, and then my girlfriend walks over to a site and clicks on facebook connect and continue, it logs her in as me because I am still logged into facebook. Now I’ve registered at a website that I didn’t want to register at, and I have no way to delete that account, and who knows what kind of information they’ve decided to store about me by this point…
Quite frankly, I can’t wait for this trend to die. It’s a headache waiting to turn into a brain tumor in my opinion.
July 3, 2009 at 1:52 am #48449In reply to: Understanding User Blog Creation using subdomains
carinallc
ParticipantNope
Here’s where things stand:– created (3) blogs. They hae IDs 1, 4 and 5. ID1 is the default blog and works perfectly, with Admin listed as the User.
ID4 was created with a User account. However, when I click on “Visit” from Site Admin…Blogs, I get the following:
Fobidden
You don’t have permission to access / on this server.
Additionally, a 403 Forbidder error was encountered while trying to use an ErrorDocument to handle this request.
Never saw that before
July 2, 2009 at 5:16 pm #48422In reply to: fyi: WP-reCAPTCHA works fine with BuddyPress
flynn
ParticipantHey all, sorry to bump and old thread, but it’s related, I promise

I’ve installed reCAPTCHA in the plugins folder, and it works brilliantly for comments. (For that matter so does wmpu-captcha in the mu-plugins folder) But neither seem to work on the registration page.
Working – http://thompsonjason.org/2009/04/11/hello-world/#comments
Not Working – http://thompsonjason.org/register
Is there a bit of code that I should be inserting into my registration page to make reCAPTCHA show up. I’ve been getting a lot of spam accounts being created lately, so I really need to get this going before we can launch the site. Any help is greatly appreciated.
July 1, 2009 at 6:36 pm #48370In reply to: BP admin bar on bbpress front page
r-a-y
KeymasterSorry for not being clear!
What I mean by “deep integration” is calling WordPress into bbPress. You can do this by doing what Necati above you said. Then you can just follow the steps I have listed above.
Thanks for posting that for everyone! My instructions weren’t the clearest!
—
[EDIT]
I decided to post the full code again for clarity’s sake.
On line 2 in bb-config.php (located in your bbPress forum install), add this:
require_once($_SERVER['DOCUMENT_ROOT'].'/wp-blog-header.php');Now, add this to your bbPress theme’s functions.php (if you do not have a functions.php file in your bbPress theme folder, create one!)
function recreate_bb_admin_bar() {
echo '<div id="wp-admin-bar">';
bp_adminbar_logo();
echo '<ul class="main-nav">';
bp_adminbar_login_menu();
bp_adminbar_account_menu();
bp_adminbar_blogs_menu();
bp_adminbar_notifications_menu();
bp_adminbar_authors_menu();
bp_adminbar_random_menu();
echo '</ul></div>';
}
add_action('bb_foot', 'recreate_bb_admin_bar');
add_action('bb_admin_footer', 'recreate_bb_admin_bar');
add_action( 'bb_head', 'bp_core_admin_bar_css', 1 );
add_action( 'bb_admin_head', 'bp_core_admin_bar_css', 1 );I also made one last change to the function because it wasn’t XHTML validating before! See if you can spot the change
June 25, 2009 at 3:08 pm #48061In reply to: BP admin bar on bbpress front page
seppolaatle112
ParticipantI am using Buddypress 1.01 width Wpmu 2.7.1 and managed to get the adminbar working great without even touching Buddypress core.
All i actually did was to make sure I had :
require_once('../wp-blog-header.php');in my bb-config.php-file, and after that i just simply added r-a-y’s code to my bb-theme functions.php file. :
function recreate_bb_admin_bar() {echo '<div id="wp-admin-bar"><ul class="main-nav">';
bp_adminbar_logo();
bp_adminbar_login_menu();
bp_adminbar_account_menu();
bp_adminbar_blogs_menu();
bp_adminbar_notifications_menu();
bp_adminbar_authors_menu();
bp_adminbar_random_menu();
echo '</div>';
}
add_action( 'wp_footer', 'recreate_bb_admin_bar', 8 );
add_action( 'admin_footer', 'recreate_bb_admin_bar' );
add_action( 'wp_head', 'bp_core_admin_bar_css', 1 );
Works just perfect. I can’t really see any need for a plugin to do this, but I guess there’s always someone who don’t manage without them.
June 19, 2009 at 11:12 pm #47818In reply to: Disable new blogs creation for new accounts?
Tracedef
Participant@Burt: Thanks, I tried that setting already but when users try to register at my register page they get, “You must first login, and then you can create a new blog. ” …. So they aren’t allowed to register a new account…. any ideas?
June 19, 2009 at 11:24 am #47755In reply to: Disable new blogs creation for new accounts?
plrk
ParticipantI want my users to be able to create blogs att signup, but I want “Just a username, please” to be checked by default rather than “Gimme a blog!”. Unfortunately, I have no found any filter for this. Any ideas other than a minor edit to the relevant core file?
June 19, 2009 at 8:03 am #47748In reply to: Disable new blogs creation for new accounts?
Burt Adsit
Participantwpmu back end > Site Admin > Options
Allow new registrations
Only logged in users can create new blogs.
-
AuthorSearch Results