[@josswinn Participant 10 years, 10 months ago]

Yes! That’s it. Thanks for pointing this out, Henry. I shall link the bug report to this thread and offer to help bug test.

Cheers
Joss

[@josswinn Participant 10 years, 10 months ago]

… and if I activate ‘Activity Streams’ but add

add_filter( 'bp_activity_do_mentions', '__return_false' );

to bp-custom.php, the problem is resolved.

So it looks like, for some reason, I can’t have mentions enabled without the problem occurring. Can anyone think why?

Thanks,
Joss

[@josswinn Participant 10 years, 10 months ago]

For the record, I’ve narrowed it down to the ‘Activity Streams’ component of BuddyPress. When this is disabled, the problem does not occur.

[@josswinn Participant 10 years, 10 months ago]

I suppose another way of looking at this would be to find the code in BuddyPress that injects hyperlinks into certain text, such as profile tags. Where would I find this?

Thanks.

[@josswinn Participant 10 years, 10 months ago]

Hi again,

I still have this problem. I’m sure it’s BuddyPress that is the cause, as it still occurs with different themes and with all other plugins deactivated. When I deactivate BuddyPress, the problem stops.

Run your mouse over the links on this page, and you’ll see the issue: http://blogs.lincoln.ac.uk/test/

I was wondering whether it is a legacy of running BuddyPress since alpha/beta and whether there is an old setting in the database or something that I might look out for. Where are the BuddyPress settings stored in the database? None of the wp_bp tables look like they hold global settings.

In my wp-config.php file, I have the following:

define( ‘BP_ENABLE_ROOT_PROFILES’, true ); //removes the /members/ slug
define( ‘BP_DEFAULT_COMPONENT’, ‘custom-profile’ ); //defaults to profile page rather than activity stream of a user
define( ‘BP_ENABLE_USERNAME_COMPATIBILITY_MODE’, true ); //for LDAP compatibility
define ( ‘BP_IGNORE_DEPRECATED’, true );
define(‘BP_USE_WP_ADMIN_BAR’,true);

Thanks for any advice,
Joss

[@josswinn Participant 10 years, 11 months ago]

UPDATE:

I’ve changed BuddyPress from being ‘network activated’ to just ‘activated’ on the main/root site. I don’t know what the recommended setup is these days, but we’ve had it network activated since BuddyPress only ran on WPMU.

Having it activated on the main site only means that the ‘bug’ now only affects the main site and not every site across the network. So the example I give above no longer shows the issue.

However, you can still see it on this page:

http://blogs.lincoln.ac.uk/test/

See how, whenever there is @lincoln.ac.uk either in the content of the page, or in a mailto link, BuddyPress injects a hyperlink with a random user’s email address following the root domain:

http://blogs.lincoln.ac.uk/amakrzanowska%40lincoln.ac.uk/

I’ve no idea how or why it’s constructing that URL and automatically inserting it whenever @lincoln.ac.uk is found in the body content.

Ideas much appreciated!

[@josswinn Participant 11 years, 7 months ago]

Well, at least I know it is possible! I’ll have a look around for those instructions. Thanks.

[@josswinn Participant 11 years, 7 months ago]

Thanks. I have a use for Multisite Plugin Control, but it doesn’t solve the issue with bbPress because bbPress can *only* be activated across the network, and so it comes outside of Multisite Plugin Manager’s control.

Anyway, thanks again. I will be using the multisite plugin for other reasons!

[@josswinn Participant 11 years, 7 months ago]

huh. I don’t understand why it’s different for me. I’ll go back and look into it. The other problem though is that if it’s just activated on the main site, then I guess it will still be listed as a plugin for other members to activate on their own sites (we allow this with plugins).

Thanks for your response.

[@josswinn Participant 11 years, 7 months ago]

I agree. But there is no other option. On a network install, the only option to activate bbPress is to ‘network activate’ it.

[@josswinn Participant 11 years, 7 months ago]

