It would be easiest to hard code them if they don’t change very often.
_ck_ described how to get bbPress information inside WordPress. Maybe something similar would work in an opposite fashion to get WordPress information inside bbPress:
https://bbpress.org/forums/topic/heres-how-to-show-bbpress-info-inside-wordpress-without-full-integration
Hi chrishajer,
Thanks for the suggestion…….
but they are bound to change sometime in future.
I also read your article. Thanks I was bit struggling with this thing also(getting WP info in BBpress). But even if I get the information, how would i construct the Permalink structure of the WP.
I have been following the WP code to write my own functions, but they seem to go pretty deep and I dont know whether creating a copy of these functions in BBpress would be safe or not.
To use WordPress functions (like wp_list_pages), you need to include WordPress in your bbPress. For something simple like this, I was hoping you could get away without doing that since it’s not recommended and at this point I’m not sure if it even works very well. The other problem with integration like that is that you need to integrate the Alpha version of bbPress with WordPress version 2.5 or newer. You’ve already installed 2.7 and 0.9.0.4. I’m not certain what that achieved since the logins won’t be shared between those versions.
I don’t know if there’s a good answer for this, which is why I suggested hard coding it, at least for now.
Hi chrishajer,
I tried to find a solution for this problem and well this is what I could get upon…
When the WP config loads, it prepares the permalink string and then scans for a file (say links.txt) in the root folder.
If the contents of the file are not same with the generated permalink string, then its written into that file.
And when BBpress gets loaded, it reads that file for permalinks and then generates header/footer as per the links.
I know that this is not the best of the methods. But still this is what I could think of.
Hope its useful for anybody trying the same thing.