Forum Replies Created
We’ve been testing against PHP7 nightly releases for a long time. It helps that our PHP is newer than most of WordPress’, so we have less really old stuff to migrate.
You can view our test coverage on https://travis-ci.org/buddypress/BuddyPress/ (“PHP: nightly” is PHP7), as you can see, there’s currently a failure with one test that we need to fix. It looks fairly straightforward to fix, and we’ll do that soon.
This one test aside, to the best of knowledge, yes, BuddyPress works with PHP 7.
If the SQL operation was carried out successfully (eventually), BP will have bumped a database version number, and next time, it wouldn’t have checked for schema updates.
Don’t want to vouch for security without actually testing it, but I like the idea of allowing field values to be parsed for oembeds, so I’ve created a ticket to capture the idea: https://buddypress.trac.wordpress.org/ticket/6603
@reggie3 what version did you upgrade from?
I think you’re going to need to copy/paste the name of each city into a dropdown box field type. I don’t think there’s any easy or quick way of doing this.*
*There are more developer-orientated ways to do this, but if I were doing this, I’d just keep it simple as you only have to do it once.
@ajarnonline Please don’t create duplicate topics: https://buddypress.org/support/topic/buddypress-xprofile-rich-text-field/
You’re only going to get the same answer.
If that’s the exact code you’re using (and it hasn’t been mangled by the forum), you need to use
"marks instead of
'for PHP to convert the
\ninto a newline.
You’re wrong — we do care about feedback, so thank you for sharing yours. You’re totally correct that there’s several plugins in town that offer features of part of BuddyPress (or in Peepso’s case, all of it), and that the biggest distinguishing feature that they have seems to be the visual appearance. It is important, and as a contributor to BuddyPress, I personally always focus on making the BuddyPress experience better for these types of new users (not just for developers, etc), so what you say makes a lot of sense.
We took a decision perhaps two years ago to make sure BuddyPress worked on every theme. To achieve this, we decided on an approach where we made the look/feel as minimal and generic as possible. The compromise means that right now, BuddyPress doesn’t offer a really strong visual appeal. What we’ll do in the future, I’m not sure yet, but we have had more discussions about the next approach to a new set of BuddyPress template in the last 6 months than we’ve had in the years prior to it, which I take as positive.
It feels like a long time away saying hopefully we’ll look much better in the six months, but there’s so many cool features and enhancements to work on, and it’s a matter of each individual contributor being able to contribute their time on working on whatever they personally want to do.
Part of the solution for BuddyPress is to find some great WordPress theme developers who are interested in helping out with that part of BuddyPress; someone could come in and really define the look of BuddyPress for 2016. If anyone out there reading this is interested, but isn’t sure how to get started, just send me a message (paul at buddypress.org).
Not a bug, Hugo just didn’t grant you access. I’ve given
bobbingwideeditor permission on codex.buddypress.org, @herbmiller — thanks for contributing.
@hnla — “bobbingwide” is not listed on the codex.bp.org/wp-admin/users.php page.
This was a great success. Write-up coming soon on the website! Thanks for coming.
@hnla you need to add the user as an editor in wp-admin
Just wanted to bump this as the event is pretty soon!
And what browser — if your site is public, we could test and figure it out.
I think this is a quirk of how the function works. The menu items are built in the
bp_get_nav_menu_itemsfunction, so I suggest investigating there. I think @boonebgorges hints at the root cause in this comment: https://buddypress.trac.wordpress.org/ticket/4624#comment:6
We have now released BuddyPress 126.96.36.199 which fixes this problem.
This is now fixed in the recently-launched BuddyPress 188.8.131.52 release.
Try the BuddyPress 184.108.40.206 release, which we put out a little while ago.
This is a general WordPress problem, not specific to BuddyPress. You will get better help if you look at the WordPress.org support forums: for example, https://wordpress.org/support/topic/automatic-plugin-upgrade-not-working-ftp-problems?replies=47
We have just released BuddyPress 220.127.116.11 which includes the fix for this problem. Please upgrade, and we’re very sorry for the inconvenience that the initial 2.2.2 release caused.
Bug ticket is https://buddypress.trac.wordpress.org/ticket/6369.
I am going to close this thread because we have a similar discussion happening over here: https://buddypress.org/support/topic/fatal-error-after-update/#post-237672