[@owrede Participant 15 years, 1 month ago]

The problem is still existing…

[@owrede Participant 15 years, 5 months ago]

I am having the problem that sending a private message points to “/members/_myuserid_/messages/compose//” which in turn responds with a Forbidden-Error page. My User ID is not “admin” though I do have site admin privileges.

This does not seem to be the bug describred in the ticket at https://trac.buddypress.org/ticket/1820

Regards,
Oliver

[@owrede Participant 15 years, 11 months ago]

Hello.

I do have spam user registrations even with registration option set to:

[*] Only logged in users can create new blogs.

I understand this option to say that new user registrations are DISABLED but registered users may create blogs. Unfortunatly the “Register”-Button appears in the welcome widget with that setting — even though clicking it will redirect back to the homepage.

To disable the above option also disables the blog creation — which I do NOT want.

For an unkown reason I do see spam registrations (a couple per week) but it seems those users are not able to login and create blogs (or comment). I also do NOT get the usual notification mails for new user registrations.

It seems like a bug to me.

[@owrede Participant 16 years ago]

Great work! Thank you all! Site now healthy again!

[@owrede Participant 16 years ago]

Anybody here with a hint for a potential workaround?

The basic functionality on member profiles is broken now for my users – rendering the whole community somewhat useless as people constantly get redirected to the homepage without knowing/seeing why!

[@owrede Participant 16 years, 1 month ago]

Yes, they do work if I type them manually.

Submitting a form (e.g. editing the profile) does not work as the action-URL points to a non-existent method.

[@owrede Participant 16 years, 6 months ago]

WOOOOOOOT WOOOOOOOOOOOOOOOOOOOOOOOOT!

[@owrede Participant 16 years, 6 months ago]

There is a TRAC issue for that here https://trac.buddypress.org/ticket/192

[@owrede Participant 16 years, 6 months ago]

Thank you, Nicola!

Is there some example to learn from (regarding blog metas and hooks)?

I “kind of” understand the theory – but I lack the knowledge about the code base to know where to put what.

[@owrede Participant 16 years, 6 months ago]

http://campusphere.de/

A site supporting Department of Gestaltung @ Aachen University of Applied Science.

We are using blogs since 1999/2000. We ran on Userland Manila, then on individual WP sites. We moved to WPMU a while ago and now “upgraded” that with BuddyPress.

We need to change the organisation and update the templates a bit to better address the new users to the site (as it is not a general purpose social community), but I am waiting fo the dust to settle with BP 1.0, so that an own templates will be more stable.

I am currently transferring all the old Manila sites to WPMU.

[@owrede Participant 16 years, 6 months ago]

Maybe you are hit by a spam bot that creates new users? Have you tried to disable the signup?

[@owrede Participant 16 years, 6 months ago]

Update:

I seem to have an issue related to the WPMU-Version.

On the page https://buddypress.org/forums/topic.php?id=1994 I overlooked the “Please also make sure you are not using the MU trunk, but the 2.7 branch.” note — I was using the WPMU trunk. So I “downgraded” to the 2.7 branch.

Now I have “Activate XYZ plugin sitewide”-Options in the Plugin area. I still have a single BP-Plugin though. I activated the BP Plugin sitewide. And it seems to worl fine.

But I ran into following problem:

I needed to update “/wp-includes/capabilities.php” to the one of the trunk-Version. The one of the 2.7-branch gave me this error on all pages:

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in

/www/wpmu/wp-includes/capabilities.php on line 537



Warning: array_merge() [function.array-merge]: Argument #1 is not an array in

/www/wpmu/wp-includes/capabilities.php on line 537



Warning: array_merge() [function.array-merge]: Argument #1 is not an array in

/www/wpmu/wp-includes/capabilities.php on line 539

Discussion is not continuing on https://buddypress.org/forums/topic.php?id=1994

[@owrede Participant 16 years, 6 months ago]

Update:

I overlooked the “Please also make sure you are not using the MU trunk, but the 2.7 branch.” — I was using the WPMU trunk. So I “downgraded” to the 2.7 branch.

Now I have “Activate XYZ plugin sitewide”-Options in the Plugin area. I still have a single BP-Plugin though. I activated the BP Plugin sitewide. And it seems to worl fine.

But I ran into following problem:

I needed to update “/wp-includes/capabilities.php” to the one of the trunk-Version. The one of the 2.7-branch gave me this error on all pages:

Warning: array_merge() [function.array-merge]: Argument #2 is not an array in

/www/wpmu/wp-includes/capabilities.php on line 537



Warning: array_merge() [function.array-merge]: Argument #1 is not an array in

/www/wpmu/wp-includes/capabilities.php on line 537



Warning: array_merge() [function.array-merge]: Argument #1 is not an array in

/www/wpmu/wp-includes/capabilities.php on line 539

[@owrede Participant 16 years, 6 months ago]

Update:

I was wondering about BP behaving like a ordinary plugin – so I re-read the forum post regarding the movement from /mu-plugins/ to the /plugins/ directory (see https://buddypress.org/forums/topic.php?id=1994)

I stumbled over the part “enable each plugin but CORE first” there. In my context the BP plugins shows up as a single ordinary plugin. I can’t “enable CORE first” I wonder if that is realted to the issue I see here…

[@owrede Participant 16 years, 6 months ago]

I am confused by step #4:

Log in as a site admin, and head to the \”Plugins\” admin panel. You will need to activate each plugin (activate CORE first).

In my context the BuddyPress plugin in shows up as a single plugin – I can’t enable “each plugin and activate CORE first”.

I also seem to have the problem, that all my MU sites are “out of the BP context” now. Their activity/comments do now show up in the global activity stream anymore until I manually enable the (singular) BuddyPress-Plugin on each MU site. (see this thread here https://buddypress.org/forums/topic.php?id=2122).

Odd….

[@owrede Participant 16 years, 6 months ago]

There is no privacy-related plugin in either /plugins/ or /mu-plugins/ anymore.

What I have found out in the meantime is that after the movement of the buddypress plugin to the /plugin/ directory – I had to manually enable it on the top-level site. It also does appear as a regular plugin an ALL other sites (which feels flawed, as those sites should not list this plugin as “inherited option”).

The other sites get the standard MU-Admin bar. If I enable the BuddyPress plugin on that sites manually, I do get the BP-Admin-Bar again and it seems that their updates are being shown on the top-level site again. This feels like I need to got through all of the MU blogs an enable the BuddyPress Plugin manually.

From my conceptual understanding I think this can’t be the intended way – a BP installation should be globally – not per blog.

[@owrede Participant 16 years, 6 months ago]

Ok. Crated ticket here: https://trac.buddypress.org/ticket/669