The size of the codebase is largely due to the amount of phpDoc and inline documentation. I expected there to be a lot of eyes on this code from both bbPress and WordPress audiences, so almost everything is described in detail.
And I certainly appreciate it, but is there an easy way to minify it then?
The query count is high and needs and audit. We’re using internal WP functions for 99% of queries, so we thoroughly reap the benefit of the WP object cache.
The size of the codebase is largely due to the amount of phpDoc and inline documentation. I expected there to be a lot of eyes on this code from both bbPress and WordPress audiences, so almost everything is described in detail.
@Gautam 15? Simply brilliant! If only I could breath code like you do.
Unfortunately, I just break, test and report things and that’s all.
Okay, I told you that I would bring you in more info if I had it. I got it!
If you do not have any salts in your wp-config.php file, then you can create keys and salts at this link:
-WordPress.org secret-key service-
https://api.wordpress.org/secret-key/1.1/salt/
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
To do a proper integration you will need keys and salts, so generate them all at this proper link.
Remember to add a ‘BB_’ prefix to each key and salt in the bb-config.php.(Example: ‘BB_AUTH_KEY’ or ‘BB_SECURE_AUTH_SALT’)
Miscellaneous info:
If you only need keys, then use this link:
https://api.wordpress.org/secret-key/1.1/
If you only need keys for bbpress then use this link:
https://api.wordpress.org/secret-key/1.1/bbpress/
For bbpress keys and salts use this link:
https://api.wordpress.org/secret-key/1.1/bbpress/salt
Okay, I told you that I would bring you in more info if I had it. I got it!
If you do not have any salts in your wp-config.php file, then you can create keys and salts at this link:
-WordPress.org secret-key service-
https://api.wordpress.org/secret-key/1.1/salt/
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
To do a proper integration you will need keys and salts, so generate them all at this proper link.
Remember to add a ‘BB_’ prefix to each key and salt in the bb-config.php.(Example: ‘BB_AUTH_KEY’ or ‘BB_SECURE_AUTH_SALT’)
Miscellaneous info:
If you only need keys, then use this link:
https://api.wordpress.org/secret-key/1.1/
If you only need keys for bbpress then use this link:
https://api.wordpress.org/secret-key/1.1/bbpress/
For bbpress keys and salts use this link:
https://api.wordpress.org/secret-key/1.1/bbpress/salt
Okay, I see what was missed.
1. I had to copy/paste all of the keys and salts from wp-config.php and replace the keys in bb-config.php. (Though the bb-config.php has only keys, you still must copy the KEYS & SALTS from the wp-config.php and add ALL to the bb-config.php.)
2. Then I had to add ‘BB_’ before each key or salt in the bb-config.php file. (Should look like this… ‘BB_AUTH_KEY’ or ‘BB_SECURE_AUTH_SALT’)
This made my logins seamless. If I have anymore info, then I will add it to this topic later.
I did all the other stuff first such as:
a. adding the bbpress integration plugin to my wordpress
b. updating the wordpress integration ‘user rolemaps’ in the bbpress backoffice
c. adding the manual cookie setting [define( ‘COOKIEPATH’, ‘/’ );] from the wordpress bbpress integration plugin to the wp-config.php file
Other info to know:
My blog is http://gerlainetalk.com
I put the forum in the same folder and not under a different domain.
http://gerlainetalk.com/forum
My lessons:
I find that having the forum in a different domain, botches things up. Such as http://forum.gerlainetalk.com
http://gerlainetalk.com/forum works much better.
Okay, I see what was missed.
1. I had to copy/paste all of the keys and salts from wp-config.php and replace the keys in bb-config.php. (Though the bb-config.php has only keys, you still must copy the KEYS & SALTS from the wp-config.php and add ALL to the bb-config.php.)
2. Then I had to add ‘BB_’ before each key or salt in the bb-config.php file. (Should look like this… ‘BB_AUTH_KEY’ or ‘BB_SECURE_AUTH_SALT’)
This made my logins seamless. If I have anymore info, then I will add it to this topic later.
I did all the other stuff first such as:
a. adding the bbpress integration plugin to my wordpress
b. updating the wordpress integration ‘user rolemaps’ in the bbpress backoffice
c. adding the manual cookie setting [define( ‘COOKIEPATH’, ‘/’ );] from the wordpress bbpress integration plugin to the wp-config.php file
Other info to know:
My blog is http://gerlainetalk.com
I put the forum in the same folder and not under a different domain.
http://gerlainetalk.com/forum
My lessons:
I find that having the forum in a different domain, botches things up. Such as http://forum.gerlainetalk.com
http://gerlainetalk.com/forum works much better.
OK. Happy to test. How do I contact you?
I am still in the finishing stages of finishing mine up and always do need testing databases to make sure it works fine.
Do contact me if you would like to help me test it as I would like to test the converter on just more then my original IP.Board and default installations.
I have taken all of the integration and deep integration steps. I have even went to a few blogs and taken the extra steps.
I can only log into one of my sites at a time. If I log into wordpress, then I am logged out of bbpress and vice versa.
I have seen others post this forum, but there has been no answers to satisfy my problem.
I have made sure that all of the information in bb-config.php and wp-config.php were matching.
I’m so stumped.
What can be done to prevent this? It’s not a good advertisement for bbPress. One of the main problems with all the other forum software is their inability to tackle spam. WIth Akismet we should have a significant advantage.
I don’t know a lot about Akismet, but in this case I feel it should overlook the fact people are registered. A lot of this is blatant spam that I’d be surprised to see get past Akismet protection on blog comments. It’s like it’s giving registered people a free pass to post whatever they like – why should it let someone post 10 topics in a row? You can guarantee this is not legitimate posting behaviour.
What can be done to prevent this? It’s not a good advertisement for bbPress. One of the main problems with all the other forum software is their inability to tackle spam. WIth Akismet we should have a significant advantage.
I don’t know a lot about Akismet, but in this case I feel it should overlook the fact people are registered. A lot of this is blatant spam that I’d be surprised to see get past Akismet protection on blog comments. It’s like it’s giving registered people a free pass to post whatever they like – why should it let someone post 10 topics in a row? You can guarantee this is not legitimate posting behaviour.
Most certainly agree Gautam, you are accomplishing a lot for your young age, your future prospects should be very good indeed!
@Chip Bennett
Thank you! One major thing that has changed is the prefix of the functions. Instead of bb_, it is bbp_. The functions names are easy to guess like bbp_forum_title, bbp_topic_title, bbp_topic_reply_count etc. We don’t have post – that has been split into topic and reply. Though post is used to refer to topic and reply both in some functions like bbp_fix_post_author(), but that’s a couple of functions only. Like the standalone, WP, BP, etc there are 2 versions of the same function – one that echoes and one that returns so you’d have bbp_topic_content, bbp_get_topic_content etc.
Right, there is a great need for the documentation. We’ve tried our best to have upto date inline documentation (phpDocs) in place.
@Chip Bennett
Thank you! One major thing that has changed is the prefix of the functions. Instead of bb_, it is bbp_. The functions names are easy to guess like bbp_forum_title, bbp_topic_title, bbp_topic_reply_count etc. We don’t have post – that has been split into topic and reply. Though post is used to refer to topic and reply both in some functions like bbp_fix_post_author(), but that’s a couple of functions only. Like the standalone, WP, BP, etc there are 2 versions of the same function – one that echoes and one that returns so you’d have bbp_topic_content, bbp_get_topic_content etc.
Right, there is a great need for the documentation. We’ve tried our best to have upto date inline documentation (phpDocs) in place.
hello thors1982,
Make sure the following are on your bb-config.php and not only in the bbpress admin panel :
BB_AUTH_KEY, BB_SECURE_AUTH_KEY, BB_LOGGED_IN_KEY, BB_NONCE_KEY
I added only the line below to my wp-config.php (no lines added to bb-config.php)
define( ‘COOKIEPATH’, ‘/’ );
hope it helped
hello thors1982,
Make sure the following are on your bb-config.php and not only in the bbpress admin panel :
BB_AUTH_KEY, BB_SECURE_AUTH_KEY, BB_LOGGED_IN_KEY, BB_NONCE_KEY
I added only the line below to my wp-config.php (no lines added to bb-config.php)
define( ‘COOKIEPATH’, ‘/’ );
hope it helped
And these popped up in mine – http://gaut.am/2011-a-new-kind-of-forum-software-is-born/comment-page-1/#comment-2667
[2791] [2792] 
Edit: Oh.. I read the rest of your comment later..
Well, yes the query count has gone up, there would have to be an optimization round.
Thanks for the age comment, though! 
these popped up in my alerts:
bbPress plugin project saw serious progress during Google Code-in
2011: A New Kind of Forum Software is Born
It’s a shame that topic split/merge had to wait until the plugin version to be done in the API and not in the previous few years for the standalone.
Neither of the writeups mention the impact of database queries and the size of the codebase so I will have to explore that next week. I suspect they are high. It’s easy to pile on features but hard to make them efficient.
ps. Gautam is only 15 ?! Wow, amazing work for such a young age.
Thanks for the update, John and Gautam!
As I am anxious to convert my existing stand-alone bbPress installation to the new WP-plugin version, I expect to start testing (and porting over my existing bbPress Theme) once the Plugin hits beta.
I’m curious about template tags, functions, and documentation. Are the existing template tags and functions from the stand-alone version used in the Plugin version, or have you developed all-new tags/functions?
Also, as I remember, part of the biggest problem with the stand-alone version was the lack of documentation. So (in all my free time…) I’ll do what I can to pitch in for documentation with the Plugin version.
Thanks for the update, John and Gautam!
As I am anxious to convert my existing stand-alone bbPress installation to the new WP-plugin version, I expect to start testing (and porting over my existing bbPress Theme) once the Plugin hits beta.
I’m curious about template tags, functions, and documentation. Are the existing template tags and functions from the stand-alone version used in the Plugin version, or have you developed all-new tags/functions?
Also, as I remember, part of the biggest problem with the stand-alone version was the lack of documentation. So (in all my free time…) I’ll do what I can to pitch in for documentation with the Plugin version.
As a sidenote to the original topic! …
Rich Pedley: @Mark – test again
Thanks for that Rich, you can see I’m having a little nose around, and thanks for the offer Gautam — Even started talking to myself, and trying out other stuff too! 
As a sidenote to the original topic! …
Rich Pedley: @Mark – test again
Thanks for that Rich, you can see I’m having a little nose around, and thanks for the offer Gautam — Even started talking to myself, and trying out other stuff too!
