__ck__
i done what you told but i have got error:
see my script:
http://pastebin.ca/638062
mdawaffe has committed to try and bring the point releases closer together. I believe there are no hard targets set, but it should be better than last time. I would estimate that 0.8.3 will be out within a month, but that is just an estimate. mdawaffe gets pulled from bbPress all the time to do other things.
I can’t talk with authority about the XML-RPC features being added, but they will potentially open up a whole heap of options for people wanting to connect their forums with other forums and blogs. You should enquire about the development priorities and directions on the bbPress dev list though, you may get more joy there.
I just noticed you said something about cache? Is the cache working in the current bbPress release?
Apache processes rewrite directives in the order they are found.
First the main Apache config file is used, then (if they are allowed) the .htaccess files are used in the order they are encountered from the root of the website out through the directories until the final directory that contains the file that is being accessed.
So if you have a page at http://www.example.com/blog/forum, then the order of processing is like:
Apache config
|
+-> /path/to/site/www.example.com/.htaccess
|
+-> /path/to/site/www.example.com/blog/.htaccess
|
+-> /path/to/site/www.example.com/blog/forum/.htaccess
So the “blog” rewrite rules will be assessed first. This means that you may want to place your bbPress rewrite rules in the same .htaccess file as your blog rules, before the blog rules, as they are more specific and should be handled first.
Also, there were some problems with WordPress throwing 404 errors based on what mod_rewrite was doing. This was specifically with version 2.1 I think, so your WordPress may need to be upgraded.
Sounds like the pre-complied version list to download would be best then. It also allows you to do emergency holds or rollbacks if something in the SVN is discovered to be spyware or malware of somekind.
The version list could then be gzipped and even mirrored dynamically on trusted sources (like the supposed triple mirror wordpress.com runs on)
Yes, I know all that, but I was talking about Subversion clients, which I don’t know as much about.
I also don’t know if LiteSpeed can do subversion, LiteSpeed doesn’t do DAV at last check.
Subversion repositories tend to be set up more cautiously, so performance doesn’t really get a look in.
It’s Javascript. PHP files are just like HTML files, and anything outside the <?php ... ?> is treated as HTML. Calling the particular function around that makes it go to that place and then go through and output the HTML (which happens to be JS).
Web compression is on an “offered/accepted” handshake of sorts.
It would not affect clients that do not support gzip.
Everytime IE or Firefox (etc.) requests a webpage, it tells the server “I support gzip” in the headers and then if the server supports it, it sends it that way.
Technically compression can be forced through the server – if trac is under the same litespeed server as wordpress/bbpress then it’s just a matter of making sure it’s enabled.
A quick test shows both the svn+trac are using apache, so depending on which version it’s either a matter of building with mod_gzip (for apache 1.3.x) or if apache 2.0 they need to just add a couple of easy httpd.conf directives.
Really though, Matt knows how good litespeed is over apache, both the trac+svn should on litespeed. I bet it could even work with the free 150 connection version instead of buying a license.
Here’s a intermediate fix until whatever the causing reason is fixed:
http://www.burn-murdoch.com/colin/bbpress_fix_404.zip
Add this to the my-plugins folder (create the folder if neccessary) and activate the plugin in bb-admin.
All it does is call header(‘HTTP/1.1 200’) on the bb_init action, which overrides the 404.
I tried implimenting the user sync with wordpress but then realised I needed the two systems to use the same database. So I went through exporting the data from the bb database to put in the wp database. But it wont import because it says wp_usermeta and wp_users already exists in the wordpress database.
Correct me if I am wrong, because what I know about databases and sql you could put on the back of a postage stamp, but I think these two fields? have come from me trying to integrate the databases so is it ok to delete wp_usermeta and wp_users from the bbpress database before copying to the wordpress database?
hi again i want to know why the function grin(tag) { is out of php code
why it need to be out side?
you just need to use defalt themplate kakumei and
create language folder in bb-includes
then create php file and name it fa_IR.php put this line to it:
<?php
$text_direction = “rtl”;
?>
put fa_IR.php ito
bb-includeslanguages
then go to the root and open config.php
find define(‘BBLANG’, ”); and replace i with
define(‘BBLANG’, ‘fa_IR’);
have fun
dar zemn chakerim in themplate ro ham barat feretstadam monteha behtare ke az hamoun dast nakhorde ash estefde koni
I haven’t seen them (doesn’t mean it doesnt exist) but I’ve figured out the framework on how to build and attach a view if you’d like to copy my homework 
This is the code I whipped up for “most-views” and “least-views” (which requires the view count plugin to be installed (and inserting the views column in view.php)
function most_views_views( $views ) {
global $views;
$views['most-views'] = 'Topics with the most views';
return $views;
}
add_filter('bb_views', 'most_views_views');
function least_views_views( $views ) {
global $views;
$views['least-views'] = 'Topics with the least views';
return $views;
}
add_filter('bb_views', 'least_views_views');
function most_views( $view ) {
global $bbdb, $topics, $view_count;
if ($view=='most-views') {$sort="DESC";}
if ($view=='least-views') {$sort="ASC";}
if ($view=='least-views' || $view=='most-views') {
$limit = bb_get_option('page_topics');
$where = apply_filters('get_latest_topics_where','');
$most_views = $bbdb->get_results("SELECT topic_id FROM $bbdb->topicmeta WHERE meta_key='views' ORDER BY cast(meta_value as UNSIGNED) $sort LIMIT $limit");
foreach (array_keys($most_views) as $i) {$trans[$most_views[$i]->topic_id] =& $most_views[$i];} $ids = join(',', array_keys($trans));
$topics ="SELECT * FROM $bbdb->topics WHERE topic_status=0 AND topic_id IN ($ids) $where ORDER BY FIELD(topic_id, $ids)";
$topics = $bbdb->get_results($topics);
$view_count = count($topics);
$topics = bb_append_meta( $topics, 'topic' );
}
else {do_action( 'bb_custom_view', $view );}
}
add_action( 'bb_custom_view', 'most_views' );
As you can see a new view requires both 1. an action 2. a filter
Easy once you’ve seen it, but try figuring it out from scratch!
This bit adds the title to view pages (missing by default in bbpress)
function bb_get_view_title($title) {
if (is_view()) {$title = get_view_name(). ' « ' . bb_get_option( 'name' ); }
return $title;
}
add_filter( 'bb_get_title', 'bb_get_view_title' );
Hello everybody,
How can I set my bbpress forum as Right to Left?
Is there any theme in this case? or how can I customize the original theme myself?
Please help me to do this big matter..
My other option is to make the update check more atomic. Here, your pagination idea could help. So instead of fetching all the plugins, I could just fetch the first page, then the second etc. etc. on request. More complicated to code, but it might be the best long term solution to keep the best of both worlds. I could also add a way to list installed plugins first, or even have a separate view of installed plugins.
I wouldn’t think Trac is faster, it has a few more overheads on the server side I think. I don’t think it will come down to that though.
Neither the Trac site nor the SVN repository use compression on their output, so gzip is useless, but that was a good suggestion. I’m not sure the SVN repository could use gzip anyway as it would potentially get in the way of some SVN clients, I’m not sure SVN even supports compression techniques like that (although it probably should).
This is fixed in the latest trunk. I believe, the WordPress tag closing function has been moved across to bbPress.
fel64, the string is internal to bbpress, not the template loop.
Fair enough, shoulda checked that. So I went and looked through the code, you know, to find the problem. bb has quite an interesting structure there. Couldn’t find the problem, though, so I looked at the code in the .8.2.1 version and it’s missing a bit.
It’s fixed in trunk. Claire, upgrade to the latest version and it’ll work just fine.
Sooner or later you may want these other tweaks too:
http://ckon.wordpress.com/2007/07/12/bbpress-plugin-bb-tweaks/
1. Get rid of the ?replies=# ugliness in topic links
2. add nofollow to post links
3. add target=_blank to post links
4. auto-close tags – bbPress’s auto-close tags is broken by default
5. get rid of [closed] on subjects – useful if you have a narrow template
fel64, the string is internal to bbpress, not the template loop.
Look at forum.php template to remind yourself
<?php while ( bb_forum() ) : ?>
<tr<?php bb_forum_class(); ?>>
$forum is being treated as a global and not reset back.
I could remember and reset $forum I guess before and after the while-loop $temp=$forum; loop-here; $forum=$temp; but that’s an ugly hack. It’s got to be fixed in the core and that’s beyond my knowledge of bbpress.
fel64, the string is internal to bbpress, not the template loop.
Look at forum.php template to remind yourself
<?php while ( bb_forum() ) : ?>
<tr<?php bb_forum_class(); ?>>
$forum is being treated as a global and not reset back.
I could remember and reset $forum I guess before and after the while-loop $temp=$forum; loop-here; $forum=$temp; but that’s an ugly hack. It’s got to be fixed in the core and that’s beyond my knowledge of bbpress.
Unfortunately no clue how to fix.
Did this not work?
The terminology here is too close to “auto-close tags” which refers to the bug in bbpress where it’s not closing markup automatically (try posting < strong > here without a closing tag and you’ll see)
What you mean is auto-suggest tags (which I wish were called categories but the blogophere does love it’s crazy little terminology).
The features you ask for are way outside the core and would obviously have to be a plugin (but don’t look at me, I disable tags on my forums).
when I create a forum and subforums, if I post in the main forum the post automatically goes to the last of the sub forums – how do I correct this?
oooohh! That explains why I keep having to move posts.
That’s probably somehow associated with this bug I found:
https://trac.bbpress.org/ticket/704
It is indeed very annoying. Unfortunately no clue how to fix.
Yup. Just don’t display the forum if $forum->forum_parent is true. Change the bit in your templates that goes like this:
<?php foreach( $forums as $forum ) : ?>
//blaaaaah HTML
<?php endforeach; ?>
to this sort of thing:
<?php foreach( $forums as $forum ) :
if( !$forum->forum_parent ) { ?>
//blaaaaaah HTML
<?php }
enforeach; ?>
(ugh colon syntax)
[Edit] Beat me to it ck (by the way, blockquote is already allowed and you’re overwriting it. Doesn’t really matter but could add conflict problems if someone wants to allow it to have attributes). Claire, worth mentioning that this method means it will ignore any subforums without you having to tell it it’s a subforum.
Claire, markup is like this:
<anytag> your text here </anytag>
so actually HTML tags go between < and >. Actual code, like php code, will be shown as code if you put backticks around it. 
You can also use a simplified markup like http://www.loinhead.net/files/felise (just copy that into a plugin file and activate), which means that *this* is bold, _this_ italic and this@someurl turns into <a href="someurl">this</a>, etc. More on that https://bbpress.org/forums/topic/markdown?replies=10
If you are trying to use <b> instead of “strong” it won’t work because it’s not the “leet” xhtml standard that bbpress wants to enforce. But you can trick bbpress to allow it with this tweak:
function allow_extra_tags( $tags ) {
$tags['del'] = array();
$tags['strike'] = array();
$tags['s'] = array();
$tags['b'] = array();
$tags['i'] = array();
$tags['u'] = array();
$tags['bq'] = array();
$tags['blockquote'] = array();
$tags['pre'] = array();
$tags['hr'] = array();
return $tags;
}
add_filter( 'bb_allowed_tags', 'allow_extra_tags' );
note as you can see I allow other tags too
