If you have the latest version of bbpress (.8.3), you need to activate the plugin that allows images.
Hi,
I’m trying to add a new custom page to my forum. It’s very simple, this is what I have so far:
– 1 custom page called test.php
– the page includes the forum header and footer
– The content (middle) part is pulled from the db aswell
All works fine except hyperlinks! Links like http://www.test.com will NOT appear as a hyperlink, but just as plain text. How to fix this? I want this to behave just like this textfield I am typing in right now (auto hyperlink converting).
bbcodes like bold do work.
_Null
I only tested one case, the dollar sign ‘$’ on my testing forum with commenting out the entire function bb_user_sanitize except last line. I can register with ‘$’ in username, post with that account and the username is showed correctly.
Hi,
Here is a quick php for it(Use this method at your own risk), you need pretty permalink to use it.
Save the following code in bbPress root folder as page.php
<?php
require_once('./bb-load.php');
if (preg_match('/.*/page/(.*)/', $_SERVER['REQUEST_URI'], $matches)) {
$file = bb_slug_sanitize($matches[1]) . '.php';
if (file_exists(bb_get_active_theme_folder() . "/static/$file")) {
bb_load_template("static/" . $file);
exit(0);
}
}
wp_redirect(bb_get_option('uri'));
?>
Put your static pages in a new static folder under your template folder, they should looks like
<?php bb_get_header(); ?>
The static content here.
<?php bb_get_footer(); ?>
Then you can access a static file. For example, access test.php(bb-templates/yourtemplate/static/test.php) at http://yoursite.com/bbpress/page/test
Remember: Use this method at your own risk
I am trying to integrate bbPress with WordPress. I installed it on my local test environment first, in order to work out any kinks. bbPress is in the same database as WordPress. The installation went fine, it seemed, and I ended up with a basic version of bbPress — left-aligned black font on a plain white background. Is this what I am supposed to see?
However, when I tried to point it to WordPress, using “require_once(‘http://localhost:8888/wordpress/wp-blog-header.php’);” in the config.php file, I only got a blank screen. Any idea what I’m doing wrong?
I sort of fumble my way through all this web design stuff, so there is a good chance the answer is painfully easy, but I can’t seem to find it. Thanks.
The previous version of this plugin. That’s version μ instead of the latest, ν.
Awesome. OK, so I removed the entry from the database and I was able to login like normal.
Then I went back and created a new post again to test if it would create a new topic in bbpress. No new topic. And it wouldn’t let me login to the backend again.
So I went back and removed the capabilites entry from the database.
I can create topics no problem in bbpress. Just doesn’t create new topics when I write posts.
Gostallion, got the latest bb?
I’m using the latest version of bbsync.
Now I can’t login to the bbpress backend. It’s like it doesn’t recognize the roles anymore. I can login and view my profile and such, but can’t get into the backend.
I am using 0.8.3 I upgraded the same day it came out and everything works great, I am very happy with everything, but this is so weird. Like you said their is something bad about this post.
I am running the forum in bluehost.com as far as I know they are pretty good at keeping up to date with their upgrades so I am sure they have all their software up to date.
I was installing PM to the forum when I notice the error so I deleted all the changes and deactivate the plugin to check if that was the problem but it turn out that even without the plugin the error keep coming up.
Maybe I just found a bug on the latest version but I don’t know anything about coding so this is up to you guys.
Slex, indeed there’s some issue there. It probably needs further thinking about. However, like I said if you want to modify it to stop wp saving comments, or even to make bb add replies to wp comments, implement the change and I would definitely like to make a branch of bbsync.
Vito, can you please open bb’s config.php file and add this line to it somewhere?
global $bb_cache;
That should fix that error (assuming you’re using the latest stable, .8.3!).
No good news on making backdated topics I’m afraid, because there’s no way to use the API to create the topic and set the time of it to be in the past. You’d have to copy and modify some large blocks of code, which is exactly what I want to avoid with bbsync (regarding the problem that became with bbpress post, for example).
However, if you edit an old post in wp and press save, it will create a new topic in bb for you (but with today’s date, rather than the appropriate one). It’s an unfortunate limitation of bbsync.
I’ve looked through the (two) plugins that allows us to restrict forums, and sadly, it seems your guesses are correct. The first one which allows you to allow users in to a forum based on member names is hardly compatible with the latest version of bbPress (and seems dead). I almost got it working right, except for the fact that it messed up my forum hierarchy, and some other bugs, which meant that threads couldn’t be posted to a certain forum without being in that forum, which was enough for me to rule it out.
The other option, private forum as you tried out yourself, doesn’t allow us to do anything but restrict it to either members, mods or admins, which is the most viable solution to me at this point. It does mean however that I will need to give all my members who need access to the restricted forum moderator capabilities. Hardly ideal, but I’ll have to go with it for now.
I’ll be looking at it this weekend though, and hopefully I can find a sort of solution to it. Right now I’m thinking of finding a way to strip moderators of actual moderating powers, but I really don’t know. Adding another usergroup (pretty simple) should work too, but it has to be reflected in the plugin as well, but I don’t have the coding skills (I don’t have any coding skills) to do that.
Hopefully a gifted plugin developer will step in and solve this for us 
Tested. Works. Good job Jaz… now I dont have to wonder how many months from now my hack would have caused a nuclear war in china.
And just for the sake of completeness. I did not test the case where a user is a blog writer (can write new posts), but is not some sort of administrator on the forum. I can’t foresee needing this functionality, but if it doesnt work, dont get mad at me.
Database redundancy time?
Yeah, I think that did it. I just tested a post as a regular user and it worked without any errors. I am short on time right now so if anyone else has a chance to try it out, that’d be cool. Here’s all I did (all in felsyncpost()):
1) added $bb_current_user to the globals
2) commented out line 36
3) added $bb_current_user = $current_user; in its place.
Try it out.
Strange that it’s not catching if it’s a BB_User. That does seem to be the actual class name. Do you want to do some more testing on that? Are users usually instantiated as wp_User if it’s integrated? Or is it just if you set up the current user as bbSync does, from wp, that you get the user as a wp_User object? It’s up to you, if you could check that and arising questions out I’d be grateful as I’m all over the place right now.
Thanks for your post, really! I feel a lot more confident about finding the solution now.
The fix that I made to that function has been tested now and it seems to work, but the fact of the matter is that it could have very well just broke that function all together. I think everything works to my satisfaction now though, so I probably wont worry about it until I run into some more problems. The only thing that gives me hope in that respect is that previously, that if statement was failing. meaning that the user was not a bb_user:
if ( !( is_object($user) && is_a($user, 'BB_User') ) )
so it would create new capabilities for the user (incorrectly at that). But when I changed it to wp_User, for some reason that if statement catches and just returns without creating the new capabilities that break access permissions. I don’t know why this works after looking into the code, but until I see negative side effects, I might turn a shy eye (<— i dont think thats a real saying…).
Also, on the topic of redundant database entries, I think since we have the integration set up from the WP comment box, it wouldnt be incredibly difficult to simply take out the one database call (somewhere in the wordpress code never-never-land) that actually posts the comment to the database. So we’re not inputting a box from bbpress, but we would effectively stop wordpress comments from being saved to the database since we never actually look at them. This of course wouldn’t work if you were merely copying database entries in order to post the comments as posts in bbPress, but I dont think thats what you’re doing. It probably is two separate database INSERT calls, and I bet we can take the wordpress one out, and have identical functionality (assuming we took out wordpress comments and exclusively use felbbreplies()). It’s merely an optimization though, and unless the user base is larger than any of us probably are going to have it might not matter… I’ll look into it tonight when I get home, and let you know.
sorry for the long post
-Alex
This has been scarcely tested, but I think I have a fix for my bug… weird…
in the bb-includes/capabilities.php file there is a function at the bottom that looks like this:
function bb_give_user_default_role( $user ) {
if ( !( is_object($user) && is_a($user, 'BB_User') ) )
return;
$user->set_role('member');
}
I changed it to look like this:
function bb_give_user_default_role( $user ) {
if ( !( is_object($user) && is_a($user, 'wp_User') ) )
return;
$user->set_role('member');
}
Instead of checking to see if the bb_user existed, we wanted to check to see if the wordpress user existed, assuming we merged our user table. For some reason, this seems like a bug in the bbPress code. Shouldn’t that be a variable prefix to begin with?
Just installed bbPress, and experiencing the exact same problem. Normal installation of WP 2.3 (latest version). No clue what might be wrong either.
Making another user KeyMaster works however. So as a workaround I’ve registered a “dummy” to use for this only. Awesome.
Edit: It turns out my “normal” account doesn’t have permission to edit tags either.
As mdawaffe mentioned, it was untested. As well, there have been core changes since, so somebody would have to ‘debug’ that little plugin. Anyone notice anything off the cuff on why it doesn’t work?
Trent
When I try to activate Akismet in my site admin>plugins panel I get this error:
Plugin could not be activated; it produced a Fatal Error.
But then I notice that there IS an Akismet Spam tab in my content panel–and it’s blocking posts from normal users and marking people as Bozos. What the heck? Am I doing something wrong or is Akismet incompatible with the latest release? Ahhh! Frustrating!
Did you copy all of the rules?
You should have copied all of these rules:
/* Default table structure
=================================== */
/* 100% is a good starting width for most tables - this is a forum! */
table { width: 100% }
/* Login form (header.php)
=================================== */
.login {
}
.login p {
}
.login label {
}
.login #submit {
}
p.login {
}
form.login input {
}
/* Breadcrumbs (most templates)
=================================== */
.bbcrumb {
}
/* Notice (profile.php)
=================================== */
.notice {
}
.notice p {
}
/* Front Page
=================================== */
#front-page #hottags {
}
#front-page #discussions {
}
/* hot tags! */
.frontpageheatmap {
}
#front-page #main h2, #forum-page #main h2, h2.post-form, #userlogin, #currentfavorites, #register {
}
#front-page #discussions ul {
}
.sticky {
background-color: #ffffd0;
}
/* Topic Page (topic.php)
=================================== */
/* wrapper for topic */
.infobox {
border-top: 1px solid #eeeeee;
border-bottom: 1px solid #eeeeee;
}
ul.topicmeta {
display: block;
margin-left 1.0; padding-left: 0em;
}
.topicmeta li {
display: list-item;
list-style: square inside;
}
#topic-info h2 {
border: 0px;
margin: 0px;
}
#topic-info {
float: left;
}
#topic-tags {
top: 1.0em;
margin-top: 2.0em;
float: right;
}
/* .nav used by topic.php & tag-single.php */
.nav {
}
.nav span {
}
.nav span, .nav a {
}
#thread {
}
#thread li {
margin-bottom: 1.0em;
}
#thread li ol, #thread li ul {
}
#thread li ol li, #thread li ul li {
}
/* following are used by post.php */
.threadauthor {
margin-left: -0px;
overflow: hidden;
width: 115px;
position: absolute;
}
.threadpost {
margin-left: 130px;
width: 370px;
background-color: #f5f5f5;
padding: 10px;
}
.poststuff {
font-size: 0.8em;
border-top: 1px solid #e5e5e5;
}
.num, #forumlist small {
}
.postform {
background: #f0f0f0;
padding: 1em;
margin-bottom: 1em;
}
.postform textarea {
height: 12em;
margin: 5px 0;
padding: 5px;
width: 96%;
display: block;
}
.postform label { display: block; }
.rssfeed { line-height: 20px; padding-left: 23px; background: url( "images/feed-icon-16x16.png" ) center left no-repeat; }
#manage-tags {
}
#manage-tags li {
}
.submit {
}
.topiclink {
}
.topictitle {
}
#topic-move {
margin-bottom: 1.0em;
}
/* Content - specific to the main content div
=================================== */
#content .frontpageheatmap a {
}
#content .infobox li {
}
#content .nav a {
}
#content .nav a:hover {
}
#content a:visited {
}
/* Profile Page
=================================== */
#profile-menu {
padding-top: 0.5em;
list-style: none;
border-bottom: 2px solid #ccc;
}
#profile-menu ul {
}
#profile-menu li {
font-size: 1.1em;
background-color: #eee;
padding: 4px 7px;
margin: 0px;
display: inline;
position: relative;
top: -3px;
}
#profile-menu li.current {
background-color: #ccc;
}
#userinfo {
}
#userinfo dt {
}
#userinfo dd {
}
#useractivity {
}
.user-recent {
}
.user-recent .alt {
background-color: transparent;
}
.user-recent ol {
}
.user-recent ol li {
}
/* Profile Edit
=================================== */
fieldset {
}
legend {
}
fieldset table {
}
fieldset table td {
}
fieldset p {
}
/* Other
=================================== */
#front-search {
}
#latest td, #forumlist td, #favorites td {
border: 1px solid #f5f5f5;
}
#forumlist tr td div.nest {
}
#latest tr:hover, #forumlist tr:hover, #favorites tr:hover {
}
#latest th, #forumlist th, #favorites th {
background-color: #e9ede8;
border: 1px solid #f5f5f5;
}
#latest, #forumlist, #favorites {
}
.alt {
background-color: #f9f9f9;
}
.bozo {
}
.alt.bozo {
}
.deleted {
}
.alt.deleted {
}
I’ve tested it with a user that has moderator permissions, and he can delete posts and add tags just fine.
So it does, indeed, seem to be a keyholder/admin problem.
It seems to be a user thing. I’d been posting from a user that’d been established in WordPress. I updated it to Key Master in bbPress, so it should have all powers. But I found that, apart from tags, I couldn’t delete a post either, same no permission message (same as noted by Jolaedana above). So I logged out and logged in as Superadmin, the default account from bbPress installation, and voila, I can do everything, add tags, delete posts.
That doesn’t solve the problem. I haven’t tested to see what happens with other users, both already registered from WP and registered through bbPress. But it’s a workaround for me, and a…clue.
I’m currently editing the default theme template for the latest version. Everything is going well, except I can’t find the code reference for the “Reply” label (it shows up as <h2 class='post-form'>Reply</h2> in the HTML output. The rest of this section is editable in post-form.php. Where do I need to look to find the section (basically I just want to either remove this label and add a new one separately, or else be able to wrap some more code around it). The only other thing which may shed some light on this is the preceeding code: do_action( 'post_form_pre_post' ); but I have no idea what this function does.
I’ve just posted some updates. See this post on my site.
I will tidy up the downloads page so you can still get to old versions. For now you can only access links to the latest themes.
