BuddyPress.org

that code above is messed, buddypress forum keeps messing with my code?? not sure why? if you open the style.css in your theme directory you will see the code to import css files, but id suggest just add to the new code to your _inc/css/deafult.css file

First off id suggest making a child theme, more info here https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/

You can put the html code in the header.php found in your theme folder, im not sure where you want it placed exactly so you will have to trail and error untill you find the right position.

The corresponding css code should be put in the _inc/css/deafult.css file, OR you could make a new separate css file and include this in your main css file like so

` @import url( _inc/css/your_new_file.css );`

http://www.woothemes.com/2010/03/cityguide/ plus BP plus BP Template Pack plus One Quick Post or something similar.

Some recommend copying the default CSS over to your stylesheet.

Benefits of this approach is one less data request and full control over your styles (good when you’re designing a completely different look from bp-default).

Negative is if your child theme completely relies on the bp-default theme with little design changes, you might as well use the @import- declaration so you can easily override selected style declarations on a case-by-case basis. Some theme designers frown upon using !important, but at the end of the day, it’s your call.

@janis

Re #1 – BP 1.2.7 will fix this.

If you can’t wait until then, try the solution posted in this thread:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/am-i-going-mad-or-are-there-now-avatars-next-to-posts-in-the-activity-stream/?topic_page=2&num=15#post-76621

Re #2 – Most likely a child theme issue. Can you post a screenshot to confirm?

@zomex – You might want to try this in your theme’s functions.php:

`remove_action( ‘init’, ‘bp_core_add_admin_bar_css’ );

if ( !is_admin() )
add_action( ‘init’, ‘bp_core_add_admin_bar_css’ );`

Untested, but give it a shot.

—

Actually, based on your report, it’s hard to give a definitive answer. What exactly is breaking in the admin area?

@janis It seems to be the avatar of the blog so if you have multiple blogs you can have different avatars for each blog. I’ve been going nuts trying to figure out how to upload a new avatar for each blog so it doesn’t look generic but I haven’t figured it out yet. If the monitors of this thread know please let me know. Also, In regards to the latest post you just need to adjust the CSS on the style sheet of the theme you are using.

There are a few possible approaches to integrating them together, and the ones you need are possible even today. That’s actually exactly how bbPress works in the WordPress plugin repository, attaching plugins to tags in essence giving them their own ‘forum’ in a sense.

The first iteration will probably closely mirror how things work today, for the sake of it being an easy transition for everyone’s existing data. The last thing we want to happen is to force anyone to make changes to their existing setups. In future iterations we’ll include some options on how you want to configure them to communicate to each other. This may be strongly theme dependent though, since all of these components would need to have the proper hooks and CSS in place to style these elements correctly in any of the places they might appear.

mercime’s suggestion will work well if you want to keep people from commenting on certain kinds of activity items. If you want to turn off updates entirely, you may want to do it at the theme level. You’ll need a child theme (https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/). In that child theme, make sure you have a file groups/single/activity.php. You can get the content of that file from wp-content/plugins/buddypress/bp-themes/bp-default/groups/single/activity.php. Then, in the version of activity.php in your child theme, remove the following lines:
`

`

similar problem over here, autocomplete function finds valid users and shows them up, but in the following lines an error is displayed 3 times:

