[@sambauers Participant 16 years, 11 months ago]

You have deleted all your data without a backup. Seems to me there is no solution.

[@sambauers Participant 16 years, 11 months ago]

See this post for a solution.

PHP Error Messages

This was a problem before this version, but is fixed in the latest builds.

[@sambauers Participant 16 years, 11 months ago]

bbPress uses encrypted cookies, you’ll need to give us a little more information on what you are trying to do if we are to help you.

[@sambauers Participant 16 years, 11 months ago]

Trunk is broken.

Try revision 1075.

[@sambauers Participant 16 years, 11 months ago]

Only if they choose to redistribute it. If they just run it as a service where the code is never sold to it’s customers – either as source or compiled – then they are under no obligation to release the source. I doubt it serves their interests to release the theme and in my opinion that’s fair enough and in the spirit of the GPL.

Besides this, it is arguable whether they would be bound by the GPL or not. As a theme strictly speaking isn’t a modification of bbPress (it’s just separate code that is compatible with the theme architecture) and the idea of “linking” as stated in the GPL is pretty vague when it comes to PHP applications. It was originally devised to cover more traditional application models where linking to libraries is more clearly defined.

[@sambauers Participant 16 years, 11 months ago]

@ChgoGrrl99

We’ll be attempting to make future upgrade processes as seamless as possible.

[@sambauers Participant 16 years, 11 months ago]

https://bbpress.org/forums/topic/making-your-theme-compatible-with-0831

[@sambauers Participant 16 years, 11 months ago]

@ fel64

BackPress is already a separate repository which is linked to externally within the bbPress trunk.

For interests sake the BackPress repository is here:

http://svn.automattic.com/backpress

BackPress has no separate Trac though.

[@sambauers Participant 16 years, 11 months ago]

@ chrishajer

Whenever I have linked to trunk in the past I have always mentioned and or linked to specific revisions, so I don’t think this is a major issue. I’ll stick it to the top so that it is obvious to people anyway.

[@sambauers Participant 16 years, 11 months ago]

@ _ck_

I suggest you try a new test install of both bbPress and WordPress integrated to see the way the auth and secrets are supposed to match up in a “clean” environment. You should be able to adjust things in your existing installation as a result.

[@sambauers Participant 16 years, 11 months ago]

> so an existing forum with 1000 users will have to instruct every single one to clear their cookies

Not necessarily, it just may be an issue if your cookies weren’t expired already.

> I wonder if this has to do with the hard coded hash I have set in bb-config.php

> How does this affect a setup with a shared login from wordpress where you have to match the same hash it has?

You will need to also run WordPress trunk to match the cookies and hash methods up. WordPress has also migrated their cookies and password hashes in trunk.

> hope there was a good reason to fiddle with it

Judge for yourself, we followed WordPress’ lead:

https://trac.wordpress.org/ticket/5367

[@sambauers Participant 16 years, 11 months ago]

You know that both cookie and password hashing have changed? You may need to clear your old cookies manually to make way for the new ones. Send a mail to the dev list or hit us on IRC in the #bbpress channel and well work out what’s going on.

We’re acutely aware of how spammers attempt to “fool” Akismet. There are steps being taken now to help improve the processes involved in combatting this. Remember that we are users of Akismet too, so have an interest in keeping it ahead of the game.

The nature of Akismet’s purpose means that back-end code needs to remain closed. If spammers knew how it worked, it would likely make it possible for them to game the system. Of course it is opt-in, so if you don’t like it then you don’t have to use it. Controlling the data that is passed to Akismet is controllable from the client end using plugins that can limit it’s behaviour. These already exist for WordPress, bbPress ones could be easily developed too. If there are hooks missing to make that possible then we’ll add them.

[@sambauers Participant 16 years, 11 months ago]

You are right, 1075 is probably the most stable release for “cutting-edge” users, but we would appreciate testing of trunk during integration of BackPress.

We do intend to experiment with PingBacks and TrackBacks in topics via XML-RPC, and you could be right about spam, but we won’t know until we try. We will build out the spam tools provided by Akismet to try and meet the challenge of spam at the same time. There are also other ways in which we can utilise XML-RPC besides those two features which you may not have considered, we already have some cool ideas about user integration and content aggregation that should be driven by the needs of the hosted project. I hope you don’t leave us just for giving it a whirl

The “Press” names are mostly about branding and the they need not be taken literally. We can leverage a lot of good-will by associating with WordPress, and we intend to create better ways to integrate the two projects, regardless of where they are installed or hosted.

[@sambauers Participant 16 years, 11 months ago]

Things may be a bit confusing at the moment with two new and different names flying around. I’ll do my best to clarify things and we can use this topic for everyone to ask questions on the subject and provide input.

For those who are interested, the first thing to do is read this post (and the articles it links to) in the blog:

The future for bbPress

That post is pretty vague about things. So let me be more specific here. First, I’d like to make it clear that bbPress is not being replaced or abandoned or drastically changing direction. As for the two new names that have been mentioned, I’ll cover them below.

BackPress:

bbPress has a lot of shared code with WordPress. BackPress is the name of a new project which is attempting to normalise this shared code into a set of generic files that will simply plug in to both projects (and potentially others). This allows us to leverage the testing and improvements made to this shared code without the overheads of manually merging changes. This way we can spend more time on bbPress’ unique code and extending new functionality.

