[@johnjamesjacoby Keymaster 7 years, 12 months ago]

My guess is the cookie hashes probably changed.

Make sure that all of your cookie settings in wp-config.php actually match what you want/need for them to be. If you need to share cookies across many subdomains, you’ll need a . at the beginning of them.

// Domain & Hash
define( 'COOKIE_DOMAIN', '.domain.com'        );
define( 'COOKIEHASH',    md5( COOKIE_DOMAIN ) );

[@johnjamesjacoby Keymaster 7 years, 12 months ago]

That’s a neat plugin, @robin-w.

I haven’t reviewed it, but the premise seems sound. Integrate it with the Customizer, and it might be a neat addition to the default template pack!

[@johnjamesjacoby Keymaster 7 years, 12 months ago]

Thanks for trying things out. What isn’t working? It’s not saving? It’s not giving them moderation capabilities? The form should pop-up an autocomplete, and I think it verifies usernames and only accepts valid ones. It ends up saving the user ID, not the username, because usernames can be changed but changing IDs would break stuff.

[@johnjamesjacoby Keymaster 7 years, 12 months ago]

I believe we fixed this in the 2.6 beta.

[@johnjamesjacoby Keymaster 7 years, 12 months ago]

We use that short code here, too, so it’s working OK for us. I’ll need to look into the links. Possible they moved to an action, or a different template part at some point.

@senatorman – do your database backup first, then swap from alpha to beta, then run the bottom three upgrade tools, for favorites and subscriptions (I forgot about forum subscriptions.)

[@johnjamesjacoby Keymaster 8 years ago]

* Do a database back-up however you’re comfortable
* Visit WP Admin > Tools > Forums
* Run the last 2 repair tools, one at a time, maybe from a beefier server if you have one available
* Confirm that your favorites & subscriptions work as expected

If something goes wrong:
* Restore your data from your back-up
* Go back to 2.6 alpha

—

Honestly, I’m being a little paranoid. The tools are fine. But… because hosting environments are so different everywhere, it’s hard to rule out any edge-cases ahead of time.

[@johnjamesjacoby Keymaster 8 years ago]

@senatorman If you have more than 10,000 users, you’ll need to manually run favorites & subscriptions migrations from someplace you are safe doing so. Otherwise, totally safe.

If you’re running a multisite installation with bbPress running on all of them, the upgrade routine will attempt to run on all of them, so there’s that too (though it’s a very unlikely situation.)

[@johnjamesjacoby Keymaster 8 years ago]

@senatorman The improvements here on bbPress.org were not-insignificant.

We have 25k topics, 100k replies, and many more in spam/trash/drafts/revisions, amounting to around 180k total posts.

It’s not a huge-huge install, but not exactly small either.

[@johnjamesjacoby Keymaster 8 years ago]

@reedy I’m here if you need help. Can also use the #bbpress channel in WordPress’s Slack instance.

[@johnjamesjacoby Keymaster 8 years ago]

Beta 2 is out to fix these embarrassing little oversights.

The upgrade tools can be ran manually by visiting: Tools > Forums (they are at the bottom)

On WordPress.org, I manually ran a custom, stripped down version of this same tool, but mostly because 8 million users is a lot to trust without some supervision.

[@johnjamesjacoby Keymaster 8 years ago]

> create the ability to have a topic relate to multiple Forums

bbPress currently requires that all topics have some parent forum, but you are not forced to expose this hierarchy in your theme/design if you’d rather not.

Custom taxonomies are the way to go, and there is a goal to eventually migrate the “Forum” post type to be a taxonomy instead, now that individual forums can have their own meta-data.

[@johnjamesjacoby Keymaster 8 years ago]

@reedy – If your install is experiencing slowness issues, I’d *love* it if there were a way for you to try the 2.6 beta. You are exactly the best person to be the most helpful, and confirm that our improvements actually make the same differences for others that we are seeing for ourselves.

Is there a way I can help you safely give it a try?

[@johnjamesjacoby Keymaster 8 years ago]

Hi there @iprg,

