BuddyPress.org

Looks like this post hasn’t been active for a month or so, but I’ll put this here anyway… I wanted to do the same thing you do, but without loosing the completely widgetized front page, so I wrote a new widget of my own by pretty much just copying the BP Recent Posts widget and modifying one line so that it displays the whole post, instead of just the excerpt.

The line in questions was

<div class="item-content"><?php echo bp_create_excerpt($post->post_content) ?></div>

which I changed to

<div class="item-content"><?php echo $post->post_content ?></div>

If you’d like to use the plugin I made to load that widget, so I didn’t have to modify the core files, you can get it here: http://benspants.com/stuff/full_posts.txt. Just download that and make it .php instead of .txt, and you should be good to go!

You know I was thinking about this another way Paul. New users need some handholding and encouragement. Perhaps you can detect that a group of users hasn’t met any of those criteria and do something to help things along.

Stick them in a group that others can pay attention to. Everyone knows that forum questions coming from that group should be cut some slack and patiently answered. New users may not feel comfortable asking questions in the main forums/groups. Questions that anyone has in a new environment. We still feel dumb asking them. I don’t feel quite as stupid if everyone in a particular group is as dumb as I am.

New users are eager to share their experience, even if limited, with others. It’s a group of people who fit together.

A ‘Welcome’ group they can graduate from by participating there. It’s 4am here. This might actually sound stupid after a couple of hours sleep. Ah, well. Too late to care.

Okay, first a couple of questions:

I have a fairly vanilla instance of the latest wpmu release…

1. What does this mean? The latest release of WPMU is 2.7. Is that what you’re running?
2. Also, which BuddyPress trunk revision are you running?
3. Are you running any other plugins besides BuddyPress?
4. Did you follow all the instructions in the first post of this thread that pertain to custom themes?
5. Did you read post eight in this thread?

Regarding the code line that seems to be throwing the problem, that would indicate that you do not have the proper permissions set on the blogs.dir directory. See question 5 above.

@Erich73

“currently we do not have the resources to create this integration in-house.

I will however, fully support the developers that will take this initiative, providing help in code and guidance.”

they dont have time

I sent Andy a message and asked him a couple questions…. considering the BP Gurus are currently pondering the same things we are, I really suggest finding out “how they would do it”

then it can be seamless and remain stable as BP changes….

again, I’ll cover half to all if this is done with “BP’s blessing”

Burt-

Well, that was one of my thoughts–and why I’m asking Grandslambert to clarify what he meant by

Using WPMU 2.7 and the latest TRUNK of bbPress

I assume he meant BuddyPress. If so, is he running WPMU 2.7 but with BP 1.0_RC2? Did he install the BP folder in the proper spot? You’ve seen my questions above.

But, I’m tired and JJJ had an intriguing idea as well. So, perhaps I should get some sleep tonight and all the problems of the universe will disappear overnight!

Some initial questions:

1. Which versions of WPMU and BuddyPress are you running?
2. Have you enabled all of BuddyPress’ components?
3. Where did you install the suite of BuddyPress components?
4. Are you using custom themes of the standard themes that came with BuddyPress?

WPMU 2.7 and the latest TRUNK of bbPress

I assume you mean BuddyPress, and not bbPress. If so, then here are a few questions:

1. What do you mean by “latest TRUNK”? Did you actually download the BP trunk from trac as a zip or use SVN? Or, did you obtain BuddyPress from the big, orange Download button that can be found on the top of any BP page?
2. What version of BuddyPress are you using?
3. Where exactly did you place the BuddyPress folder?
4. You are using WPMU 2.7 and not WPMU 2.7.1-beta1 or -beta2, correct?

Danielfelice-

Okay, a few more questions:

1. Are there any errors being reported in the error logs? If so, what are they?
2. Are you using the default BuddyPress themes with no changes at all?
3. Did you use the new WPMU config file, or a config file from an older version?
4. Is buddyPress-home theme installed in /wp-content/themes/ ?
5. Is buddyPress-member theme installed in /wp-content/bp-themes/ instead of /wp-content/member-themes/ ?
6. Did WPMU work fine before BuddyPress was installed and activated?
7. Do you have any WPMU plugins other than BuddyPress installed? If so, have you tried deactivating them to see if that makes a difference?