TalkPress:

It has been public for a while that Automattic intends to create a hosted forums service based on the bbPress project code. The intention is to make this work much like the existing WordPress.com hosted service for blogs. Matt Mullenweg let it slip that the working name for the project (and not necessarily the service) is TalkPress. We probably won’t talk much about it here, but I can say that the majority of the code written to create this new project will be released as open source. Regardless of the name of that service when it launches, the name of this project, “bbPress”, will not change.

As for the upcoming work for bbPress, I’m happy to elabrorate here:

bbPress code:

Along with the inclusion of BackPress into trunk, there are other things going on. We are in the process of implementing a new taxonomy structure for tags. Improving bbPress’ object cache to make it compatible with various WordPress object cache plugins. Replacing the fairly ordinary “favourites” system with a much more flexible and useful topic aggregation tool, and later on we will be incorporating a set of functionality based around the XML-RPC tools available in WordPress such as pingbacks and trackbacks.

bbPress.org website

The bbPress.org website is due for a clean up. Most importantly, the extend area will be upgraded to include a plugin repository similar in functionality to the one that exists on the WordPress.org website. There is a possibility that we will also launch a theme repository based on the same system. A little later on, we plan to re-design the whole site.

I hope this clears things up a little and I’m happy to answer any questions here. I can’t think of anything, but it’s possible that there may be some things that I can’t say about the hosted service project. Feel free to ask though.

[@sambauers Participant 16 years, 11 months ago]

We can continue this conversation over here:

TalkPress

Closing this topic.

[@sambauers Participant 16 years, 11 months ago]

Repost from the dev mailing list:

As of the last commit at this time (revision 1076), trunk is in an experimental and unreliable state. We are attempting to abstract some functions and classes for easier sharing of code between WordPress and bbPress. This shared code is called “BackPress”, and we’ll probably be mentioning it a few times here and there in Trac and other dev discussions.

[@sambauers Participant 16 years, 11 months ago]

I’m out of ideas I’m afraid.

[@sambauers Participant 16 years, 11 months ago]

@j8h9

I’ve got 3 fixes for you to choose from:

1. Make the above changes

2. Upgrade the version of PHP you are using

3. Download the current trunk (rev 1071) here

Or go back to phpbb, your choice.

: )

[@sambauers Participant 16 years, 11 months ago]

Looks like it may be rejecting the mail due to the “From” email address being invalid. Try this code in a plugin and make sure your admin_email option is a valid email address:

<?php

if ( !function_exists( 'bb_mail' ) ) :

function bb_mail( $to, $subject, $message, $headers = '' ) {

if (!is_array($headers)) {

$headers = trim($headers);

$headers = preg_split('@r(?:n{0,1})|n@', $headers);

}



if (!count($headers) || !count(preg_grep('/^from:s/im', $headers))) {

if (!$from = bb_get_option('admin_email'))

if ($uri_parsed = parse_url(bb_get_option('uri')))

if ($uri_parsed['host'])

$from = 'bbpress@' . trim(preg_replace('/^www./i', '', $uri_parsed['host']));



if ($from)

$headers[] = 'From: "' . bb_get_option('name') . '" <' . $from . '>';

}

$headers = trim(join("rn", $headers));



return @mail($to, $subject, $message, $headers);

}

endif;

?>

[@sambauers Participant 16 years, 11 months ago]

That’s right, enough room for every person on the planet to have 3 billion accounts in your installation.

[@sambauers Participant 16 years, 11 months ago]

See the solution in this post. It may fix your problem.

https://bbpress.org/forums/topic/php-error-messages?replies=10#post-13143

[@sambauers Participant 16 years, 11 months ago]

Because of the restrictions on the bbPress logins in the current version I suggest using bbPress for registration/login. Logout can be either.

With WordPress 2.5 and the next bbPress 0.8.x they will be as good as each other.

Please don’t bump.

[@sambauers Participant 16 years, 11 months ago]

Put this in a plugin file and activate it. It’s a drop-in replacement for bb_mail() from the current trunk

<?php

/*

Plugin Name: Fix bb_mail function

Plugin URI:

Description: Temporary replacement for bb_mail() function

Author: Sam Bauers

Author URI:

Version: 0.0.1

*/



if ( !function_exists( 'bb_mail' ) ) :

function bb_mail( $to, $subject, $message, $headers = '' ) {

if (!is_array($headers)) {

$headers = trim($headers);

$headers = preg_split('@r(?:n{0,1})|n@', $headers);

}



if (!count($headers) || !count(preg_grep('/^from:s/im', $headers))) {

$from = parse_url(bb_get_option('uri'));

if ($from && $from['host']) {

$from = trim(preg_replace('/^www./i', '', $from['host']));

$headers[] = 'From: "' . bb_get_option('name') . '" <bbpress@' . $from . '>';

}

}

$headers = trim(join("rn", $headers));



return @mail($to, $subject, $message, $headers);

}

endif;

?>

[@sambauers Participant 16 years, 11 months ago]

The filename and the BBLANG definition have to be the same.

So sv_SE.mo should have:

define(‘BBLANG’, ‘sv_SE’);

[@sambauers Participant 16 years, 11 months ago]

Which version of bbPress was this? 0.8.3.1 or latest trunk?