[@boonebgorges Keymaster 15 years, 2 months ago]

You can put the group class into bp-custom.php.

Put the HTML markup for your fields in the display() method. In the create_screen_save() and edit_screen_save() methods, save the data in the $_POST array using groups_update_groupmeta().

[@boonebgorges Keymaster 15 years, 2 months ago]

`bp_the_topic_post_content()` is the echo function. Use `bp_get_the_topic_post_content()` instead.

[@boonebgorges Keymaster 15 years, 2 months ago]

@archonic Consider yourself ignored

[@boonebgorges Keymaster 15 years, 2 months ago]

@foxly and others – Just wanted to drop a note about a recent commit https://buddypress.trac.wordpress.org/changeset/4977 where I made a minor adjustment to the new load order that should help a lot with plugin backward compatibility. In particular, plugins that are using the (old and incorrect but functional in 1.2.x) method of hooking their global and nav setup routines to ‘wp’ and ‘admin_menu’, which wasn’t working in earlier revs of BP trunk, should now be working. See https://buddypress.trac.wordpress.org/ticket/3476 for more explanation.

That said, you should do the right thing and update your plugin so that it does it correctly: set up your globals at bp_setup_globals and your nav at bp_setup_nav!

[@boonebgorges Keymaster 15 years, 2 months ago]

@archonic bp-template-pack will be updated for 1.5, yes. What about the members/single files was particularly confusing?

@foxly Thanks for the new links. I’ve made the change.

[@boonebgorges Keymaster 15 years, 2 months ago]

Sure thing – thanks @karmatosed.

[@boonebgorges Keymaster 15 years, 2 months ago]

That’s one way to work around it

[@boonebgorges Keymaster 15 years, 2 months ago]

WP/BP versions? It’s hard to match line numbers without specific versions.

[@boonebgorges Keymaster 15 years, 2 months ago]

I know what the problem is, but not necessarily how to solve it.

These JS rich text editors work by hiding the HTML textarea, and hijacking the form submit process; when you submit the form, the CKeditor takes the content of its custom editor and puts it into the hidden textarea before the form is submitted for processing. The problem with the activity update form is that it’s submitted with ajax rather than with a regular HTML form submission (which requires a page load).

TinyMCE has a method called .triggerSave() that you can call manually on an event (such as (‘#whats-new-submit’).click()) that will do this content shuffling without a regular form submit. It’s possible that CKeditor has something similar.

[@boonebgorges Keymaster 15 years, 2 months ago]

@foxly Thanks. Yeah, it must be stripping iframe tags from non-Administrators. (And this is a separate install from wordpress.com, so it doesn’t have the googleapps shortcode.) Anyway, I’ve put them in there: https://codex.buddypress.org/releases/1-5-plugin-compatibility/

Not sure what’ll happen when a non-Admin edits the page; they may get stripped again. I’ll try to figure out a way around this.

[@boonebgorges Keymaster 15 years, 2 months ago]

In BP 1.5, there is a function `bp_is_user()`, which will return true on any member page.

If you need to support BP 1.2.x, do the following:
`global $bp;
if ( !empty( $bp->displayed_user->id ) ) {
// member page stuff
}`

[@boonebgorges Keymaster 15 years, 2 months ago]

@foxly I’m not sure I have the authority to make you a super admin, but I’m happy to try embedding it myself. Can you give me the URLs for the docs, or the embed code?

[@boonebgorges Keymaster 15 years, 2 months ago]

@foxly Both you and @fanquake are Editors on codex.buddypress.org. (It used to be that everyone on bp.org was, but the synching script broke at some point.) Thanks!

[@boonebgorges Keymaster 15 years, 2 months ago]

I knew you knew @foxly

[@boonebgorges Keymaster 15 years, 2 months ago]

I’m a bit confused at what this discussion is trying to accomplish

When you set up globals, as in the function excerpted above, you should hook to bp_setup_globals.
When you set up navigation, as with functions like bp_core_new_nav_item(), you should hook to bp_setup_nav.

[@boonebgorges Keymaster 15 years, 2 months ago]

Thanks for posting that tutorial, @foxly. The ‘wp’/’admin_menu’ hook is a very old technique that has nonetheless continued to work. I’ve got that on my list of things to write about on bpdevel.wordpress.com. Maybe I’ll do so later today, and link to your very helpful wiki page.

[@boonebgorges Keymaster 15 years, 2 months ago]

I kind of agree with @djpaul. The average user will (or at least should!) have WP_DEBUG disabled, and will (or should!) have error reporting turned off. In that sense, those plugins are in fact compatible with BP 1.5. (To put that another way, if we go by the strict standards, they were never compatible with any version of BP )

[@boonebgorges Keymaster 15 years, 2 months ago]

What do you mean that the website “crashed”?

It’s highly, highly unlikely that BuddyPress would have caused you to lose any data. If, after activating BuddyPress, your screen goes white, it usually suggests that you have insufficient memory on your server. In that case, simply navigate to wp-content/plugins with an FTP client, and delete the buddypress folder. WordPress stores content separately from its program files, and your data is still safe.

Here is a very helpful codex page on “blank screens”, which is what I assume you mean by “crashed”: https://codex.buddypress.org/troubleshooting/blank-pages/

[@boonebgorges Keymaster 15 years, 2 months ago]

Great!

If you’ve got command-line access to your server, you can check out latest development version via Subversion. Create an empty directory /wp-content/plugins/buddypress/, and then
`svn co https://svn.buddypress.org/trunk`
The nice thing about this is that you can then upgrade to the latest development version at any time by going into that directory and typing
`svn up`

It’s not recommended that you run the trunk version on a production server, though – only a development or test server.

[@boonebgorges Keymaster 15 years, 2 months ago]

When’s the last time you svn upped your installation? Or are you using one of the BP 1.5 betas? I’ve been told that this issue has been identified and fixed since BP 1.5-beta-2: https://buddypress.trac.wordpress.org/ticket/3469#comment:1

[@boonebgorges Keymaster 15 years, 2 months ago]

oops, you answered my question before I asked it

Yes, that sounds like a bug. I have opened a Trac ticket, which you can follow for updates: https://buddypress.trac.wordpress.org/ticket/3469

[@boonebgorges Keymaster 15 years, 2 months ago]

I was not able to reproduce either issue. When new users sign up, their display name is correct. And data is correctly synced back and forth between display_name and the BP name field.

Have you changed the name of your Full Name field? What did you change it to?

[@boonebgorges Keymaster 15 years, 2 months ago]

BuddyPress Group Email Subscription 2.9 has just been tagged, and is fully compatible with BP 1.5.

[@boonebgorges Keymaster 15 years, 2 months ago]

I’ve just released 0.5 of BP Group Management, which is fully 1.5 compatible (it already was, btw, but I cleaned up some PHP warnings and other small issues )

[@boonebgorges Keymaster 15 years, 2 months ago]

@foxly I can’t say “thanks” enough for the effort you guys are putting into 1.5 compatibility. This is a *huge* help to the community (and benefits you too, since it gets 1.5 out sooner )

It’ll be great to get @karmatosed write-access to the google doc. She has stepped up and taken a leadership role with a 1.5-compat codex page and with this forum thread, and it will be great for you to combine your resources – BP Media checking compatibility in-house, and @karmatosed (and others) collecting reports, etc from the forums.

Again, thanks so much.