BuddyPress.org

I have a version of the plugin that’s 1.5-compatible almost finished. I’ll try to release it today.

If I manually install 1.5 RC1, will I be notified and be able to update normally/successfully via the dashboard when 1.5 is released?

Yes.

Since 1.2.11 is in the works, I’m assuming 1.5 isn’t going to be […]

@valuser Thanks for your patience, and for the kind words 🙂

Just to be clear, bp-default has been fixed to do automatically what @karmatosed suggests you do manually. This is only an issue for the BP Template Pack.

In the meantime, why not just use more specific […]

It probably means that the stylesheet for bp-template-pack is being loaded after your custom styles. For now, either use !important, or just use a more specific selector. I’ll open a ticket on Github to see if […]

Are you sure that the styles are coming from bp-default, and not from the bp-template-pack CSS? (It would be very strange indeed if it came from bp-default, unless of course your theme is a child theme of […]

The plugin does not use a real cron job. it’s wp’s “pseudo-cron”, and it will stop a soon as the plugin is disabled.

The command would be something along the lines of

DELETE FROM wp_bp_groups_groupmeta WHERE meta_key = 'ass_subscribed_users';

though I must say that I do not recommend doing this, as there is no undo!

BPGES doesn’t create any tables. It stores some data in _bp_groups_groupmeta, with the key ass_subscribed_users, as well as some usermeta. Probably not worth cleaning out, unless you have serious performance issues.

See https://codex.buddypress.org/developer-docs/group-extension-api/, especially the edit_screen(), create_screen(), and corresponding “save” methods. If you don’t want to have a public tab associated with the […]

2 – You would have to write some javascript that does the refreshing. I don’t know of any ready-made implementations.

3 – There’s no automatic way to filter these out in BuddyPress at the moment. You could […]

Very strange. Well, if the problem arises again, take careful note of what plugins you may have turned on/off around that time, and then post again here. Thanks for your patience.

Sorry about that, I misread what you were writing. I understand now.

Have you, by chance, turned off any BP plugins recently? I have a hypothesis that there are notifications in your database corresponding to a […]

So what happens when you do
var_dump( $major );
after all of this? Does it show up as false, or undefined? If false, the problem is that the user has not filled in the data (or the field doesn’t exist). If […]

Hm. Your upgrade must not have completed properly. In BP 1.5 RC1, there is no file called bp-core/bp-core-notifications.php. That file, along with the files that called it, must be left over from your pre-upgrade […]

Very strange. I wonder how old notifications might have caused this problem. You don’t happen to have access to your server’s PHP error log, do you? It might help to see whether this is a problem with BP itself.

The plugin folder must be called ‘buddypress’. Yours is called ‘1.5-rc-1’.

The current stable version of the template pack has not been verified as compatible with BP 1.5. You can get the dev version from https://github.com/boonebgorges/bp-template-pack

Did you upgrade from BP 1.2.9 or another version?