[@hnla Participant 16 years, 4 months ago]

@Marco72

You could achieve zebra striping of the activity-stream LI elements using this approach (tested as working but I would defer to the more experienced as to whether it’s a valid or best)

In file bp-themes/bp-default/activity/activity-loop.php

add line ‘<?php $class = ‘even’; ?>’ above line 20 ‘<?php while ( bp_activities() ) : bp_the_activity(); ?>’

Immediately below the while loop on line 20 add:

‘<?php $class = ($class == ‘even’) ? ‘odd’ : ‘even’; ?>’

To print out the odd or even classes go to the file:

bp-themes/bp-default/activity/entry.php

And add :

‘<?php print $class; ?>’ to line 5 so it looks like:

‘<li class=”<?php bp_activity_css_class() ?> <?php print $class; ?>” ‘

You can then style the classes ‘odd’ and ‘even’ as you wish.

[@hnla Participant 16 years, 4 months ago]

I would be careful about confusing plain single user WP with WPMU they are not exactly the same beast and that list – which is written with single user WP in mind – suggests things that would perhaps be inadvisable such as renaming DB tables.

As for hiding the admin account not really sure it’s that huge a concern? but others may suggest a means.

[@hnla Participant 16 years, 4 months ago]

You keep bp-custom.php within your BuddyPress plugin directory? I have mine in the root of /wp-content/plugins/

[@hnla Participant 16 years, 4 months ago]

Testing further a bit one thing that appears apparent is that with compatibility plugin enabled and all legacy components selected one can still access and post to the wire in ones profile while also having the newer ‘Updates’ approach available, however posting on your wire does not appear in main activity stream -is it supposed to? I’ve disabled the legacy component ‘Wire’ and what is apparent is that I can still read older comments made via ‘Wire’ so am thinking that it’s perhaps better to disable further use of the ‘wire’ in favor of ‘Updates’ . The issues being though how would members take to that and the Twire plugin at present is broken but would it work anyway with the ‘Wire’ disabled and it’s a feature that is liked.

[@hnla Participant 16 years, 4 months ago]

I don’t think I found anything disabled by default. The ‘what’s New’ textarea window allows me to post updates to ‘My Profile’ or groups and when submitted it does appear in the general activity stream, logging in as a different user I can then directly reply to the comment left from within the general activity stream. I did have to kick things into life a bit though.

Overall the methodology of the new activity stream does feel a lot better and I am getting used to it, however it has been a fair bit of work working it into an existing layout, buts that’s another issue that I touched upon briefly as a footnote to my earlier post – I’m still of the opinion that upgrading to 1.2 but attempting to maintain backwards compatibility is not straightforward due to inherent changes to markup and class tokens which throws up a bit of confusion, and am finding that major features implemented such as ‘Events’ plugin are not compatible which cause one to have to think carefully about upgrading a live site where this sort of feature is in regular use.

[@hnla Participant 16 years, 4 months ago]

But ‘is_site_admin()’ is a WP function not BP; seem to remember mention of a change to something like ‘is_super_admin()’ but things shouldn’t break – should they? if the function is deprecated that’s fine but the function should still work, it’s quite a critical thing really

[@hnla Participant 16 years, 4 months ago]

It’s not gone just radically altered?

It’s part of the activity stream now?

I think if you want it exactly as before you need to use this plugin provided to maintain backwards compatibility:

https://codex.buddypress.org/getting-started/upgrading-from-10x/

https://wordpress.org/extend/plugins/buddypress-backwards-compatibility/

But someone more versed in these matters may provide a better answer.

Maintaining this backwards compatibility does not seem straightforward though, and a better step by step guide would be useful, and I’m not sure that in reality 1.1.x and 1.2 are such different beasts that 1.2 ought to be considered a separate branch at least it doesn’t really feel as though 1.2 is an upgrade from 1.1 less a point release than a milestone almost a 2.x?

[@hnla Participant 16 years, 4 months ago]

And I have demonstrated the test conditions of a clean install of 2.9.1.1 and BP 1.2 with NO additional plugins.

However I will qualify ‘clean install’ by adding that BP 1.1.3 was originally installed activated once deactivated and not used on this particular install other to test once only that it was functioning. BP was upgraded to 1.2 for purposes of this test and activated.

[@hnla Participant 16 years, 4 months ago]

*bump*

Sorry but bumping this as I would like a little further info if possible, if it were a minor issue I might ignore but frankly it’s not?

