A plugin would be welcome. I doubt anything will be added to the core.
> why is this forum here anyway?
Support… 
The mailing list has less non-dev chatter. In fact it has none, so if people post dev related stuff there, they are more likely to get noticed. Most of the traffic here is community support – high quality community support I might add – but not generally stuff that directly relates to development of the codebase.
As for the question about jQuery UI, I guess we’ll move if there is a compelling reason. I’m sure there could be, and if you put a case either here or on the dev mailing list we can discuss it further.
You have to keep your custom templates up to date your self.
You might want to use the browser in the trac site to see which files have changed.
https://trac.bbpress.org/browser/trunk/bb-templates/kakumei
Put this in a plugin file named ‘_addSuperuser.php’ in the my-plugins directory:
function addSuperuserToArray($array)
{
$array[] = 'Superuser';
return $array;
}
add_filter('bb_trusted_roles', 'addSuperuserToArray');
.
If there is no my-plugins directory in the bbPress root, just create it. The underscore at the start of the file name should make the file autoload, so it is available without activation in the admin area.
I don’t really see what the difference is between “local” and “remote” gravatars, they are all remote to end users. I would suspect the changes by Automattic to the serving will be somewhat better than you imagine. Gravatar used to run from two servers, Automattic have a fair few more than that I believe, plus better caching setups. I guess we’ll have to wait and see, but it would be a shame to add options like local caching on top of the simplicity of the Gravatar idea.
As for the Ruby on Rails issue. I’m not 100% sure that the actual Gravatar serving uses Rails, it does use Ruby though. Ruby can scale, it’s just a little less used than PHP and I think it takes more resources to do it. There are a few scaled Ruby on Rails apps out there that are much more complex than Gravatar too, I’m thinking of the ones made by 37signals for example.
Automattic intend to upgrade the avatar size to 128 x 128
The word “import” is confusing, better to say “use”…
Didn’t one of the avatar plugins have gravatar support already?
Assuming you are actually talking about bbPress, the best solution I can think of is to make your cookies expire a long time in the future. Then you just need to login once for each user as long as the cookie is there. Anonymous posting doesn’t sound like a solution as you probably still want to know who owns which messages.
To set the cookies to expire after ten years, save this to a file called “_loginExpiry.php” in my-plugins:
<?php
function bb_login($login, $password) {
if ( $user = bb_check_login( $login, $password ) ) {
bb_cookie( bb_get_option( 'usercookie' ), $user->user_login, strtotime("+10 years") );
bb_cookie( bb_get_option( 'passcookie' ), md5( $user->user_pass ), strtotime("+10 years") );
do_action('bb_user_login', (int) $user->ID );
}
return $user;
}
?>
bbPress is released under the GPL v.2
Unless you plan to redistribute (i.e. give away or sell) your modified code, you are under no obligation to release your modified source code.
Unfortunately there are too many other things occupying my time right now as I’m in the middle of changing jobs. I anticipate I will have a lot more time to work on bbPress stuff in the future though. It will probably be mid November by the time I get things done.
Did the “you do not have permission” message occur on the command line? If the user you login as on the server doesn’t own the files you will need to do the chmod-ing as root. If you don’t have root access, then I have no idea how you edited the files in the first place.
The plugin doesn’t do any checking to determine whether the files are writable. It probably fails quite horribly if you have set PHP to write errors to the screen.
The files and folders need to be writable by the webserver user. You may have changed the permissions when you edited the files that exist there already.
The easiest approach (but insecure on shared hosting services) is to chmod the files.
chmod -R 777 bbpress-root/my-plugins
.
Or you can change ownership on those files to the webserver user, usually “www” or “apache” depending on the setup.
chown -R www:www bbpress-root/my-plugins
.
Remember that the upgrade facility of the plugin browser won’t maintain your manual changes to the plugins. You will need to re-edit the new versions.
Plugins that are installed normally will happily co-exist with those installed by the plugin-browser. Just keep them outside of the pb–xxxx folder structure.
bbPress themes are similar, but not drag-and-drop compatible with WordPress themes. What you are suggesting won’t work.
You will need to create a new bbPress theme to match your existing theme.
Try changing line 80 from this:
if ( !empty($this->charset) && version_compare(mysql_get_server_info(), '4.1.0', '>=') )
to this:
if ( !empty($this->charset) && version_compare(mysqli_get_server_info($this->$dbhname), '4.1.0', '>=') )
The database is selected a few lines down on line 83.
The socket (final and optional) parameter is not used as socket style connections aren’t supported.
Did you supply a password?
Does that database username have a password?
The error indicates there was none given.
Anyone desperate for some plugin action can try browsing the SVN repository directly:
https://plugins-svn.bbpress.org/
The last release of bbPress (0.8.2.1) is incompatible with WordPress 2.3
You can either upgrade to the latest trunk now, or wait a few days when a new bbPress should be released that is compatible.
See here: https://bbpress.org/blog/2007/09/wordpress-23-is-out/
You shouldn’t underestimate yourself _ck_, alot of the bugs in Trac that I have seen in the past are well within your range. You should try out a couple.
Did you activate them in the admin area?
This is only possible once the topic is created. In the standard template the button (link) is at the bottom of the topic page.
I found your topic…..
it’s here
Looks like there is a problem with the way slugs are generated and incremented.
I’ll look into it.
It probably has to do with the question mark in the original topic title.
Check your database and see if the topic slug contains the question mark as well.
There may be some discrepancy between the URI that is being produced and the topic slug it is trying to match in the database.
> I’m looking for the ability to assign any registered user (say, from a dropdown list) to any particular support entry.
This sounds like a nice feature. I’m working on 2.4 at the moment and I’ll consider adding it.
Do you want to be able to specify which users appear in the dropdown, or can I just offer the ability to list all moderators (or some other role)?
> Support Forums 1.2
That’s a really old version of Support Forums, not sure if it has anything to do with your problem, but it is really old.
