[@fairweb Participant 14 years, 11 months ago]

Found the translation bug.

In bp-events.php, line 2831

add_action ( 'plugins_loaded', 'events_load_textdomain', 9 );

should be

add_action ( 'plugins_loaded', 'events_load_textdomain', 1 );

As it was in 9 priority, it was loaded after

add_action( 'plugins_loaded', 'events_setup_globals', 5 );

That’s why the other strings loaded but not this one.

[@fairweb Participant 15 years ago]

Glad I could help as well.

Don’t forget to adjust user’s rights on blogs when a user is added or removed from a group.

Good luck and yes please, let us know how it goes.

[@fairweb Participant 15 years ago]

According to your project’s requirements, why do you absolutely need to develop a wiki ? I understand that you want easy writting facilities so why not using blogs ? Of course, there would be a lot to build in the group’s front end but at least you can use WP’s core functions.

1 – link a blog to a group, maybe using group meta (and make it private if needed) and give group users certain rights on blog.

2 – build a front-end tool for groups to be able to view, add pages and create content

3 – the post revisions could be useful to have full history of the page

Of course, work has to be done on user’s roles and capabilities to be able to view revisions and edit contents as non admin users.

This is just an idea, I don’t know if this could match your requirements.

[@fairweb Participant 15 years ago]

This problem occurred even though I had desactivated all plugins (including BP) before upgrading. And the Buddypress menu showed in the admin menu though I had not yet been able to reactivate BP due to the bp-activity error.

Like David Lewis, deleting the “active_sitewide_plugins” value in the wp_sitemeta table sorted it out.

[@fairweb Participant 15 years, 1 month ago]

Thanks for the tip.

[@fairweb Participant 15 years, 6 months ago]

I’ll be interested if you have such a solution.