[Abdessamad Idrissi]

thank you guys,

@psycheangels

I checked the database and my forum as well and can’t find any problem either with forum_slug or post_position, if you have this problems, maybe, you are using an old bbpress or phpbb3 installation, it is recommended that you update both your phpbb3 and bbpress installation to the latest versions (as stated in this page title) before proceeding with the convertion.

[yangt299]

Tested.

Will not work with W3 Total Cache either. Shame. Any other good cache plugins?

[Abdessamad Idrissi]

ABOUT

A script to help you convert you phpbb3 (version 3.0.7) forum to bbpress (version:1.0.2) forum. This code is an update to the code made by wmnasef (http://bbpress.org/forums/topic/phpbb3-gt-bbpress-converter-beta-release).

GET IT @

http://code.google.com/p/phpbb3-to-bbpress1-converter/

BUGS CORRECTED

* works with bbpress 1.0.2

* corrects the single quote problem

* corrects the login problem

HOW TO INSTALL

1. make a backup from your online forum (if possible make an exact copy of your forum in your localhost server, this prevents any damage to the online forum).

2. install bbpress anywhere, just use the same database of phpbb3. this is important because the script assumes that all tables are in the same database.

3. download the script from here. extract it, and you’ll get 2 files.

4. copy the file phpbb3tobbpress.php to “phpbb3/” directory.

5. copy the file _phpbb3_pass.php to bbpress/my-plugins/ directory (if it doesn’t exist, create it!).

6. go to http://path-to-phpbb3/phpbb3tobbpress.php and start converting your board.

7. voila .. all your data is converted to bbpress tables, go to your bbpress installation and login. don’t forget to visit admin->manage->recount to make sure your converted board is updated.

As said before, it is advised to copy your phpbb3 forum to a localhost installation and make the conversion as stated in the steps above, this way if you have big forum with thousands of posts, it is easier and safer to run the conversion on localhost.

Hope this helps and thanx to the original poster.

Tested by http://numediastudio.com for http://forumcine.ma

[kevinjohngallagher]

woah woah woah (sweet child of mine)

There’s no doubt we’re doing exceptionally well in how far we’ve come with this, especially given that the Project Lead left 4 months ago, but we’re not anywhere near that stage.

1.0 had 10 alphas (though pre-Alpha6 was massively different to Alpha7-10).

It had no beta’s. It had 1 RC which was turned into an actual release 7 days later with minimal bug fixes, and we’ve been stuck with these bugs for a year because of it.

If you want to help, and it’s awesome you do, please download the latest nightly build from the Trunk and report bugs like mad.

There should be no real alpha/beta/rc packages until we’ve squashed all the existing tickets (possible exception to backPress reliant ones).

The moer bugs we find now (in the nightly builds) the more confident we’ll all be in the Alphas that we put out there

And Gautam, excellent work once again.

[Rich Pedley]

can a release candidate be put together for general testing?

[noepiyu]

i upgraded my bbPress to latest version 1.0. But i have a warning message:

---

Warning: file_exists(): open_basedir restriction in effect. File(/www/***.org/d/e/n/denemefrm/bb-config-path.php) is not within the allowed path(s): (/www/***.org/d/e/n/denemefrm/htdocs/) in /www/***.org/d/e/n/denemefrm/htdocs/bb-load.php on line 141 Warning: Cannot modify header information – headers already sent by (output started at /www/***.org/d/e/n/denemefrm/htdocs/bb-load.php:141) in /www/***.org/d/e/n/denemefrm/htdocs/bb-includes/backpress/class.wp-auth.php on line 273 Warning: Cannot modify header information – headers already sent by (output started at /www/***.org/d/e/n/denemefrm/htdocs/bb-load.php:141) in /www/***.org/d/e/n/denemefrm/htdocs/bb-includes/backpress/class.wp-auth.php on line 273 Warning: Cannot modify header information – headers already sent by (output started at /www/***.org/d/e/n/denemefrm/htdocs/bb-load.php:141) in /www/***.org/d/e/n/denemefrm/htdocs/bb-includes/backpress/class.wp-auth.php on line 273 Warning: Cannot modify header information – headers already sent by (output started at /www/***.org/d/e/n/denemefrm/htdocs/bb-load.php:141) in /www/***.org/d/e/n/denemefrm/htdocs/bb-includes/backpress/class.wp-auth.php on line 273 Warning: Cannot modify header information – headers already sent by (output started at /www/***.org/d/e/n/denemefrm/htdocs/bb-load.php:141) in /www/***.org/d/e/n/denemefrm/htdocs/bb-includes/functions.bb-pluggable.php on line 232

—-

How can i solve this problem???

[kevinjohngallagher]

Does it work on your development/testing version?

[cmunns1]

shows up on latest discussion page:

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected ‘America/Los_Angeles’ for ‘PDT/-7.0/DST’ instead in /Library/WebServer/Documents/wordpress/_bbpress/bb-includes/functions.bb-formatting.php on line 327

I also can’t login as keymaster for some reason. Any thoughts on this? Password recovery doesn’t work either.

[Gautam Gupta]

I have posted a patch in that ticket, can you test it?

[r-a-y]

@gautam – Haven’t tested this yet, but great work. Glad to see some movement.

Silly question, but it’s possible to turn off anonymous, loginless posting right?

[Arturo]

really good news, in the weekend i begins the test!

[saraw]

Yes, that’s how it’s structured:

my-templates (755)

–promoforums (755)

—-style.css (755)

—-theme .php files (644)

This was working fine on my local testing server (MAMP); is there any other way to import a custom theme (I’m wondering if something is being garbled during the FTP upload)…?

[saraw]

I’m having the same problem with my custom template; I’m using a recent install of bbPress 1.0.2, and have uploaded my theme to the my-templates directory (I tried it in the bb-templates directory too, as a test) and have checked the directory structure to make sure that’s ok, my style.css header is correct, my permissions seem to be correct (755 on all folders/sub-folders, 644 on all files), there is no mod_security going on with my host… and yet, my theme does not appear in the “appearance” panel of the admin.

Are there any other details I should check? I need to get this sorted or my client will be unhappy.

Thanks –

Sara

[Gautam Gupta]

Because your server would be having the latest version of PHP.

[Gautam Gupta]

Just an update on what’s going on Trac – bbPress 1.0.3 milestone has 3 tickets left (all the tickets have patches and 1 depends on a BackPress ticket), while 1.1 milestone has 4 tickets left (2 have patches, and 2 need patches). There’s also another BackPress ticket that needs to be fixed (which also has a patch). That means that bbPress 1.1 is very near to its release!

How can you help?

1. Checkout a copy of bbPress trunk version via SVN and test it.
2. Test the patches of the open tickets.
3. Contribute patches to the tickets which don’t have one.

What’s new in bbPress 1.1?

1. Email subscriptions
2. Loginless posting
3. Better administration of posts and topics
4. Better search and statistics
5. Bug fixes. Some critical ones are – #1261 (RSS feeds errors), #1146 (faster recount functions), #1150 (undelete topic error).
6. Better tags administration (if #1243 goes in)

Some tickets that missed 1.1 milestone are #960 (better user administration) and #1277 (kakumei cleanup) even though they had patches but could cause errors as they were huge changes and needed more testing. They might get into 1.2 though.

Cross Posted Here on the bbdevel blog – http://bbdevel.wordpress.com/2010/06/22/bbpress-1-point-1-maybe-soon/

[Ashish Kumar (Ashfame)]

This site is running 2441 at the moment and the latest changeset is 2442 at the time of writing this post.

[kevinjohngallagher]

You’re not an idiot mate, but this is where bbPress starts to struggle a bit – especially with no documentation.

You want to make a call to the Database directly via SQL (SQLECT * FROM blah blah blah), but thre is no quick fix. You can use the $bbdb class to connect to the database.

If your’e still struggling, do a hunt for $bbdb with here on google. Remember that search on this site su… has many inbuilt features that are not bugs

[shsn]

Not to sound like an idiot, but how would I do that? Any simple way?

thanks in advance

[kevinjohngallagher]

Anybody? Nobody?

venividi,

you give us less than 24 hours to answer.

WordPress3.0’s been out for about 2-3 days, and you’re talking about something not working that has never been supported.

Automattic made no effort to make sure things were cool with bbPress before releasing so we’re all going to have to wait until we get more reports in.

Lets not forget that a large number of people wait until the first (if not second) bug fix release is made availible before chaning over.

Patience is needed my friend, just don’t push untested just release software onto a live enviroment and you’ll be fine – and we know you didn’t do that because that would be so silly ;-]

[kevinjohngallagher]

Yeah, basically the global variable you’re using $forum/$topic/$posts etc. have been codedin such a way that they can only be iterated trhough once.

You’ll need ot make a separat SQL/data call for each bit of info that you need.

[shsn]

I have made a second latest discussion panel (in the header of my design), but it is an exact replica of the other latest discussion panel found in the front page. So if I want my new panel to have only 5 latest discussions, I have to also limit the original latest discussion to also have 5 latest discussions via the admin section of the website in the settings page. Also when I click on the next page of the latest discussions, my new panel also shows the next page, instead of showing a constant number of latest topics.

Any ideas on how to fix this?

thank in advance

[kevinjohngallagher]

Gautam,

This won’t be a short post, but I truly wish for you to know this comes from a place of respect and admiration for both your code and your commitment to bbPress and it’s community.

Please, let us focus on what we need to get the next release finished.

We simply cannot fix everything.

We have to prioritise.

Matt, who is the project lead, did the prioritising for us.

• Critical Bug fixes
• Email notifications
• Anonymous posting.

That’s it. Once those are ready, we release.

Matt himself said that the focus should not be on bugs, but on the 2 new features and critical only bugs.

It’s not for me to tell you, nor even ask, what you should be working on; but please allow me to help you. As a developer, and someone who loves this project, you are trying your best to solve as many problems as possible. It is so admirable, and we all appreciate your efforts. But in the long run, you are only going to slow us down. How?

Bugs.

When a developer writes code, especially large pieces of code, there are bugs. It is the nature of the beast. We have very very few testers, very very few people who download the latest trunk version to test. The chances of us catching anything but the most obvious of bugs are slim.

Take the new default Kakumei theme you’ve included. While I’m in total agreement that the default theme needs changing, this is not the way forward. You’ve changed about 400 lines of code, and there will be bugs. Given that a new Kakumei theme isn’t part of the feature list, those bugs are going to count against us, not be a positive.

You’re giving theme developers slighty more tools to work with, but all you’re giving the average user and the new users is an untested theme that looks like the old one (which looks crap still).

Regardless of how awesome your code is, and it looks brilliant, the best we can hope for with it is that it doesn’t go badly. If it works flawlessly, no-one will notice. There is no winning scenario here. No part of releasing a new theme in 1.1 will be beneficial, especially as it looks identical to the old one.

Sadly the same can be said for your efforts to totally rewrite the entire tag system. I’ve absolutely no doubt, 100%, that your code and functionality would be amazing. But right now, it works. Same for your Mass Delete / User handling functionality. etc etc

There comes a time when Less is More.

Less code changes means less new bugs, means less “OMG it’s taken a year to come out and it’s still terrible” posts. Less code means less to test, it might mean more bugs are caught, it means less bugs released. Less code means we can release quicker. Less code means less testing time.

Realistically, we have only 2 bugs in 1.0.3 ( #1228, #1276 ) and 2 bugs in 1.1 ( #1244, #1268 ) that are stopping us from releasing this thing to alpha for testing. Thats great work, even if #1244 looks like it will be a lot of work.

The other bugs (#538, #1183, #1277, #1243 ) are all “nice to haves”, and yet somehow contain about 800-1000 lines of code with changes. There has to be some form of Risk Assesment here bro. 1000 lines of code changed with no functionality to forum users, but instead increases the chances of bugs?? Risky, very risky.

Look, BackPress might never include the fix we need to get this thing working, so lets focus on the outstanding bugs that are blocking us, and lets worry about the others after. Because lets be honest, if we’re building a new theme for bbPress, it’s should look nothing like KAKumei (emphasis on KAK)

[kevinjohngallagher]

The “subscribe to topic” link is on the left hand side, above Tags.

It just doesn’t work. One of the joys of releasing a broken untested theme.

[kevinjohngallagher]

No question is dumb mate, though the idea of testing your users to get 9/10 questions right before allowing them to talk on a forum might be very close to it

It’s just a SQL call.

You can store the information you need in the “_meta” table.

Basically don’t think about it as a bbPress plugin, just code the PHP as you would if it was a website you’d built yourself.

[kevinjohngallagher]

Seems valid mate, or you could not bother with the role chaning bit, and just test for a meta_key/meta_value pair in the database.