Forum Replies Created
-
In reply to: Upgraded to 0.8.3.1 – special characters broken
I’d say it was latin1 all along.
I’m not sure how well older versions of bbPress handled character sets. But it works properly now at least.
There are other factors that could have influenced things as well, but the permutations are a little too numerous to list.
In reply to: Trouble with first time loginI assume that bbPress is in a sub-directory of your WordPress install?
Sounds like the rewrite rules are incorrectly set or the existing WordPress rules are somehow getting in the way of bbPress.
What type of permalinks are you using? Set that value to FALSE in your config.php if they are turned on and see if this still happens. I think that will narrow it down a bit.
In reply to: Upgraded to 0.8.3.1 – special characters brokenbbPress will create tables using the character set and collation specified in the config.php file. However it won’t change the tables character set or collation if they are already created, as in the case with upgrades like yours.
In fact, once installed, the collation value is not used at all, but the character set value is forced on every connection to the database with “SET NAMES ‘foo'”, where ‘foo’ is the character set (if it is specified).
So if your database is ‘latin1’, and for some reason we don’t address it that way you will get improper character mapping of your data to characters.
In reply to: PHP Error MessagesThis is fixed in the latest trunk by the way.
In reply to: PHP Error MessagesChange line 168 of bb-settings.php to
if ( function_exists( 'glob' ) && is_callable( 'glob' ) ).
Also, change line 6 of bb-admin/plugins.php to (note curly brace at the end)
if ( function_exists( 'glob' ) && is_callable( 'glob' ) ) {.
I suspect the version of PHP where the problem is occurring is less than 4.3.0
Either that or the “glob” function is disabled by the system administrator.
In reply to: Upgraded to 0.8.3.1 – special characters brokenYou should find out what character set your database is in and try to match it with the charset constant in the new config.php
Copy all other config values over verbatim.
In reply to: PHP Error Messages> This has been reported 3 or 4 times.
Can you link to the Trac tickets? I’ve never experienced this issue. With or without a plugins folder.
In reply to: Upgraded to 0.8.3.1 – special characters brokenDid you change or not set the database character encoding settings in config.php.
They need to match your previous install, including being blank if you previous install did not have them set.
In reply to: Cannot set forum name other than roman letter!If you use the latest trunk from the subversion repository then this setting is made in the database rather than the config file.
Scroll to the bottom of this page and use the “Zip Archive” link.
Although a little new, trunk should be stable enough to use right now (rev.1010).
Better still, install trunk using subversion and then updating is much simpler.
In reply to: bbpress + wp user integrationYou can’t share cookies across domains that are as different as that
The domains need to have some common part like:
blog.example.com
forum.example.com
In reply to: Import/Export WorkbbPress has a fledgling xml exporter. We had a discussion on IRC#bbpress recently about creating an importer of the same format.
This would be great for migrations and backups, and if we wrote some code for other forum software to export to this same format, we would have greater ability to cross-grade.
In reply to: Retrieve the “secret” valueThe “secret” in the installer is only relevant once the new cookie creation methods in WordPress trunk are ported across to bbPress.
That should be soon.
Matching it with the secret in WordPress is only necessary for integrated installs.
Furthermore, there are two secret values. One in the config file, and another in the database.
The only way to retrieve them from WordPress at this stage is to look at the config file and to manually query the database.
I realise this is messy at the moment and I am trying to get things up to parity with the current WordPress trunk.
I don’t package up the releases, I’ll see what mdawaffe thinks.
[971] is the best candidate.
Revision [971] is the best option to integrate with WordPress 2.3.1 in my opinion.
Trunk will not be compatible with WordPress 2.3.1 again. Maybe not ever. It will be compatible with the upcoming WordPress 2.4 when that is released (or soon after).
In reply to: Url Rewriting ProblemThe short answer is that you can’t.
bbPress would have no way to tell whether it was searching for a topic or a forum.
In reply to: Let’s collaborate on bbPulp.orgI was actually suggesting that the user-level stuff stay off there and be concentrated in the documentation here on bbPress.org
But if people are keen about writing docs then perhaps bbPulp can be a sandbox for that and when content matures it can be pulled across here to the “official” documentation.
I’m not sure that’s the right advice. The latest development versions will definitely break integration as they are geared towards integration with the current WordPress trunk. There are lots of differences in password hashing and cookie storage.
Revision [971] might be OK to use for this specific problem, but I can’t guarantee it. And it won’t fix socket connection under MySQLi.
In reply to: Broken Profiles for users with spaces in the names.You can have it now if you use trunk.
At the moment revision [980] is the most stable.
ZIP file is at the bottom of this page:
https://trac.bbpress.org/browser/trunk?rev=980
If you are integrating with WordPress at the moment I don’t recommend using trunk though.
> I suspect bbPress of having hard coded a connection to localhost and thus configuring define(‘BBDB_HOST’, ‘…’) to be something else than localhost doesn’t really matter.
That’s simply not the case.
…you need to change them unless you want the same data in each installation.
You could prefix the first install “bb1_” an the second “bb2_” (you get the idea)…
Whatever makes sense to you, there is no guideline.
In reply to: DB access problem in the first installation step.The very latest trunk [988] is a little unstable.
You are better off with [980] the zip download of [980] can be found at the bottom of the following page:
In reply to: Limiting RSS Feed to First Post OnlyIf you can wait, this functionality is probably going to be in the next release anyway.
I’ve already started work on it. I was just putting it aside until I got the new installer and options pages finished.
In reply to: constant BBDB_HOST problemDB_HOST is not the right constant, do you mean BBDB_HOST ?
In reply to: Having trouble integrating WP functionsstreams.php and gettext.php are just libraries, so if they are loaded by WordPress, then they don’t need to be loaded again. Although “include_once” should take care of that.
The problem with the language file not loading is because of the next couple of lines. They say that if WordPress is loaded not to load the kses.php and l10n.php files. This means it is looking for yor language file for bbPress in the same place as the WordPress language file.
It’s possible (but I don’t know enough about how gettext works) that just dropping the bbPress mo file into the same place as the WordPress mo file will work… just call the bbPress mo file bbpress-de.mo or something like that.
I think someone solved this before… search a little harder through the forums I think.
