I’ve a settled and happy little wordpress (version 2.02) community that I want to add a robust Forum software to.
Seeing as how WordPress.org recommends (and uses) bbPress, I thought I’d give it a go.
I’ve read through the (available) documentation <–that which I understood, and made changes to the “config.php” file as I believed all should be. I know I have something wrong, because I can’t seem to get the Forum to work with the WordPress installation I have.
My problems are less now than the first install (I keep going into the database and deleting all the ‘bb_’ instances before try to run the install each time (6 times now) – but I still have a few issues I can’t seem to put my finger on and would like to pick some brains – or be led down a truer path of enlightenment.
#1 – I am not a php programmer (an illustrator by trade) but pretty sharp so you don’t have to speak to far down to me =0)
#2 – I took the info for the top 3 lines of the “config.php” from my wordpress install. that is I left the ‘BBDB_Name’, ‘added my DB name’ left ‘BBDB_USER’, ‘added MySQL username’ and then the database password
#3 – the bbPress will reside within a “forums” directory inside directory named “cms” which is in the root of the site. I’m a mite confused about the blog and domain paths requested I thought I had them correct but everything lacked the WP template look (no css) and all the links for the “bbpress-integration.php” <-is this really a release plugin?), ahem…all of the links in the window this plug-in generates are two directories higher (on the root) instead of in the same directory as the forum.
(more on this in a bit)
This is what I have here:
// If your bbPress URL is http://bbpress.example.com/forums/ , the examples would be correct.
// Adjust the domain and path to suit your actual URL.
// Just the domain name; no directories or path. There should be no trailing slash here.
$bb->domain = ‘http://domain.com/cms/forums’; // Example: ‘http://bbpress.example.com’
// There should be both a leading and trailing slash here. ‘/’ is fine if the site is in root.
$bb->path = ‘/cms/forums/’; // Example: ‘/forums/’
respectively – and believe they are wrong – but unsure.
#4 – named the forum ‘forum name’ ; added my email address ‘firstname.lastname@example.org’; left pretty permalinks to false; topics to 30; edit-lock to 60; offset time zone -5; used my actual akismet key # (is that correct?) and then got to the serious stuff – the three items for integration with WordPress.
#5 – set
$bb->wp_table_prefix = true; // ‘wp_’; // WordPress table prefix.
$bb->wp_home = http://domain.com/cms; // WordPress – Options->General: Blog address (URL) // No trailing slash
$bb->wp_siteurl = http://domain.com/cms; // WordPress – Options->General: WordPress address (URL) // No trailing slash
And since this site isn’t loading WordPress with bbPress (being that WordPress is the primary site) I left that alone.
#6 – then I create a folder/directory in the ‘forum’ directory called “my-plugins” and add the “display-name.php” plug-in to it (it gets calls for error on line 15 which is “search”) everytime during config
I turn on the plug-in added to WordPress – (/cms/wp-content/templates/plugins) “bbpress-integration.php” (which opens immediately in “raw format” – even before I run the bbPress install.
But these two plugs are recommended for us non-techies – so I go with it.
#7 – run the config.php follow the link to Step 1 [and get the same page shown with the “bbpress-integration.php” plug-in (links wrong) at the top, at the bottom a path error on headers and then the regular “Step 1″ information to fill in.
Repeat for step 2
Finally, when it appears to be complete I have a login page that is without css (no template integration); links two levels up toward root than where the forum resides ‘domain.com/link’ instead of domain.com/cms/forums/link’
and not wp integration what-so-ever…none of the users/passwords are recognized (over 200) etc…
what, what, what in gods name am I doing wrong?
thanks for any insight in advance…..
You must be logged in to reply to this topic.