Sorry, but there isn’t yet. It wouldn’t be too difficult for us to implement this feature inside of wp-admin, though.

Are you comfortable creating a feature request over at https://bbpress.trac.wordpress.org? If so, that’s the best place to log this idea, and we’ll try and get it into a future release.

[@johnjamesjacoby Keymaster 8 years ago]

Related: https://core.trac.wordpress.org/ticket/39418

[@johnjamesjacoby Keymaster 8 years ago]

I think I understand the expectation here, but that isn’t how it’s currently designed to work.

More specifically, bbPress subscriptions do not discriminate against the user’s current role. If they were subscribed before, they’ll be subscribed until they unsubscribe.

To achieve the behavior you desire, a plugin could be written that either:

• Filters bbp_topic_subscription_user_ids and removes users with/out desired roles
• Filter bbp_set_user_role and permanently delete all subscriptions when the new role matches one that qualifies

Maybe a combination of both of the above, if you need to account for already removed users, but want to clean-up future role changes.

[@johnjamesjacoby Keymaster 8 years ago]

It’s still a nice idea, to be able to unsubscribe from all topics & forums.

I’ll make a note of this, and maybe we can get it into a future release.

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

🙌

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

Sorry about this, y’all. 2.5.12 is out now to fix this.

bbPress 2.5.12 – Requires WordPress 4.7

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

Can you try 2.5.12?

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

Sorry about this. 2.5.12 is out now to fix this.

bbPress 2.5.12 – Requires WordPress 4.7

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

Sorry about this, y’all. 2.5.12 is out now to fix this.

bbPress 2.5.12 – Requires WordPress 4.7

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

@mikehaceman – that was it.

See: https://bbpress.trac.wordpress.org/ticket/3026

Can you try what Netweb suggested again, and see if it works now?

[@johnjamesjacoby Keymaster 8 years, 1 month ago]

Hey @mikehaceman, sorry you are having trouble.

This isn’t usually necessary, but something between your two installations isn’t cooperating, and in these rare cases it unfortunately requires a bit of scrutiny.

WordPress installations since 4.4 and beyond will try to use utf8mb4 for their character set, and utf8mb4_unicode_ci for their collation. Traditionally these are InnoDB tables, but you’re usually free to decide this for yourself.

utf8mb4 tables have reduced maximum key lengths due to the additional bytes required for each character, so the safe maximum length is reduced to 191. It’s possible we haven’t updated our special converter table to handle this, so I’ll check, and update it if that’s the case.

If you wanted, it may be worth going through all databases, all tables, and all columns, and ensure that your encoding & collations are what you expect them to be. (This means in your old forums, and your new ones.)

[Edit: Updated this post to reflect what we’ve updated in bbPress’s converter]

[@johnjamesjacoby Keymaster 8 years, 9 months ago]

It’s actually much easier than this.

If you set words, phrases, or IP addresses in your Settings > Discussions of WordPress’s admin, bbPress will adhere. Whatever you use for WordPress comments, also works for bbPress topics & replies.

Hope that’s helpful!

[@johnjamesjacoby Keymaster 9 years, 2 months ago]

With every iteration, bbPress writes to the _bbp_converter_query option to record the last successful query. You can use that to cross-check what the converter is putting out against what the records are that are being imported.

Usually when this happens, it’s a database encoding issue, and MySQL is getting stuck on a specific character in a specific record.

To confirm if this is the case, you’ll want to go back into phpMyAdmin (or your favorite database management tool) and bisect that range of posts to identify exactly which post in your vBulletin installation that bbPress is getting hung up on.

For example, when I converted bbPress.org from bbPress 1.2 to bbPress 2.0, it got stuck on 8 individual posts that had had encoding issues from 10 years ago when someone changed the encoding from whatever it was to latin1, and because WordPress usually expected to be UTF-8 and we have HyperDB in the middle to route queries around, bbPress’s converter would do exactly what yours is doing.

If it’s database encoding or some other anomaly, isolating what is goofy with exactly which post(s) is the only way to get around it. I’m anxious to hear what you figure out here, and very happy to improve our importer if there’s anything we can do on our end.