Search Results for '"wordpress'
-
Search Results
-
Hi. I am setting up integration with Word Press. On the integration page in the bbPress admin, it says:
This must match the value of the WordPress setting named “auth_salt” in your WordPress site. Look for the option labeled “auth_salt” in this WordPress admin page.
“in this word press page” links to :
[wordpress folder]/[bbpressfolder]/bb-admin/options-wordpress.php#
but there is no “auth_salt” anywhere on this page.
One thing i notice is that it says the option is in my wordpress site, but the page it takes me to is part of bbPress.
I need something like «bbPress post» plugin. But only for «Discuss» link on every post in my wordpress blog. Link must create topic for discuss. First post in bbpress topic must be content from post in wordpress blog where link was clicked.
Looks like «bbPress post» is not available by now – http://bbpress.org/forums/topic/bbpress-post-003
Sorry for my bad english
Topic: bbpm and wordpress
Hi. My site has bbpress integrated into wordpress. I’ve added bbpm plugin so that private messaging is enabled in the forum section. Trouble is recipients can’t read their received PM’s because they are not displayed in wordpress admin.
http://www.fire-sprinkler.co.uk.
Anyone know of a solution or workaround?
bump.
after reading wordpress and bbpress forums and posts and … finally coming to the realization that what I’m looking for is this “bbpress channels” extension. I’d love to know when it might be available? We’re going to unleash bbpress on hundreds of sites via a multisite server if we can get bbmu to work… I ‘spose I can write my own extension, but it’d be more fun to install and tweak yours. thanks!
Topic: languages problem
I had install wordpress vision 3.0.1 and buddypress plugin. I installed bbPress forum. The problem is it only support English language. it did not genarate utf-8. the post topic like this ??????(1post)and the post like this ???????.
but if I write in English it is work fine.
How do I fix this problem? anybody can help. Thanks for the the wise man.
Thanks to JJJ for pointing this topic out to me.
Right now, my forum plugin isn’t planned for public release. I’d much rather see a community-supported plugin because a lot more can get done. The plugin could simply be better developed and have better support if it’s a community-run project. Make no mistake, a plugin like this is massive amounts of work, more than one person can realistically handle. Honestly, I don’t want to be the only person developing and supporting a forum plugin.
The reasons I’ve been doing my own thing rather than fully devoting my time to bbPress:
1) I just wanted to see if I could do it for fun.
2) I had some projects that needed basic forum functionality that couldn’t wait for alternate solutions.
3) Everybody wants something, mostly things I don’t believe belong in a lightweight forum plugin.
4) I’ve been hesitant to get more involved in bbPress because I don’t want to deal with all the drama here.
I just finished three months of intense writing for a WP plugin book, so my time has been limited for a while. I’ve still got book-related things this month as well. Once this process is done, I plan to devote more time to the bbPress plugin.
What we want:
These are the things I believe most of us want, which is the reasons I put together a plugin and the reasons for the bbPress plugin. This comes down to two things:
* A plugin that easily integrates into the WordPress user/role and login system.
* Forums that can be managed from our WP admins.
It’s basically about being able to run forums without a lot of hassle.
The direction I’d like to see the bbPress plugin go:
* Stick with the philosophy: lightweight and basic.
* Allow plugins to extend anything needed beyond basic forum functionality.
* Use the functions WordPress provides where possible.
* Forget backwards-compatible hooks and functions. Build a new system.
Thanks to JJJ for pointing this topic out to me.
Right now, my forum plugin isn’t planned for public release. I’d much rather see a community-supported plugin because a lot more can get done. The plugin could simply be better developed and have better support if it’s a community-run project. Make no mistake, a plugin like this is massive amounts of work, more than one person can realistically handle. Honestly, I don’t want to be the only person developing and supporting a forum plugin.
The reasons I’ve been doing my own thing rather than fully devoting my time to bbPress:
1) I just wanted to see if I could do it for fun.
2) I had some projects that needed basic forum functionality that couldn’t wait for alternate solutions.
3) Everybody wants something, mostly things I don’t believe belong in a lightweight forum plugin.
4) I’ve been hesitant to get more involved in bbPress because I don’t want to deal with all the drama here.
I just finished three months of intense writing for a WP plugin book, so my time has been limited for a while. I’ve still got book-related things this month as well. Once this process is done, I plan to devote more time to the bbPress plugin.
What we want:
These are the things I believe most of us want, which is the reasons I put together a plugin and the reasons for the bbPress plugin. This comes down to two things:
* A plugin that easily integrates into the WordPress user/role and login system.
* Forums that can be managed from our WP admins.
It’s basically about being able to run forums without a lot of hassle.
The direction I’d like to see the bbPress plugin go:
* Stick with the philosophy: lightweight and basic.
* Allow plugins to extend anything needed beyond basic forum functionality.
* Use the functions WordPress provides where possible.
* Forget backwards-compatible hooks and functions. Build a new system.
I’ve had a check-out for a while, but nothing of his has made it in yet.
Because there are only so many ways to do the same thing, our code is very similar with a few different methods here and there. His code is more mature in a few areas (mapping WordPress meta capabilities, topic/reply counts, additional query caching…) and it’s almost time to cherry pick his code and give props where due.
He started out using taxonomies for forums, but a lack of taxonomy meta thwarted that idea. We talked before either of us made too much progress on how to best do things so we would be loosely compatible with each other. I committed early on to using post types for data storage for everything to allow for easy forward compatibility with things like forum/topic/reply thumbnails, excerpts, revisions, etc… Justin and I both agreed it was the quickest way to go, we put our noses down and wrote some code, and we met a month or two ago in #bbpress on IRC and exchanged more code and ideas.
It was really cool for Justin to volunteer to share his code and approach. He spent countless hours getting things dialed in and that time is going to be greatly appreciated real soon.
It would have been even cooler to have him contribute patches directly to trac, but from what I recall of our talks he had some previous obligations that prevented it. I’m sure if I’m wrong Justin will catch wind and chime in.
Edit: I saw a reply in the above linked topic about him ‘turning over’ code to bbPress, but I don’t really see it like that. His code is always his, and he’s free to continue developing his plugin if he wanted to. No hard feelings.
The bbPress trac is public and the code is visible for everyone to see, versus Justin’s forum code which to my understanding isn’t something he wants openly available for download, or else I imagine he’d probably have it that way. I know from experience that supporting something as large as bbPress on top of other obligations can be a challenge, so I wouldn’t blame him for not wanting to volunteer additional time.
Either way I’m honored to have his respect and be able to have someone attempting to do something similar at the same time. It’s one of the first times in my professional career I’ve had what most people would consider ‘friendly competition’ without ever feeling like we were against each other in any way… not that I’ve ever had unfriendly competition… but you get the idea.
I’ve had a check-out for a while, but nothing of his has made it in yet.
Because there are only so many ways to do the same thing, our code is very similar with a few different methods here and there. His code is more mature in a few areas (mapping WordPress meta capabilities, topic/reply counts, additional query caching…) and it’s almost time to cherry pick his code and give props where due.
He started out using taxonomies for forums, but a lack of taxonomy meta thwarted that idea. We talked before either of us made too much progress on how to best do things so we would be loosely compatible with each other. I committed early on to using post types for data storage for everything to allow for easy forward compatibility with things like forum/topic/reply thumbnails, excerpts, revisions, etc… Justin and I both agreed it was the quickest way to go, we put our noses down and wrote some code, and we met a month or two ago in #bbpress on IRC and exchanged more code and ideas.
It was really cool for Justin to volunteer to share his code and approach. He spent countless hours getting things dialed in and that time is going to be greatly appreciated real soon.
It would have been even cooler to have him contribute patches directly to trac, but from what I recall of our talks he had some previous obligations that prevented it. I’m sure if I’m wrong Justin will catch wind and chime in.
Edit: I saw a reply in the above linked topic about him ‘turning over’ code to bbPress, but I don’t really see it like that. His code is always his, and he’s free to continue developing his plugin if he wanted to. No hard feelings.
The bbPress trac is public and the code is visible for everyone to see, versus Justin’s forum code which to my understanding isn’t something he wants openly available for download, or else I imagine he’d probably have it that way. I know from experience that supporting something as large as bbPress on top of other obligations can be a challenge, so I wouldn’t blame him for not wanting to volunteer additional time.
Either way I’m honored to have his respect and be able to have someone attempting to do something similar at the same time. It’s one of the first times in my professional career I’ve had what most people would consider ‘friendly competition’ without ever feeling like we were against each other in any way… not that I’ve ever had unfriendly competition… but you get the idea.