I can hunt through the trac for the issue and any fix I guess but would like to know if it’s something we can address for versions other than latest trunk.

[@hnla Participant 16 years, 4 months ago]

Re reading the original response do I take it that we are saying it’s a problem that is evident in 1.2 but fixed in 1.2.1

I neglected to state the version the issue was occurring in although it can be surmised from what I mentioned earlier but I am running 1.1.2 planning for a 1.1.3 upgrade.

It seems that this issue runs through a few versions? if it is fixed in 1.2.1 can we have a idea of what the issue is/was as that may help to understand why it’s seemingly a random event and possibly what actions/plugins it might be triggered by. is there a ticket on the issue?

[@hnla Participant 16 years, 4 months ago]

Oh dear not the response I was hoping for

So it is an issue and frankly a horrendous one, blogs are offered to users as fully functioning ones.

Sadly it’s not necessarily a straightforward matter to upgrade, at the moment I would have to run the backwards-compatibility plugin as I have got the community up and running based on a child theme overriding bp-sn file where necessary, in tests on local dev install upgrade to 1.2 I had to do a fair bit of work to get the existing theme running again and to rework styles to accommodate the new activity stream layout.

Thanks for the quick response though DJPaul I have to now figure how we proceed as too many aspects of the 1.x are demonstrating problems and I’m beginning to wish we had been able to wait for 1.2 to be released.

One point of interest though on another of the many test installs I keep running and one that I have kept pretty close to the production site in plugins and customizations this issue doesn’t arise and I can create pages quite happily so this can’t simply be a inherent BP issue but triggered by some action or plugin but don’t see what at this stage.

[@hnla Participant 16 years, 4 months ago]

I’m somewhat at a loss as to why people debate this issue or try and state it’s a WP issue as logically that doesn’t make sense?

As jfigura posts this is an inherent problem, I have it on a production install and it must be hugely confusing for users, and yes the only approach so far has been to modify the text and remove the WP password from the confirmation emails.

Further testing points to the initial blog registration as being possibly the issue:

Clean install of WP MU 2.9.1 & BuddyPress 1.2 no significant further plugins activated.

Test Condition 1:

WP MU with BuddyPress disabled – admin options -> Allow New Registrations ->’Only user account can be created’

Register new user

Receive confirmation email of new registration along with Activation key

Activate registration

Receive second email with account username and pass

All as expected!

Test Condition 2:

WP MU with Buddypress activated – admin options for registration still set as ‘User Account only’

Register new user

Receive confirmation and activation key

Activate registration – screen message stating ‘you can now login with user name and password you set’

No further emails sent!

Test Condition 3:

WP MU BuddyPress still activated – admin options -> Allow New Registrations -> ‘Enabled. Blogs and user accounts can be created.’

Register new user as well as a blog!

Receive confirmation and activation for account and new blog

Activate registration – screen message ‘you can now login with password you set etc etc’

Receive further email from WP! (copied below)

Dear User,

Your new *********.co.uk Blogs blog has been successfully set up at:

http://eggs.********.co.uk/

You can log in to the administrator account with the following information:

Username: eggbert

Password: 5f112917

Login Here: http://eggs.**********.co.uk/wp-login.php

We hope you enjoy your new blog.

Thanks!

–The Team @ ********.co.uk Blogs – Sent via Site Admin options email

So having new accounts and new blogs enabled at initial registration triggers the sending of the ‘Welcome Email’ noted above.

clearly this is confusing as it contains the WP generated password.

Why is it that BP registration doesn’t disable / override the WP registration completely? To my mind this IS a BP issue, but I may very well be wrong on that score as I don’t profess to have a deep understanding of the core coding involved here.

On a sidenote:

Testing this and the slightly odd behavior of ‘Allow New Registrations’ where option for ‘only logged in users can take a blog’ actually seems to prevent all registrations. It occurred to me that on a social community ,and from our experience, blogs are not necessarily what users register for and that I would prefer the option to have a blog be only available for registered users from their account options. what actually happens is that registration is disabled completely! Not the effect I desired. I realise this IS a WP MU issue but is simply daft behavior and that set of options needs to be re-worded to be a lot clearer as to what it really does.

It would be great to be able to restrict blog signup to users already with account set up and remove, completely, the option to take a blog on initial signup, I have done this by simply scripting out the option / section for registering a new blog in BP register page but feel it’s not the best approach?