[timsilva_]

@leonstafford Thanks for stepping in and offering advice! I really appreciate it. I will take a look at HTTrack first. 🙂

[timsilva_]

Thanks for the reply Robin =) When/if I get some time to try WP2Static I’ll report back how well it worked.

[timsilva_]

It would be awesome for Matt find another engineer to support bbPress, I know the team is spread pretty thin. v2.6 feels like it may never come. =(

[timsilva_]

*Bump. Just curious if anyone saw this, the issue seems to still be there. =)

[timsilva_]

There haven’t been any active tickets on v2.6 for several weeks, do you guys think that its ready to be released?

[timsilva_]

Thank you for fixing those download links Pascal 🙂

[timsilva_]

Hi @johnjamesjacoby and team. Like everyone else, I’ve been waiting for the 2.6 release for a few years now. I can see that the last remaining ticket is for the “bump” functions that have been in there for a while.

I’m just curious, are bump functions uniquely challenging to code? Either way, is there anything that I (or anyone) can do to help get this task finished? I have somewhat arbitrarily been waiting for the 2.6 release to make some changes to my site. I’m contemplating updating to the RC5 release. By the way, where can I find the latest RC download link? I dug around but couldn’t find a copy. The RC5 link here (https://wordpress.org/plugins/bbpress/advanced/) is still broken.

[timsilva_]

Robin, just wanted to drop in and say that you rock! I’ve seen you and other donate tons of time to this place and ironically, I wish bbPress[.org] had a like/reaction feature so that I (and probably many others) could passively support your posts haha.

@paladinbrewer – I also wish that some of these features were built in, but I appreciate elements of how it works as well. Where stacking plugins get complicated is with conflicts; every so often you’ll find two plugins/features that you need, and one of them breaks the other one somehow. Free and open-source software has its pros and cons. 😉

[timsilva_]

Sweet! Thanks so much for contributing so many of these essential plugins for the community. You rock. 🙂

[timsilva_]

@michaelachung This is an excellent plugin that has a list/counter of online users: https://wordpress.org/plugins/bbpress-improved-statistics-users-online/

[timsilva_]

Related to this question: Is there a more advanced member’s list. Most forums (and I realize that the BuddyPress feature isn’t like a forum) have a user list where you can see loads of data like number of forum posts, join date, last active, etc that you can sort by with pagination and so on. The BuddyPress list is super basic, painfully limited even. Is there any good plugin that makes that page more useful?

I am aware of the Members loop, but I’d rather have a thoughtfully crafted option if one exists rather than attempt something custom. Just curious. 🙂

[timsilva_]

The @mention feature must be turned on in BuddyPress first. Go into the the BuddyPress Settings in WP Admin, and make sure that “Activity Streams” is checked. Mentions only popup after you begin to type at least one letter. So “@a” will bring up “@alex”, “@amy”, etc… Just typing “@” by itself shouldn’t trigger the suggestions popup. If you are doing all of this correctly, there might be something else causing it to not work.

[timsilva_]

I’ve had that trac page bookmarked for over a year, so happy to see it’s almost done. 😀 Congrats to the team for all the hard work, looking forward to testing this out.

[timsilva_]

I was considering Tapatalk for bbPress (after migrating from SMF which has Tapatalk support) a while back in an effort to compete with Slack.

I did bookmark this URL: https://tapatalk.com/download_bbpress.php – but it is no longer active, it just redirects. Here is the archive.org version: https://web-beta.archive.org/web/20150911232515/https://tapatalk.com/download_bbpress.php

There also was this plugin, but I haven’t tested it or confirmed that it is actually meant for bbPress specifically (it looks like it is for blog comments): https://wordpress.org/plugins/tapatalk/

If anyone is currently using Tapatalk with bbPress, let us know how. 🙂

[timsilva_]

I have wondered this myself, nice to see that these themes are publicly available. 🙂

[timsilva_]

I dealt with some of these issues about a year ago. I was migrating from SMF 2* to bbPress and I had tons of issues with formatting in posts and missing data. I ended up hiring Michael Z Noble (http://wwww.michaelznoble.com/ – The 4 w’s is intentional 😉 ) to write a custom migration script to help me through all of these issues (as well as transfer a bunch of data like signatures, up/down votes, thread view counts, avatars, etc, into various bbPress/BuddyPress plugins/functions). The utf8mb4/utf8mb4_unicode_ci/character set issues were particularly tough for me to get through. I ended up switching to a new host that had a newer version of MySQL in order to successfully complete the migration. In short, if you aren’t a senior dev, hire a dev. 😉

Best of luck my friend! 🙂

[timsilva_]

Thanks so much for the detailed instructions Robin!

I was able to make that edit in a separate installation and I can see the value being updated in the database each time I load a topic on a certain page. I have been clicking around to various pages and topics trying to understand the patterns, and I think it might have something to do with the custom migration work that I had done.

One of the issues with the build-in SMF to bbPress importers had to do with posts that were created by users on SMF who later deleted their own accounts. After a handful of users did this on SMF, their old posts were still visible, but their usernames/display names wouldn’t link to their SMF profile page since it no longer existed. After I migrated my SMF site, these types of posts (the ones created by users that no longer existed) were all automatically attributed to the first WordPress user ID. The end result was a bunch of old posts from deleted accounts that looked like they were created by the admin account on my WordPress installation. So I hired a developer to transfer the old post author’s metadata over, along with some other data.

Anyways, I suspect that the posts by users who deleted their accounts are possibly not being counted as posts which is causing the pagination calculations to break. So I am showing 15 replies per page, and if 1 of those posts is by a deleted account, I think it is counting 14 instead. I’m not sure if this is correct, but it seems plausible. The more I click around to different threads, the less consistent this explanation seems to be.

But I am not seeing 1 or 0 for the faulty topics.

In newly created topics with pagination, the counting is much clearer. The value is 14 for the first page (subtracting 1 from 15 since the original post doesn’t count as a reply), and then page 2 is 29, page 3 is 44, page 4 is 59, page 5 is 74, and page 6, which only has 4 replies, is 78. This makes sense with 79 total (if you include the original post as a reply).

…30 minutes later…

After some more digging around, I have noticed that the count seems to have started over from 1 in the topics that have had new replies after the migration. So if a topic had 10 pages (let’s say 144 replies, not including the original post) before the migration, and then someone replied to the topic (which would be reply #145), the $reply_position would be 1. Another reply would make it 2, and so on…

So that appears to be the pattern. I did find and verify that at least one thread that was migrated with 702 replies (excluding the first post) is still working after it was responded to once after the migration, although I wouldn’t be surprised if another reply could cause the bug to come back.

It sounds like I will eventually have to repair the reply counts or something along those lines. :/ I’m gonna have my developer take a look as soon as he can, this info is really great to know!

[timsilva_]

Sorry for all of the replies, I am finding new leads to the root of the problem.

In both loop-single-reply.php and loop-search-reply.php, the bbp_reply_url function seems to also be outputting URLs without the pagination bits. I have been trying to dig in to the functions, but I’m way out of my league. I found on line 487 of includes/replies/template.php where the $reply_page variable seems to be calculating the pagination for a link, but I don’t know where to begin debugging with it. I also looked at bbp_get_reply_permalink and a few other functions, didn’t see anything obvious.

[timsilva_]

Hmm, I also just noticed that some topics from the migrated database with only a few pages (4 pages in the one I just tested) don’t seem to have this issue.

I designed some the forum topics to be long, ongoing threads. For example, we have a “Music” thread that currently has 7,674 replies (15 per page, so 512 pages total). Could the issue simply be that the thread is so large, that bbPress somehow doesn’t do the calculation?

I have read in some support threads about issues with pagination on bbPress when dealing with large numbers, perhaps it is related to that?

Some additional details that may be related: I have nested replies turned off (and they were never turned on). Also, all of my categories are set to hidden.

[timsilva_]

@robin-w I do have access to phpmyadmin. I have been looking around, and the only thing that looks fishy is that the “guid” varchar(255) row has my old local environment in the URL instead of my live domain. So it is http://localhost/forum/topic/title/ when it should be http://example.com/forum/topic/title/ – But after I tried to correct that for the post and the postmeta of the thread’s latest reply (in a safe environment) it didn’t seem to fix the problem. I did notice that my old local URL was hardcoded over 220,000 times in my database though, I wonder if this is something that needs to be corrected for each topic/reply.

I tried to get creative by changing the “Replies Per Page” in wp-admin > Settings > Forums to a different number. That successfully recalculated the correct number of pages required for the non-affected threads (I set it from 15 replies per page to 30 replies per page, so a thread with 10 pages was updated with 5 pages, and the latest reply link updated to point to page 5), but the affected threads still have no “/page/##/” segment in the URL.

[timsilva_]

So I went ahead and decided to launch my site with this bug still present.

I have been trying to isolate the cause of this issue, and I think I have found some common traits about the threads it seems to affect. It seems that only the threads that were migrated from my previous forum (SMF) that have been replied to after the migration are missing the “/page/##/” piece of the URL. So newly created threads always have the “/page/##/” piece of the URL, and old threads from before the migration that haven’t been replied to since the migration to bbPress also always have the correct URLs being generated.

I have tried running all of the repair tasks that should be related, but none of them seem to make any difference.

Does this sound like anything anyone has experiences with the bbp_topic_freshness_link() function?

[timsilva_]

Hi Pascal, thanks a lot for the response, I appreciate your time. 🙂

I should have mentioned that I am all up to date with WP 4.4.2.

Here are some screenshots of the issue:

As you can see in the first image, the /page/#/ part is missing when it should be /page/103/.

Shortly after making these screenshots, I clicked on the “10 hours ago” link, and it returned me to the first post on the first page of the “Gaming” topic even though the URL loaded still has “/gaming/#post-683963” in it. In a few instanced where the /page/#/ part is missing, I have been able to click on the link and land on the correct page anyways. Still haven’t found a logical pattern, I will keep digging to try to identify it.

I will soon look to see if I can replicate the issue from a fresh install. I tried turning off all plugins (except bbPress + BuddyPress) with no luck.

[timsilva_]

@netweb – Great point, bump would make sense as a paired featured.

@casiepa – Exactly right. Here is the most direct explanation of the feature from the article I posted above.

…force the discussion to sink down the list naturally by changing that particular discussion to no longer update it’s “Date of Last Comment” field as new comments are added.

So yes, the date of the current last reply would remain fixed on the last reply at the time that an admin/moderator sets the topic into sink mode. Once set to sink, it would also be ideal for an admin/moderator to be able to “unsink” the topic which would return the frozen current last reply to the true last reply.

The bumping feature may have a complex relationship in some cases as you would most likely want to disable the action on sunken and closed topics.

I would be happy to contribute a plugin if I had the skills. I’m still fairly new to coding anything that works directly with the backend. It’s great to know that the feature isn’t there yet though, I appreciate the confirmation and interest in the idea. 🙂

[timsilva_]

@gptxffa – They are still working on making sure the solution is rock solid, but it will eventually be in a normal WP update.

In the meantime, all you have to do is follow the instructions from the diff patch. Basically, open wp-includes/post.php, scroll to line 4303, and replace:

if ( 'publish' === $parent->post_status ) {

with

if ( 'trash' !== $parent->post_status ) {

So you replace the red tinted line of code with the green. 😉

[timsilva_]

Thanks @tharsheblows! That patch fixed the problem. Cheers! 🙂