[kevinjohngallagher]

Ah sorry Chris, I wasn’t clear.

What I meant was this:

• We want/need people to test a year’s worth of code in 1.0.3
• Why not download the latest version.
• Apply the the patch to that downloded code.
• Put in a zip file.
• Rename Zip file “bbpress-1.0.3-alpha.zip”
• Upload to website
• Ask people to download and test.

We know we can’t release 1.0.3 into the wild given that it’s whole implementation is questioned by the bugs in 1.1; but it’ll at least give us a heads up on a year’s worth of bugs.

[FMA]

I’m using the newest bbPress version.

How can I resolve/fix this? (:

[kevinjohngallagher]

bbPress is built to be a standalone software that can share logins with WordPress. It loads it’s own theme.

The best thing to do is to make your own bbPress theme that looks like your wordpress theme.

[Gautam Gupta]

We can add the same code (the one I posted in the patch) in bbPress, but BackPress would be a better place for that. Anyone should contact westi as he can fix it.

[Gautam Gupta]

Easy way is deep integration but is highly not recommended as it adds unnecessary extra load on the server. Other way is to code a template yourself which looks similar to your WP theme or hire someone to do that.

[kaluwu]

I have installed the wp multisite 3.0. and bbpress the latest version. Everything is fine. But when I click on forum, it lead me to another different templet which is the bbPress templet instead of my WP-MS templet. How can I use both with one site without going to the bbPress theme? Anyone?

[chrishajer]

BackPress is included as an external. I don’t have the ability to update the code here. I can just check in code to bbPress. Then, on some sort of cron schedule, the code that runs bbpress.org/forums is updated. It’s not nightly, as evidenced by the fact that this site is still running r2441 (actually, I think r2442: I tagged it wrong.) So, maybe it’s not automatically done, but the job fails and someone needs to do it manually.

So, I can’t update the BackPress code that is running on this site. I could fix my local installation, and you could fix yours, but I can’t fix it here.

If you want to see what’s included externally, you can download a trunk release from the bottom of a trac page and see that Akismet and BackPress are both missing. When I check out a copy with subversion, those externals are checked out. But I can’t check in to either of those projects.

[chrishajer]

I don’t think I have any ability to update the code that runs at the plugins site, so I can’t fix the plugins search. I believe the search is fixed here in the forums so if they update the code at plugins, it will be fixed.

I don’t know if I can fix the < < thing locally (in an external?) but I would rather they just fix the BackPress bug properly. If we fix it here, then there’s no pressure to fix it in BackPress.

[kevinjohngallagher]

Yes,

we’ve seen this before,

you cannot have a blank entry for your WordPress table prefix and integrate with bbpress1.0.

I am presumig you’re using bbpress1.0 (you’ve not mentioned it).

[kevinjohngallagher]

Actually,

Don’t we package and include BackPress with every release?

Why are we reliant on the BackPress team at all, can’t we just apply the patches to BackPress as we release them for testing?

If thats teh case, cant we get an alpha for 1.0.3 out the door soon? Maybe ask people to test it and get a few bugs in while waiting on 1.1 development?

[FMA]

Hello bbPressers! (:

I’ve got some problems with integrating WordPress into my bbPress install.

What am I doing wrong?

http://i45.tinypic.com/15678gn.png

There just simply no $table_prefix in wp-config.php

I hope someone can help me with this.

With Kind Regards,

FMA

[kevinjohngallagher]

Yes mate it is, but it’s mental that it’s still not been fixed.

The person who is doing these updates could even apply your patch to our own version of backPress on this site and it would be sorted.

[Gautam Gupta]

And seriously, what is up with these >>> tags? It’s about to span into it’s 3rd month of not working. We can only help so much…

That is a BackPress bug, I think you know about it.. – http://backpress.automattic.com/ticket/25

[kevinjohngallagher]

I can’t wait until email subscriptions arrive!! This will be awesome.

Indeed it was, 2 years ago when we had it as a working plugin.

Gautam,

Given that we’re waiting on BackPress to update, and that the bug in question hasn’t had any response/update from any AutoMattic employees in 6 months, and isn’t included in the next Backpress release… how crucial is it that this bug is fixed?

[kevinjohngallagher]

You know, I love the silent updates to the site; but at the risk of sounding ungraetful – Could you please TEST the chanegs after you’ve made them Live??

All links to plugins from the plugin browser link to: https://bbpress.org/plugins/topic/#post-

Can be seen/reproduced here: https://bbpress.org/plugins/search.php?q=test

And seriously, what is up with these >>> tags? It’s about to span into it’s 3rd month of not working. We can only help so much…

[lissovski]

Excellent, thanks. Looks like 1.0.3 will have the fix.

[mr_pelle]

I don’t think Matt knows that we are changing the version manually. It would be nice to have that updated automatically, but I don’t have enough access to make that happen with subversion, so I just change it manually.

I know, I know, I just thought it was funny that he did not even look at any last commit…

[Gautam Gupta]

Here it is – #1261

[lissovski]

I had searched for a ticket or post but couldn’t find anything. However, saw some posts about problems with deep integration with WordPress and, separately, Permalinks.

[Gautam Gupta]

This has been fixed in the trunk version.

[lissovski]

Clicking RSS links within the body of a page (ie, “RSS feed for this topic”, etc.) results in the following error on Google Chrome (5.0.375.86 beta):

—

This page contains the following errors:

error on line 10 at column 44: Entity ‘raquo’ not defined

Below is a rendering of the page up to the first error.

photogoodness forums » Topic: Test http://forums.photogoodness.com/topic/test

—

This is not happening with Firefox. Also, everything is fine if you were to manually copy the link and add it as a subscription to Google Reader.

I have verified that this is happening regardless of the Permalinks scheme. I have not done any integration with WordPress for this instance of bbPress, although I am running WordPress on a separate subdomain on the same host.

BTW, similar thing is happening with the version of bbPress currently up at bbpress.org/forums, ie it blows up in Chrome / fine in Firefox, although it’s a different error.

[chengdu-living]

I can’t wait until email subscriptions arrive!! This will be awesome.

[wallaroo]

Quote: If you’re using BuddyPress, you’re not talking to the people behind the bbPress you’re using. the bbpress that works with BuddyPress is a different beast, and for some reason they decided not to rename it, so we get the support questions and bad rep – constantly!

You know this is the first time that’s actually been explained (that I could find anyway).

I paid for an install of wpmu / buddypress / bbpress from the guys over at premium wpmu – and had some trouble understanding why there were 2 installs of bbpress. I guess this explains it (unless I’m still missing something) – so thanks so much.

[Gautam Gupta]

More updates

bbPress 1.0.3 milestone now only has 1 ticket left, which depends on this BackPress ticket), while 1.1 milestone has 2 tickets left (both need patches). There’s also another BackPress ticket that needs to be fixed (has patch).

Also, there would be no tag administration in 1.1.

And just for a note, matt also committed a patch about 11 hours back – [2450]

[chrishajer]

I don’t think Matt knows that we are changing the version manually. It would be nice to have that updated automatically, but I don’t have enough access to make that happen with subversion, so I just change it manually.