“Warning: Cannot modify header information – headers already sent by (output started at mountpointwp-contentpluginsbuddypressbp-themesbp-default_incajax.php:556 in mountpointwp-contentpluginsbuddypressbp-messages.php on line 556”

any idea?

by the way, is there a plugin which enables a better useabbility for choosing multiple user’s to send a private message to? Something like a list with checkboxes for example?

Create a child theme of bp-default theme, upload and activate. Then go to dashboard Appearance > Widgets and drag the “Recently Active Member Avatars” widget to Sidebar and save it.

You came here seeking help from those more experienced!

BTW, I’m a total newby at both WP and BuddyPress and came to the forum to find help, not to get dumped on

Where have you been dumped on?

It doesn’t help to get snippy about “generally not the done thing to do on forum

There is a very deliberate reason old threads are not raised again, and yes sorry but forums rules in general frown upon this action and do ask that people start their own threads. You claim this thread mirrors your own issue, but I’ll point out that your stated inexperience in matter leaves you not best placed to judge that.

I don’t think starting lots of new threads about the same problem will help anyone

Again let us worry about that.

Please set aside the attitude it doesn’t help. Once again you have come here for help, that help often comes from experienced professionals that earn their living coding and developing, please respect the fact that there is no obligation to help and that this help forum and the project itself is maintained by volunteers – unpaid!

You really needed to have followed my advice earlier about testing with bp-default and plugins disabled if you had lurked on the forum you would have noted that this is a very common and important request.

Now as to your concern as to losing work you wont! it is perfectly safe to change themes that is the nature of the WP themeing side of things, disable your custom theme and activate bp-default also deactivate any BP related plugins except BP itself nat and also any custom functions that you may have created in your themes functions file.

Test the registration process in this default state if it works then you now know you have an issue with either your custom theme or a plugin; if it still doesn’t work then you might consider checking that you have in fact told WP to allow registrations in the WP options screen, if that is set confirm whether WP itself can accept registrations – helps to make sure WP is set up correctly and working before moving on to adding further layers like BP.

When that is done please report back and let us know what the outcomes were and we can then proceed from there.

You can disable plugins and themes temporarily without losing work. WP and BP content is stored in the database and shouldn’t be affected by what themes and plugins you do or do not have activated.

It’s important that you test whether the problem arises with bp-default, the BuddyPress Default theme that comes with BP. If registration works with that theme but not with your custom theme, then we’ll know that your problem is theme-related. Most likely, your theme is missing the template files that BP expects to find when someone visits the registration page, and for some reason the fallback template (which should be wp-signup.php) is not being found either.

Please test with the default theme and report back.

Sufussion and Atahualpa , the 2 themes use quite different coding structure. You do need to consult the theme developer to get a smooth intergration.

We have WP 3.0.1 and are using the Citizen Kane 1.0.2 theme. I can’t see any way to tell what version of BuddyPress we have, but it was installed just a few days ago, so it should be whatever the latest number is.

BTW, I’m a total newby at both WP and BuddyPress and came to the forum to find help, not to get dumped on. This topic is dead on point. Although this thread was STARTED 5 months ago, nobody seems to have offered any help and people were still posting the same problem just a week and a half ago.

It doesn’t help to get snippy about “generally not the done thing to do on forum” when there hasn’t been any useful response to this one in the past and, frankly, I don’t think starting lots of new threads about the same problem will help anyone. Isn’t that why forums are organized into threads in the first place?

Can we get back to solving the issue?

Before we start dismantling all our work, what will happen to all the stuff we’ve created (design work, etc.) if we disable all the plugins and change themes?

You will probably need to add a little more detail, version numbers, theme in use plugins etc. 1.2.6 has no issues that I’m aware of with signup and works correctly so there must be something else upsetting things.

It would help to confirm whether disabling all plugins other than required BP and dropping back to the bp-default theme still presents the issue or whether it works with default bp

This thread is 5 months old and apart from possible usefulness as archive reading (not in this instance) it serves little purpose resurrecting old threads to post to, and is generally not the done thing to do on forum please always create a fresh thread on an issue.

On a volunteer support forum it’s not really appropriate to ask members to do work for free, members are generally willing to help people to work through things but it will always be expected that they will attempt with help to get this done. Of course if you really haven’t the skills then you can take the option to pay someone to do this for you then we would ask that you post a request for paid help in the Jobs Board group:

https://buddypress.org/community/groups/bp-jobs-board/

I presume you have used the template pack plugin to try and get your theme compatible with BP, have you run through the codex page to see if that helps at all:
https://codex.buddypress.org/theme-development/bp-template-pack-walkthrough-level-easy-2/

This thread where I stripped out the markup from a BP index file and theme page.php file to show the common markup that requires to match may help you a little?
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/lightword-theme-help/#post-80930

I’m afraid that is asking slightly too much as that approaches ‘Work’ and as such I earn my living – supposedly – from coding and development- it also takes the BP project site / support forum into the realms of a ‘Service’ which for any any ‘Help’ forum is a dangerous confusion.

When you attempt this kind of customisation you have to accept that a certain level of knowledge is required , it is only a basic level but you do need to learn it.

So no I am not prepared to do that work for you – and provide a ready edited theme for you to use as that would be chargeable work however on a help forum I am prepared to guide you through what you need to do and help you along, so get your site up and live somewhere and make a start, provide a link to it so that I or others can look at where you have got to and advise on the further steps required.

I f you re-read my last post it should make sense – i referred to checking for example elements such as <div id=”content”> exist in both files as these main elements must match. You can clearly see in the two examples you posted that straight after the header function call there are two elements in the index file but only one in the page.php file and it’s id is different – lightword will be managing the layout i.e applying it’s styles vie elements such as this ‘div id=”content-body’ if that id is not found as it’s not in /activity/index.php then any important CSS rulesets will not be applied.

I will strip the files down to the common elements for you removing those parts of the code which are unique and necessary for both files e.g the output loops essentially.

page.php
`

`
Avtivity/index.php
`

`
What you have now represents the common elements of both files and which need to match -obviously what has been removed is for clarities sake and is required if both files are to output their data.

There may be other elements introduced in other files that you will have to deal with and adjustments needed to styles and stylesheets but that will become apparent as you work through things.