BuddyPress.org

Regarding the theme: if you want to make your own version, do as hnla suggests. Otherwise, how about mocking up some designs for post formats support and see how things go?

Yep. ‘svn diff > patchfile’ I what I usually do.
Trunk is where the dev is happening, so if you’ve spotted things you want to fix, check out a trunk install and check that we haven’t fixed it already.

If you’re looking for things to fix, typically any ticket on trac is valid and warrants a patch, but see if you think you can attack any of the issues in this report. These are the main tickets we still would like to fix for the next release: https://trac.buddypress.org/report/11

Thanks

The private messaging doesn’t use the email addresses directly. I spent a bunch of hours this last weekend fixing problems with the private messaging system in certain situations involving differences between the user’s log in, and user nickname fields, and when the compat mode constant is set (I assume you have set this in your wp-config.php if you are logging in with email addresses — can you confirm?

Is this then an issue with Messages only? In other words, those who register on your site using email addresses that end with country code extensions receive activation emails?.

@el_terko

ok, latest news from fighting field:
last code in itself adds working “view” button to every activity, reply buttons still are there.
function my_bp_activity_type_is_new_forum_post() still returns same error.

Edit: no need to proceed with this question, I will use code by josemv. thanks again

Do it then but not the default theme, create a child theme which is essentially re-modeling the default. Themes are in short supply so if you have the ability then I’m sure many will be grateful for an addition to the theme library for BP.

i’d like to contribute by remodeling the default theme

Anyone is able to create a trac ticket for bug notifications or enhancements once created it will await review by one of the three core commiters (those three + 1 are the only ones with commit access on the project), if approved or passed as valid others that actively run trunk/bleeding edge test sites might look at and if necessary feedback and/or test patches as required.

If you have enhancements / code changes then submit them as patch files that can be tested out on installs.

You can use svn, but you want have commit access (http://svn.buddypress.org). As for reporting bugs, and viewing what needs to be fixed, you can do that on Trac (http://trac.buddypress.org). You’ll use the same login credentials to post on Trac that you use to post here.

@kunalb Thanks for this great plugin. I want to override the orange color for .ep-event-details specified in events.dev.css. First I put the class in my child theme style.css. This didn’t work until I disabled events.dev.css by renaming it to xevents.dev.css. I’m now trying what you are saying above, and I want to make sure that I understand you correctly. I put /assets/css/events.dev.css in my child theme folder and it does not override the events press style. I also tried putting my own version of events.dev.css in my child theme root and that also doesn’t work. Then I tried putting /mytheme/assets/css/events.dev.css in the buddypress theme folder – no luck there either. I’m going to resort to the rename hack for now, but I’d like to find a more permanent solution. Any suggestions are much appreciated.

@gunju2221 I’m well aware that bbPress views weren’t in that file. I wasn’t answering that question. I was responding the the question of where bb_*_topicmeta() functions were located.

@lockamiz23 That code is a start, but it’s going to need to be cleaned up, and customized to integrate with BP. If I get some time, I’ll see if I can get it working Don’t count on anything soon though.

I believe this is your issue (https://trac.buddypress.org/ticket/1796). If so, please add any new information you might have. You can use the same login credentials that you use here.

bbpress views aren’t in that file.

Here is a Bb plugin that narrows it down for you, you will need to port it over to buddypress however.

https://bbpress.org/plugins/topic/bb-topic-views/

Anytime you make changes to the core you will lose them next time you update buddypress.

If it’s giving a bluehost 404 error, than something is wrong with your host, not buddypress. Try contacting Bluehost to see if there are any problems or issues with them or your account.