I believe the theme for this forum is available for download somewhere, it might even be Trent’s theme?
The GPL doesn’t work that way. The idea of “linking” is very compiler specific terminology, it doesn’t really apply to php scripts calling other php scripts.
Changing GPL code is OK and you can’t be forced to redistribute it (hand over source), but if you do, the source must be made available and the licensing must remain the same GPL license.
user_nicename isn’t what you are after. You want the display_name column. user_nicename in WordPress is a URL safe version of the username. Future versions of bbPress will utilise this field for that purpose too.
Trent’s right. The string ‘false’ equates to the boolean TRUE. Which means you have basic permalinks turned on.
This is addressed in the latest revisions and should be part of the next release.
And in case anyone wants to keep their passwords hashed in MD5, I’ve got a plugin that’s about to go into the plugin browser that enables that (for bbPress anyway).
The current trunk contains the new password hashing method. We will do a simultaneous release with WordPress to avoid issues for people with integrated installs.
The quickest (and dirtiest) solution might be to change line 91 in bb-settings.php to:
require( BBPATH . BBINC . 'db.php');
.
I haven’t tested this, but it should work.
It will force bbPress to use the MySQL PHP extension instead of MySQLi
bbPress passes of the email to PHP immediately. So timing is all going to depend on how your web host handles email sent from their web-servers. Some throttling of emails may be in place to discourage spamming via badly configured web based email forms. This is not unreasonable of them to do if that’s the case. You’ll need to talk to them to get this changed for you if possible.
If you supply the url of your site and the relevant contents of your config.php file I’m sure someone here can sort out your problem. People have used GoDaddy before, just without permalinks.
Are you sure they are robots? There are people in India, China and elsewhere whose job it is to register spam users to websites.
These measures will not work on them at all.
Yes, by design of the system… 
This is by design at the moment.
Better to use the latest version from trunk than those diff files if possible.
Of course, people can do what they want, but I don’t think this is an appropriate use of tags. Some plugin that added a text input field to the posting form and used the topic meta table to store the option would be better.
The file you mentioned is harmless.
Your problem was with an iframe that was inserted at the end of the page.
Your site still contains some obfuscated javascript at the end of the page.
Were you aware of this site:
http://bbpress.de/
?
I didn’t say anything about the script at the top. I assume that’s from a plugin you’ve installed.
Remove the script and iFrame from the bottom.
Look in footer.php
Where did you download your files from?
At the end of your pages, after the closing HTML tag there is an additional script and an iframe.
This code is not in the download tarballs, so it seems the code has been injected on your site only. You should contact your web host for assistance as your service may have been compromised.
The sub-forum setup may not be what you are after exactly, but it is the only way to closely approximate your needs using a default install.
Categories (similar to what you show in your image) was something I spent quite a lot of effort on a few releases ago. It never made it to core, but there is still an intention to add similar functionality in the future. I’m thinking maybe we should have forums which don’t hold topics, and act as de-facto categories when they contain sub-forums. This is future stuff though, for now sub-forums is as good as it gets.
I think that’s what chrishajer is suggesting. Maybe try it and see if it turns out right for you.
There is an LDAP plugin which would be a good jumping off point for Active Directory authentication.
https://bbpress.org/plugins/topic/26
Theme compatibility between WordPress, bbPress and MediaWiki is a stretch. I have a project on the back-burner that might help with WordPress/bbPress theme integration, but MediaWiki is a big ask.
Sounds like a guestbook to me.
All we use from the Interface library is “Sortables”:
http://interface.eyecon.ro/docs/sort
This is probably easily replaceable by the jQuery UI counterpart.
We have some other priorities first though, I propose the following path:
1. Upgrade to jQuery 1.2.1
2. Remove Prototype JS and replace with jQuery
3. Move accross to jQuery UI
Thoughts?
BTW, we still only run jQuery 1.1.4 and jQuery UI requires 1.2.1
