[@boonebgorges Keymaster 15 years, 7 months ago]

bp_dtheme_blog_comments() is a callback for wp_list_comments in comments.php. So the best way is to give your new version a different name (eg chouf_blog_comments() ) and then change comments.php in your new theme to call that function instead of the bp_dtheme version, eg
` ‘chouf_blog_comments’ ) ); ?>`

[@boonebgorges Keymaster 15 years, 7 months ago]

Unfortunately, this is quite complicated. Adding another item to the Order By dropdown is quite easy, using the ‘bp_members_directory_order_options’ hook (or putting the additional option directly in the members/index.php file of your theme). But making it actually work in terms of reordering will be complicated – it will involve hijacking part of the loading process, and filtering the members queries (see bp-core/bp-core-classes.php, around 193).

[@boonebgorges Keymaster 15 years, 7 months ago]

Weird, I’ve never heard of this error before. Is it happening with other WP or BP emails? (Other WP emails include comment notification and password resets – give one of them a try)

[@boonebgorges Keymaster 15 years, 7 months ago]

Hi Paul,

If I understand your question correctly, you should be able to find some help in the function bp_activity_new_comment(), in bp-activity.php. Look especially around line 752. That’s where the action is put together for activity comments. In a plugin, you can filter ‘bp_activity_comment_action’ something like this:

`function bbg_comment_reply_action( $action, $userlink ) {
// Do whatever you want to $action, and then:
return $action;
}
add_filter( ‘bp_activity_comment_action’, ‘bbg_comment_reply_action’, 10, 2 );`

Good luck!

[@boonebgorges Keymaster 15 years, 7 months ago]

Hi Donald,

It sounds like the plugin hasn’t been updated for WP 3.1, which introduced the new Network Admin (where the BuddyPress dropdown is now found).

Follow the instructions in this post https://buddypress.org/community/groups/buddypress-group-email-subscription/forum/topic/change-admin_menu-to-network_admin_menu-for-wp-3-1-and-bp-1-2-8/ except do it on the file buddypress-auto-group-join/php/bp-auto-group-join-init.php. That should do the trick.

[@boonebgorges Keymaster 15 years, 7 months ago]

@nexia Open source community projects like BuddyPress are built by volunteers. That means: people *volunteer* their improvements, in the form of patches. You’re not under any obligation to provide a patch. However, it’s a misunderstanding of how the development process works when you scoff at the idea of voluntarily providing a patch – “i’m not using the trac… if the guys want it, they can ask” – as if BP is some separate entity with its own timeline and development roadmap. Instead, BP is made up of those people who choose to contribute.

That does not qualify as “crapping trac”. It’s what Trac is for, and it’s how the project moves forward

Anyway, if you aren’t going to make a patch, I’d love to see the code anyway – please do post a link if you decide to release a plugin.

[@boonebgorges Keymaster 15 years, 7 months ago]

acpage is the way that BP renders activity pagination to those clients with javascript disabled – such as search engines.

I started a ticket for discussion of technical issues: https://trac.buddypress.org/ticket/3116

[@boonebgorges Keymaster 15 years, 7 months ago]

Thanks! I helped with some of the BP UX, but not the design at all. I did the BP customization, as well as some of the work on geography quizzes.

[@boonebgorges Keymaster 15 years, 7 months ago]

There are a few rules you will probably want to follow if you want help on these forums:

