@doyle640
If you mean basic user database and cookie sharing then yes (and it should have worked in 1.0-alpha-1 as well). If you mean loading WordPress inside bbPress, then no – that is still partially broken.
@beernews
I hope not, although it’s getting closer, it’s not production ready yet.
This was a small oversight which is already fixed, if you re-download the release it will be fixed there.
Does this happen when you log out of bbPress then login to WordPress?
@ddemeo
Probably, I haven’t tried an upgrade form 0.9.0.2 yet. In theory it should work. If you try it then make sure you backup your files and database first.
There was an error in the original release, the fix is made, but until it is available on the download site you need to get it from here…
[deleted] – see below
The zip archive is at the bottom of the page.
There was an error in the original release causing this, the fix is made, but until it is available on the download site you need to get it from here…
[deleted] – see below
The zip archive is at the bottom of the page.
@leoleoleo
Well, you should just be able to replace the bbPress files with the new ones then go to your sites admin area to run the upgrade script (it appears automatically if it is required).
Make sure you backup your old files and your database first to be safe.
Does that mean you are including WordPress’ header.php file in bbPress?
@_ck_
Thanks!
BTW, you’ll be happy to know there are three different ways to tun off XML-RPC:
* In settings
* Forcibly, via a plugin
* Just plain delete the file (xmlrpc.php)
But I’d like to think that you could help us to keep it secure instead : )
On a related note, thanks to everyone who has helped out with testing so far. Apparently the first alpha was downloaded over 2,500 times, thanks to all those who took time to report bugs and suggest improvements over that time.
I’m looking forward to further input and feedback as we approach 1.0 beta and beyond.
@ear1grey
A commendable approach, I approve.
Are you loading WordPress inside bbPress?
I’ve added the ability to do this to the development trunk. If you want to backport this to an older bbPress, you can follow the changes here:
https://trac.bbpress.org/changeset/1786
Then drop the function <?php bb_latest_topics_pages(); ?> wherever you want it in the front-page template to show pagination.
Latest discussions on the front page is meant for latest discussions… so paging has never been a possibility there.
Forum pages do provide paging of topics though.
The admin screen was not available until today. Try installing version 0.1.2 of bbPress Live.
The only ways to do this are fairly hackish. I wouldn’t recommend them.
Another thing left is to try it using the default template instead of the custom one you are using and seeing if that changes the behaviour.
You can just switch to it temporarily, then test and switch back.
The display of that empty option is suppressed in 1.0 when it isn’t available.
It’s only ever visible to admins anyway, so it wasn’t a huge deal.
Turns out there is an error in 0.9 that stops the “throttle_time” option from being set.
If you run this raw SQL on your database it should set the option to 30 seconds which will force a checkbox to show up in that form.
INSERT INTO bb_topicmeta VALUES (NULL, '0', 'throttle_time', '30');
Some cookie handling has changed since the first alpha release.
@Detective
Why not just edit the previous post? 5 minutes is within the default editing time limit.
Topic meta is similarly arranged to do less queries. I think the problem that was cited was that sticky topics and normal topics were not done in the same query. We decided against changing that in the end I think.
I’ve pinpointed and fixed that particular issue on topic pages in trunk. You should only get a query equivalent to number 55 in your query set for adding meta data, but the individual user queries will remain. Still, that will help a lot on that particular page.
The password hash is always unique, even when the password is the same, that’s the nature of phpass hashes.
I joined and logged in to your site. I edited my profile and indeed the password stopped working. First things first, try deactivating the signatures plugin you are using and see if the problem still occurs. If not that’s the culprit and it needs to be modified by the plugin author to stop this behaviour.
