Forum Replies Created
-
In reply to: Fix for users of s2member and bbPress 2.2
Any idea why bbPress’s bbp_set_current_user_default_role() function isn’t working?
In reply to: Author MCE brokenThey are already aware of the issue; I have this fixed in the next version of Jetpack already. đ
bbPress purposely forces the editor into âteenyâ mode. You’ll need a plugin to change that, which is possible to filter out.
In reply to: php option valueMakes sense. Best of luck!
In reply to: Can't Post New TopicAre you using group forums, or do you want site wide forums?
In reply to: bbPress 2.2.1@rossagrant – it already tries to do that, via: Settings > Forums — Auto role —
âAutomatically assign default role to new, registered users upon visiting the site.â
Basically, that bit looks for users with no bbPress role, and automatically gives it to them (without interfering with existing WordPress roles.)
I think the problem comes from having modified the bbp_participant role previously in the database, and bbPress not using those modified caps any longer. (Just a guess.)
bbPress moved away from âeditable rolesâ in 2.2, since plugins like s2member and Members allow for manipulating bbPress’s roles in such a way that safe updates to bbPress are pretty much impossible; the moment we change our capability mapping, this all blows up.
Going forward, bbPress uses dynamic, secondary roles, that won’t interfere with any other capability or role on the site. I.E. a user can be a forum moderator and a blog editor, or a blog admin and and a forum participant, or no role on the blog, and a key master in the forums.
This type of setup is best for 95% of installations, but anyone that’s relying on roles in the DB are currently stuck (like we see here.)
One possible solution is to just let your database roles override bbPress’s dynamic roles. You can unhook most of those functions, but I don’t think that’s advisable for the long term, because you’ll lose any capability updates going forward, leaving some users in limbo when new features are introduced.
In reply to: Can't Post New TopicThe UI on BuddyPress’s end hasn’t been updated yet. If you have bbPress installed, and are using it to power your group forums, the BuddyPress forums component should be completely turned off.
It’s possible there’s an issue with BuddyPress 1.6 in this regard, but there wasn’t in my testing. I’ll take another look around.
In reply to: Author MCE brokenMaybe related to Jetpack 2.0. I’m not able to duplicate this issue with just WordPress and bbPress installed.
In reply to: bbPress 2.2: All forums now return "Page not found"Will there be a core solution for this with bbpress?
If its a bbPress bug, then yes. It’s likely an issue with bbPress using multiple user roles, and it being a foreign concept to most other plugins.
In reply to: php option valueCan’t tell if this is spam or not. It doesn’t sound like it has anything to do with bbPress.
There’s a plugin already; something to the effect of Advanced TinyMCE.
Easily enabled with a small plugin or filter. I’m sure someone can chime in with a solution here.
In reply to: bbPress 2.2: All forums now return "Page not found"Sounds like the problem is s2Member using set_role() which wipes out all roles a user might have.
Basically, s2member is not compatible with users having multiple roles.
Tried emailing you a few times, got bounced back.
In reply to: bbPress 2.2.1@rossagrant – Not yet, need to write something up soon though.
In reply to: bbPress 2.2: All forums now return "Page not found"There’s a topic in the S2Member forums that explains how to fix this. This is related to having customized roles and capabilities setup that bbPress isn’t looking in the database for any longer.
It probably sounds and feels counter-intuitive now, but the new roles and capabilities in bbPress 2.2 are actually intended to prevent these exact problems in the future. The forums roles and caps in bbPress 2.0 and 2.1 weren’t very cooperative, so everyone rolled their own.
Now that we’ve dialed it in, everything you’ve customized isn’t playing nicely anymore.
Unclear exactly what the *best* solution is for everyone, since every installation is different. Anyone want to volunteer to give me a peek into their installation and let me toy around?
In reply to: Close topic does not workNo. Will need much more information about your installation to help.
In reply to: New Topic button?- Make a new WordPress page.
- Use the bbp-topic-form shortcode.
- Done.
Who said you weren’t being helpful?
Much of it is the same. You’ll want to focus on:
- turning the BuddyPress forums component Off
- the bbPress 1.1 import tool
- the BuddyPress settings in: Settings > Forums
If you’re a super admin, you always have access to everything in a stock install. Some custom modification caused this to break.
Try:
- Update your permalinks.
- If you have custom roles and capabilities setup, revert back to normal.
They’re new in bbPress 2.2.
- Spectators can view the forum, but cannot contribute.
- Visitors are what you are before you become a participant. You have the same capabilities as a participant, but you haven’t participated yet.
Could probably remove/hide the Visitor role from display, since it’s not really useful for anyone to manually select it.
I don’t think this guide is 100% accurate anymore, so not worth keeping stuck until it’s corrected.
In reply to: Edit reply page does not load rightLooks like a CSS issue in your theme. Try display: block;’ing the main content div, or the wrapper around your content. Possible you have some other weird float/overflow CSS that’s causing this also.
In reply to: Why is integration so troublesome?If users show up as anonymous, and post_author’s are incorrect, then something was wrong with the migration script. You can try the Importer that comes with bbPress 2.2, but I’m not sure what “ImportForums” is to be much more helpful.
In reply to: bbpress not working nowNo database connectivity. I suspect something else besides bbPress is broken.
In reply to: bbPress 2.2.1Also, there is no bbPress 2.2.1 yet; it’s what comes next to address any bugs in 2.2.