Thanks. I see what you mean, but it’s too focused on commercial upgrades, whereas the site I managed it based at a university with students and staff as users.

Thanks anyway. There used to be a plugin called ‘Plugin Commander’ that might also have worked, but having tested that, it doesn’t seem to work at all with the current version of WP. Also, because bbPress can only be network activated on a network install, I’m not even sure it would have been any use anyway.

[@josswinn Participant 14 years, 9 months ago]

On this subject, how about building RSSCloud and PubSubHubub into the Activity Stream RSS feed? There are plugins for WordPress, written by Automattic. I guess they could be modified to work for BuddyPress feeds?

https://wordpress.org/extend/plugins/pushpress/

https://wordpress.org/extend/plugins/rsscloud/

[@josswinn Participant 14 years, 10 months ago]

Thanks, mark. That’s what I needed.

Andy, the problem is that the More Privacy Options plugin adds new privacy levels, like on wordpress.com and the Activity Stream doesn’t recognise those. It only knows about Searchable/Not Searchable ‘privacy’ options (I’ve never understood why blocking search engines is referred to as ‘private’ – I think it’s misleading).

[@josswinn Participant 15 years, 2 months ago]

Thanks. It was a problem with the theme which has been fixed in the last couple of days. An upgrade of the theme solved this. http://premium.wpmudev.org/project/buddypress-corporate-theme

[@josswinn Participant 15 years, 2 months ago]

It’s not related to my browser. It happens on all browsers, on all blogs and on all themes. It even happens in the Dashboard area. You can see an example snapshot here: http://joss.blogs.lincoln.ac.uk/files/2009/11/Picture-2.png

[@josswinn Participant 15 years, 2 months ago]

Hi, I’ve upgraded to 1.1.1 and am getting lots of these warnings, too. A custom theme from dev.wpmu.org

I’ll post over there to see if they claim responsibility!

[@josswinn Participant 15 years, 5 months ago]

I’ve just upgraded to 1.0.3 and this message is back, despite Andy’s fix noted above.

PHP Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /var/www/vhosts/blogs/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-signup.php on line 261

Not critical, but annoying to see it so often in the logs

[@josswinn Participant 15 years, 6 months ago]

Yeah, thanks Andy

[@josswinn Participant 15 years, 6 months ago]

Still seeing the warnings in my logs following the 1.0.2 update:

PHP Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /var/www/vhosts/blogs/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-signup.php on line 261

[@josswinn Participant 15 years, 6 months ago]

I’ve tried to trigger it in safari, IE and Firefox but haven’t managed it. Still seeing the warnings though, but they’re not from me on the site.

[@josswinn Participant 15 years, 6 months ago]

I can’t tell you if it’s browser related. I’m using Chrome and I can’t trigger it but I’m seeing other IP addresses trigger it every few minutes. I could try switching log level to debug and see if that shows the browser identifier. If I get anything, I let you know.

PHP 5.1.6 (cli) (built: Feb 26 2009 07:01:12)

Copyright (c) 1997-2006 The PHP Group

Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

with eAccelerator v0.9.5.3, Copyright (c) 2004-2006 eAccelerator, by eAccelerator

Apache/2.2.3

WPMU 2.7.1

BuddyPress 1.0.1

No other errors in my logs

Thanks.

[@josswinn Participant 15 years, 7 months ago]

Thanks for your quick response, Andy.

[@josswinn Participant 15 years, 9 months ago]

Socialpreneur is quite right. The plugin works very well. The issue is changing the template so users are directed to wp-login.php as an alternative to normal signup in the way that the fb-connect plugin is integrated into the default themes.

[@josswinn Participant 15 years, 9 months ago]

Not me. I haven’t the skills but it seems like a quick win for someone who does.

[@josswinn Participant 15 years, 9 months ago]

well, i don’t know what to do. i’ve set up another test site and there’s no problem. i think i’ll just remove the problem site and start again. not a big deal.