I’m a little confused. The word “portal” is such an overloaded term that I’m having trouble seeing what bbPortal *does*.
Does it simply add a distinct front page to a bbPress install? Can it be used to supplement bbPress with freestanding pages under separate tabs? Or something else entirely?
I’ve looked back at other bbPortal posts, gone to bbportal.org, etc. and still don’t quite get it. Thanks for any light you can shed.
Some more data points. I’m running a brand-new 0.8.2.1 install with no plugins.
– When creating a new forum, declaring an existing forum to be its parent does not automatically position it in the hierarchy. I have to go through the “Edit Forum Order” process to drag it into place.
– New forums do not appear immediately in the “Forum parent” dropdown on the forum creation page, but if I go do other things and return, they get there eventually.
– Most troubling: When I post a new topic directly in a top-level forum, it does not appear there, but rather in the last of its subforums. That is, if I have forum A with subforums A1 and A2, forum B with subforums B1 and B2, and forum C, and I try to post a new topic to top-level forum B, it will actually get posted to subforum B2.
The last strikes me as a serious bug.
I don’t mind cutesy names that appear only behind the scenes, but since the role “Key Master” gets displayed to end users, it might be helpful if it were called something more intuitive. Users may grasp the Admin > Moderator > Member > Inactive > Blocked hierarchy, but probably not that there’s a Key Master who rules them all. “Superadmin,” maybe?
Just a suggestion. I guess as a workaround I’ll create a new Key Master account and downgrade my usual account to “Admin.”
Thanks for the above: in my first-time install of 0.8.2.1 I had set mod_rewrite to ‘true’, intending to get back to it, which resulted in a blank screen when I clicked on “Edit”.
[REDACTED: After the above fix I had a problem with some but not all views triggerng a download as type “PHP Document” rather than display as HTML. It must have been some sort of cacheing problem, as restarting Apache fixed it.]
