Fel -yup, that was apparently the problem
Livi- and that plugin works without borking code. Thanks!
I still have this problem. Anyone?
Any news on this issue? I’m constantly editing posts where users enter tags with spaces 
I would say the wording is correct. It’s the feature that needs fixing.
Yes, the line says “spaces” which adds to the confusion. BBPress touts a feature which doesn’t exist!
Ok, but we’re getting off topic. At least one other person has noticed this problem with tag separation, hopefully it can be looked at/addressed?
WordPress doesn’t have tags…
Thanks, fel.
One question-maybe this is stupid, but why do I seem to be the only one with this issue? No one else has users entering a mix of spaces and commas for tags? No one is getting new posts with separate tags as one long tag?
I updated to .8.2.1 and this issue isn’t resolved; in fact, it’s worse. I re-hacked the line to read
$words = explode(' ', $tags);
It no longer strips out commas. So a user entering this for tags in a new post:
“one, two, three four five”
returns these tags:
one,
two,
three
four
five
Any ideas how to fix this?
Brackets were just my (apparently needless) way of indicating a text field. Sorry 
Flickr works with spaces and quotes, but if you use commas, they are stripped.
For what it’s worth, flickr uses quotes for multiple words, so you could enter:
[foo bar “foobar”] or [foo, bar, “foo bar”] if you like commas. This seems a good way to handle both
I prefer commas too, but I have to say that nearly *every* post at my site has had tags entered with spaces. For whatever that metric is worth. Seeing as my change accepts both, all is good.
Ok, I changed line 1255 in functions.php to:
$words = explode(' ', $tags);
And this seems to allow both spaces AND commas in new post tags. If there’s a better way to do this, I’d like to know
I am running the latest alpha…it was switched to commas? Can it be switched back? Spaces I think are much more common a tag method than commas (or can it be hacked to acccept both?)
Thanks, but thats not what’s happening. These are all new posts. A user created a new post, enters “foo bar” and “foo bar” becomes one tag.
What I mean is, when I wrap text in backticks, it actually converts it to <pre><code> and removes the contents, replacing it with a random character, like an “n” or whatever.
I want to be able to just use backticks for code, but I can’t. That’s the problem.
Edit: Here’s an example. I created a post that looks like this (swapping a backtick for “[backtick]” so it won’t get eaten:
[backtick]test[backtick]
What it spit out is this (swapping parens for brackets so it wont get eaten):
(pre)(code)s`
(/code) `
This is the url:
http://automatorworld.com/forum/tags/
I’m having the problem described in this thread: the /tags/ page goes into an redirect loop, and doesn’t load if I have permalinks or slugs enabled. It works fine with permalinks off.
Thanks
Steve
Bumpage, sorry…anyone? Bueller?
Hi – I’m having the same problem with /tags/ when I use permalinks or slugs. I’m running latest bbPress with the trac fix, and the the htaccess hack didn’t work either (it spewed content of tags.php as raw text)
Any ideas?
What confused me I suppose is that post deletion and tag creation is ajax, so it seems natural that posts should be to. Is there reason they’re not?
My site has a similar integration. I tossed around the idea of doing a conditional header like you describe, but in the end it was just simpler to have a second header file specific for bbpress, which is basically a copy of the WP one with some of the required bbpress stuff thrown in.
Replies here are ajax, any idea how to get it to work?
Edit…or maybe not? I guess it just loads fast…
Re-reading the baptiste thread, I see that commenting out add_filter('pre_post', 'bb_filter_kses', 50); in default-filters does the trick. It solves all my problems at once!
I guess bbpress needs to do better conflict checking againt wp when wp is included.
This is the site: http://automatorworld.com/bbpress/
I’m wrapping my whole WP site around bbpress. It’s more than just styling, as you can see. I though this wasn’t supposed to present problems, but I guess this whole “kses” thing is one, eh?
