[@aaronthomas1979 Participant 9 years, 9 months ago]

Thanks very much!

[@aaronthomas1979 Participant 9 years, 10 months ago]

Thanks very much!

Is there an easy way to dissuade WordPress functions from Buddypress functions?

Would we have not had this conversation if I had read up on the WordPress docs more?

[@aaronthomas1979 Participant 9 years, 10 months ago]

Yes, my BP brothers, there’s a plugin called BP Simple Private and I think it will solve your problems, without having to work with robots.txt

Prior to using BP Simple Private, my site’s member pages were way too accessible.. You could type http://mysite.com/members <- and you’d see the whole members directory.

Prior to using BP Simple Private, you could type http://mysite.com/members/aaronthomas1979, and you’d jump straight to my profile.

With this plugin, people (or search engine bots,) will be redirected to a page of your choosing, and the member pages will not be displayed.

If you already have the issue of member pages being displayed in search results, there’s nothing you can do to immediately fix that, but make the change (get the plugin) and wait for those bots to crawl your site again, but next time, they won’t find those pages.

It works for me..

[@aaronthomas1979 Participant 9 years, 10 months ago]

I hid the input box and it disables it.

Put this in your child-theme’s style.css:

/* Removes option to CC PMs to more than 1 recipient */
input#send-to-input.send-to-input.ac_input {
display: none;
}

Clear cache & presto!

[@aaronthomas1979 Participant 9 years, 10 months ago]

That is what I assumed, but I just wasn’t sure. Thanks for clarifying this!

I will hide it – BTW: Just to be sure we are all aware, the feature does not check the name entered to see if it’s in the database. Someone could easily spell a name wrong, think that the message was sent, and then log out.

(Resolved)

[@aaronthomas1979 Participant 10 years ago]

This issue is resolved.

The problem was with Buddydev’s Conditional Profile Fields plugin. For me, to fix the problem, I figured out that I had to set all conditional fields to unconditional, then make any necessary changes to the profile fields, then when satisfied, go back and set the conditional statements, then the problem of not being able to save was gone.

[@aaronthomas1979 Participant 10 years ago]

Update: Surprisingly, I figured it out. If anyone else needs this info, here’s how I matched the size of the email box to the size of the username & password boxes:

I added this to my child theme’s CSS:

input[type="email"],
textarea {
	width: 35%;
}

[@aaronthomas1979 Participant 10 years ago]

Thank you! Works great on Graphene too!

[@aaronthomas1979 Participant 10 years ago]

So just to be clear, my registration form does not ask for real name. It asks for username, email address, password, and then it proceeds to the extended profile questions. But it does NOT ask for “Display Name,” it just copies whatever the user typed for username into the “Display Name” field. A friend of mine created the function, and I am not extremely PHP literate, but this is working on my site.

I’m a little embarrassed, because I don’t know exactly where in the code is this function that my buddy created for me, so I will have to give you the URL to my register.php file, and then you can view it in it’s entirety. (Code view with your browser.)

Click here to see my register.php

[@aaronthomas1979 Participant 10 years ago]

Thank you!

[@aaronthomas1979 Participant 10 years ago]

I have a function set up in my register.php that copies the user-supplied username (in the registration form,) copies it over to the “Display Name” field, and hides the display name field on the registration form. This way, whatever the user entered for username will automatically be used for his/her display name. (To avoid asking the user for a name 2 times!)

Would you like to do this? If so, I’d be glad to share my register.php file with you. Let me know. If this is not what you need, then please disregard this message.

[@aaronthomas1979 Participant 10 years ago]

I understand. This topic belongs in one of the plugin forums. I will figure out which plugin it is and ask in the appropriate forum. Thanks anyway!

[@aaronthomas1979 Participant 10 years ago]

I’m using a plugin called Buddypress Xprofile Custom Fields Type.

If I edit a profile field, Buddypress begins to malfunction by not letting a new user save his info entered into the register.php form.

So if I delete all my profile fields, and then re-create them, Buddypress will begin to function properly again, but, then I create custom profile search widgets with a plugin called “Buddypress Profile Search,” and then the problem starts again. (User can’t save the data he entered. Registration page just refreshes.)

[@aaronthomas1979 Participant 10 years ago]

I’ve painfully isolated the issue to Xprofile Custom Fields. After I make changes to the profile fields, the new user registration stops working. (Stops saving new user data – refreshes new user data screen instead of saving.)

[@aaronthomas1979 Participant 10 years ago]

I have a function that copies the user-defined username over to the Display Name. I would just remove the function and test it, but I will need to have a friend of mine remove the function for me, if this is the case.

[@aaronthomas1979 Participant 10 years ago]

Thanks, and I went through the process, and then I re-installed Buddypress, but I’m still having the same problem. It’s when I click the button to save the new user info, and instead of proceeding to the next step (“Check your email for verification,” it’s just refreshing the new user registration form. It won’t let a new user get passed that screen.

I read about someone else having the same problem, in this forum, but he never did describe how he overcame the problem. I’ve tried deactivating all buddypress related plugins, but no luck.

I think the best thing for me to do is going to be to re-install WordPress from scratch, but do you have any other recommendations before I do that?

Thanks.

[@aaronthomas1979 Participant 10 years, 1 month ago]

Yes, I’ve tried that, but with no luck. Do you know if there’s a way to delete buddypress & all settings so that when I re-install it will be like a fresh install? I’m asking because typically when I re-install a plugin, it always remembers the previous settings.

[@aaronthomas1979 Participant 10 years, 1 month ago]

Thanks again, this is working great! Problem solved.

[@aaronthomas1979 Participant 10 years, 1 month ago]

Thanks very much guys!

One last question: If I go for the css trick, which css file is associated with register.php?

I have a child theme, and I tried adding the code to the .css file in the root of the child theme folder, but that didn’t work.

[@aaronthomas1979 Participant 10 years, 1 month ago]

I appreciate your effort, but things like username, email address, and password, are simply not in the profile fields editor; there is no re-arranging them. I wish it was that easy though! That would be nice! This is definitely going to take some php and/or css editing.

[@aaronthomas1979 Participant 10 years, 1 month ago]

Thank you very much! Everything is completely resolved here.

[@aaronthomas1979 Participant 10 years, 1 month ago]

I did what you said and it’s working now. Thank you very much!

It’s confusing as to why the new sub-folders differ so much from the originals. (In the child theme, we don’t have bp-templates, for example.)

Is the child theme only good for Buddypress editing?

Or can I use it to edit another plugin as well?

If I can use it to edit other plugins, could you give me an example of how I will create that path?

[@aaronthomas1979 Participant 10 years, 1 month ago]

Thanks! Now, to be certain, let me ask you this:

This is the original path to the original register.php:
public_html/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/register.php

This is the new path that I created by adding new folders:

public_html/wp-content/themes/graphene-child-theme/buddypress/bp-templates/bp-legacy/buddypress/members/register.php

Please notice that I did NOT create a folder called “plugins,” during this process. Is this correct?

If not, let me know where I goofed. But if I am correct, and there will be no folder called “plugins,” with regard to the child theme, then let me ask this last question:

I will MAKE CHANGES TO the child theme’s register.php, and I will stop caring about what happens with the ORIGINAL register.php. Is this correct?

Thanks for your patience with me. I appreciate very much!

[@aaronthomas1979 Participant 10 years, 1 month ago]

Thanks very much for your help! Problem solved.

All that genericness going on is due to the fact that I re-installed everything because I thought this error was due to some faulty plugin. So when I re-installed, I was dumbfounded when I was still having the re-direct issue. Now I can bring the site back to life. Thanks again!