More questions?

1. By latest WPMU, do you mean latest public release?
2. Have you customized the theme in any way?
3. Have you tried disabling all but the BuddyPress plugins?
4. Where exactly do you have the BuddyPress plugins installed?
5. Have you tried re-uploading from scratch?

Oh. bin.buddypress.org of course.

EDIT: I said that with just a knee jerk reaction. Kind of a ‘not invented here’ thing. Now that I’ve had time to think why, I realize it’s because we do need to control it. In case nobody has noticed, we’re have the opportunity to *not* follow the rules for technical support and software development. The nature of buddypress, it’s social nature, gives us the opportunity to invent something truly different and useful.

Don’t ask me yet what that is yet but signs of it are beginning to appear.

Complaints about the bp.org group forums not being live yet. They aren’t just complaints. They seem to be us, struggling to accomplish something in a certain manner and knowing that the tools are dangling before us.

We’re discussing code collaboration, commenting, sharing solutions to user problems and questions. Solving things in front of people. How best to accomplish that with code paste bins.

Suggestions and approval of a ‘technical blog’ that will show people, by example, how to do things.

It’s like we’re all suffering some vague malaise and we sense where to find the remedy.

Sorry, Burtadsit, but can you break this down a bit more for the truly moronic like me? I’m having the same problem and I have installed vipers-video-quicktags which is nicely displaying all the various video icons in my visual editor. It is working correctly, but when the post is saved the code disappears as above. Now you say it’s a security hole. I don’t want to open up something bad, but I do want to easily add video to my posts. I don’t want to do anything with the forums.

Is this the entire code I put in a bp-custom.php file?:

function my_allowed_tags($allowedtags){

$allowedtags[’embed’] = array();

return $allowedtags;

}

add_filter( ‘edit_allowedtags’, ‘my_allowed_tags’ );

I’m confused as why you mentioned bp-forums.

And again, I really don’t want to open up something bad. What are the implications of adding this?

Thanks in advance. I know I ask pretty dumb questions.

In wp-login.php, I have found the following line of code (around line 470) ….

I want to redirect the user to their profile page, so I changed it to …

I would highly recommend that you stay away from hacking core WPMU files. You’ll have to make the changes all over again the next time you update WPMU.

This is the way you should do it: https://buddypress.org/forums/topic.php?id=1095

How can I change the wp-login page to include my site\’s logo instead of the WordPress logo? Is this possible?

http://premium.wpmudev.org/project/rebranding-wordpress-mu

By the way, you may receive faster responses in the future if you ask WPMU questions on the WPMU forums and ask BuddyPress-specific questions on this forum.

Vito687-

I can not change or create avatars

I assume you mean that you cannot create avatars at all. If that is the case, then you cannot even get the chance to change your avatar. Is this correct?

The error you mentioned in your OP is found in only two places in BP:

• bp_core_avatar.php –> in the function bp_core_avatar_admin
• bp_xprofile_signup.php –> in the function xprofile_validate_signup_fields

So, either you do not have sufficient permissions in the folder where the avatar is first uploaded, or you’re uploading an avatar that is too big. I will guess that it is the first problem based on the error message.

But, let’s be thorough.

You mentioned that you’re running a very recent BP trunk version and WPMU 2.7.1_beta from branch. We’ll assume that everything is correct with your upgrade and that you’ve also read the thread Lance mentioned and tried any applicable suggestions.

Here, then, are some additional or follow-up questions:

1. What is the size of the avatar you’re trying to upload?
2. What is the avatar’s format?
3. Are you using the standard buddypress-member theme or a customized theme?
4. What version of GD is installed?
5. What version of PHP are you using?
6. Have you checked all the folders in blog.dir and made sure that there are indeed no files?
7. Have you checked the permissions of each of the subfolders in blog.dir?

Peter-

I realize that you are not getting the answers you desire. You must have a sufficient understanding of and comfort level with PHP before you can delve too deeply into hacking your own solutions or coding your own theme templates. Otherwise, you need to use the stock WPMU and BuddyPress install and then customize with any plugins and 3rd-party themes that may be useful.

Since we do not have any idea of your particular coding skills, we are trying to point you in the right direction. Please realize that beyond a certain point, we cannot help you write your own custom code.