– Please don’t call out every notable user by name. Use the @-mention system for drawing someone’s attention to an item when it’s relevant to them. To flag everyone down every time you have a problem has the potential to be quite annoying.
– Make your forum post titles descriptive. Almost everyone in this forum is looking for help; naming your topic ‘HELP’ does not help anyone else to know what your problem is. Also, no need for all the exclamation points.
– Please give as much information as you can about your installation. You are apparently not running the latest stable version of BP (1.2., as line 432 of bp-core-signup.php in BP 1.2.8 does not have a reference to bp_core_signup_user(): https://trac.buddypress.org/browser/tags/1.2.8/bp-core/bp-core-signup.php#L432 Try upgrading to the most recent version of the software, or at least providing more details about your installation: WP/BP versions, other plugins you are running, etc.

[@boonebgorges Keymaster 15 years, 7 months ago]

I think you’re probably right that this should be a class rather than an id, but it needs a bit more of an audit (in particular, a sweep through the rest of the core code to ensure that changing it to a class selector wouldn’t break everything else). @aljuk, would you mind opening a ticket on trac.buddypress.org to that effect, using the same username/pw as you do on this site?

[@boonebgorges Keymaster 15 years, 7 months ago]

Thanks for the kind words

Good thought on the cross-posting. The plugin is built in such a way that cross-posting can easily be done – I just haven’t built anything on the front-end for it to work yet. Also, I’m planning to build a piece that allows users to see lists of their own docs under their profile, but that will probably have to wait for the second public release, as it involves writing quite a bit of code.

[@boonebgorges Keymaster 15 years, 7 months ago]

FYI – The first iteration of BP Docs will *not* have any upload features. However, on the short list of near-term developments is integration with Peter’s BP Documents, which is the de facto document storage solution on the site that I run. I’ll make the upload component in a detached enough way that you could build your own plugin that uses BP Media or the native WP media storage functions for file storage on the backend.

[@boonebgorges Keymaster 15 years, 7 months ago]

If you made changes to the core files, then yes, those changes will be deleted. What do you mean by “made some changes”?

[@boonebgorges Keymaster 15 years, 7 months ago]

The safest way to do it is like this:

– If your site is currently being actively used, block access with an .htaccess rule. (This is not required, but I do suggest it.) See http://www.techiecorner.com/97/redirect-to-maintenance-page-during-upgrade-using-htaccess/ for example
– Download the most recent stable build of BuddyPress https://downloads.wordpress.org/plugin/buddypress.1.2.8.zip and unzip.
– With an FTP program, go to wp-content/plugins. Delete the buddypress directory and its contents (Don’t worry – this only deletes the plugin files. Your data is stored elsewhere, and is completely safe.)
– Upload the unzipped buddypress directory to your wp-content/plugins directory.
– Verify that the site is working, and then remove the redirects from .htaccess (if you did that step).

[@boonebgorges Keymaster 15 years, 7 months ago]

Try deleting and reinstalling the BuddyPress 1.2.8 files. It sounds like you got a corrupted version.

[@boonebgorges Keymaster 15 years, 7 months ago]

The file should be bp-custom.php (with a hyphen, not an underscore). Also, make sure you have opening and closing PHP delimiters:
`<?php
// your code here
?>`

[@boonebgorges Keymaster 15 years, 8 months ago]

Thanks for the step by step, albill. We’re still trying to straighten out the problems with the wordpress.org repository, and we’ll have a real fix soon. Sorry for the inconvenience, all.

[@boonebgorges Keymaster 15 years, 8 months ago]

Hm…comments seem to be enabled, from what I can see?

[@boonebgorges Keymaster 15 years, 8 months ago]

There is a problem with the way that wordpress.org created the zip file. We’re looking into it.

[@boonebgorges Keymaster 15 years, 8 months ago]

I got 99 problems.

[@boonebgorges Keymaster 15 years, 8 months ago]

You should always test *any* upgrade of *any* type in a development or test environment. Never, ever, ever, ever, ever put untested code into production! A word to the wise

[@boonebgorges Keymaster 15 years, 8 months ago]

The changes that have been made in BP 1.2.8 are very, very unlikely to break any plugins. It’s possible that some of the changes in WP 3.1 will break some BP plugins, though I don’t know of any plugins where that is the case (and I have been running 3.1 in my test installs for quite some time).

[@boonebgorges Keymaster 15 years, 8 months ago]

BuddyPress will be updated later today to account for changes in WP 3.1.

In the meantime, if you have upgraded your live site and are unexpectedly missing the BP admin bar, use the code provided by aces above.

[@boonebgorges Keymaster 15 years, 8 months ago]

Hooray for understanding!!

[@boonebgorges Keymaster 15 years, 8 months ago]

Instances of do_action() don’t, in themselves, do anything. They are signposts (‘hooks’, in WordPress terminology) that allow other plugins to add functionality. It is thanks to such idle hooks in WordPress that BuddyPress is able to function. See https://codex.wordpress.org/Plugin_API for more info about how the system works.

Grep will tell you the locations of all references to the text you provide. Generally, that will give you enough information to open up the file(s) given in the grep results and look at the specified line. I just ran the command I gave you above, and I got the following result:
`./bp-themes/bp-default/registration/register.php:162: `
In other words, as I suggested, this particular text is only mentioned in one place in BP – the moment where it is defined. The hook is not called by any function in BuddyPress.