We all started at the beginning when it came to coding and then had another learning curve when it came to understanding the inner workings of WordPress and BuddyPress. It can be frustrating along the way but it is indeed possible to accomplish!

Here are a few more tips:

1. Since you do seem to be wanting to group all user data within stock WP tables, you should search the WP and WPMU forums and ask your questions there
2. Visit these WP Codex pages to help shed more light:

• https://codex.wordpress.org/Function_Reference/wpdb_Class
• https://codex.wordpress.org/Function_Reference

3. Google for tips on learning data-driven PHP coding
4. Hire a 3rd-party developer who can do the work: hacking files directly or create a plugin that will accomplish what you’re after

Please hang in there and don’t give up hope.

I would say it would be in your best interests to get used to how the new versions of wpmu and buddypress work together, if what you want is to stay on top of the most recent bug fixes, etc…

Upgrading from RC1 is going to open a whole new set of questions though, as it’s not a super easy thing to do.

Some questions….

1) Remove all your bp widgets. (Done that)

2) Open translation.po

(Where is that file located?)

3) Find bp-core/bp-core-widgets.php (it is mentioned many times and write down the line numbers)

(Didn’t find it….) ??

4) Open mu-plugins/bp-core/bp-core-widgets.php

5) Translate manually the lines where the translation file was supposed to do it.

(Can anyone tell me the line numbers?)

6) re-upload mu-plugins/bp-core/bp-core-widgets.php

7) activate widgets that now will be named on your translation language e.g. “welcome” will be “Bienvenido”

send me a beer!

(Ill send you 20 beers if you help me)

Thanks yall!!

Okay, a couple of questions:

1. Which version of BuddyPress are you using?

2. What did you name the file?

3. Where did you place it?

Well, it seems like you have an issue, alright. Let’s go down the list once again:

1. You’re working with a current trunk of both WPMU 2.7.1_beta1 (current: r1725) and BuddyPress 1.0_RC2 (current: r1324)
2. You’re using an old copy of wp-config.php which you updated as appropriate. In other words, you did not use the wp-config-sample.php that came with WPMU 2.7.1.
3. You did a clean install of WPMU 2.7.1_beta1 by deleting everything, except your updated version of wp-config.php, and then uploaded the unzipped Mu files
4. You then launched WPMU’s admin screen. That worked with out any problems.
5. You then went to Site Admin > Upgrade and finished the upgrade
6. You logged out of WPMU
7. Next, you installed BuddyPress by:

• moving the contents of the unzipped BuddyPress 1.0_RC2 (r1324) to the WPMU plugins directory into a subdirectory called /buddypress/
• moving the /bp-themes/ directory out of the /buddypress/ directory
• placing the various themes in their proper locations

8. You then logged back into WPMU and got a blank screen

A few follow up questions:

9. You’ve enabled error reporting as detailed above by John and Burt and after step 8 above, there are absolutely no errors being reported of any kind.

A few thoughts:

• Since this seems to be a test install and you do not have any content that needs saving, I would delete everything once again.
• This also means deleting your MySQL table that you’ve been using for this attempt and starting with a brand new database.
• I would then download the latest trunks of both WPMU and BuddyPress once again–>get rid of the old ones first.
• I would then use the wp-config-sample.php file that comes with the latest WPMU trunk and configure as necessary
• IMPORTANT: I believe when I downloaded the WPMU trunk (r1722) and looked at the wp-config-sample.php file, it had a trailing space after the closing php tag. You need to delete this!
• Now, go through steps 1 through 7 again and let’s hope when you get to step 8 it works!

Great — glad to hear it. Sorry to have missed your previous questions.

where do i upload the .po file to??

Anywhere on the server, it doesn’t matter.

what does this command do exactely

It takes your PO file and creates the MO for you.

did you mean.. ”and added the buddypress-spots.mo file there…”

Yes.

i have already set up in wp-config.php will this clash with what you have said to doo..

Hmmm… that I don’t know. I don’t use those configuration settings, myself. I would suggest commenting them out and testing your site. If the language file changes are still working, go ahead and delete those lines from your wp-config file.

Overall the language file is a better long-term solution since you can make changes for other labels there as well if they come up in future versions, whereas those custom definitions are only specific to a few labels.