Those versions are compatible, so I don’t think that is the cause of your problem.
Does the table it is complaining about, ‘addiva_bbpress.wp_users’ actually exist, or no?
@chrishajer: I didn’t the diff cause I’m starting over with the forum – no data to care. So after the error comes I just removed all files and elimI searched and inated all tables from database. I should make some tests and take the diff.
@balgo: Yes, is a php error, but is called from a script in functions.core.php. There’s no results relevant to actual versions of bbpress neither functions.core file.
@zappoman: What let me really confused, please correct me if I’m wrong, is that I got error installing from “svn co http://svn.automattic.com/bbpress/tags/1.0-alpha-1/” but had no errors with a installations from “bbPress 1.0 Alpha (latest-alpha.zip)” in the download page. Since is tagged, is the same package right?
Thanks all your attention guys.
For the record, ThemePress integrated theme for bbPress+WordPress can be found in the middle of this page:
http://www.adityanaik.com/integratepress-part-i/
direct:
http://www.adityanaik.com/download/ThemePress-v-1.zip
it’s probably a bit outdated because it was meant for version 0.8 but should still work with a few modifications (for example his instructions say “config.php” when it’s now “bb-config.php” and the plugins he recommends are no longer required and might actually make things not work)
I was seeing something similar and I found it relates to ADMIN_COOKIE_PATH in wp, and $bb->wp_admin_cookie_path in bbPress.
In my case, I had bbPress located at domain.tld/forum/ for a wp install at domain.tld. If I set the wp ADMIN_COOKIE_PATH to /wp-admin/ as usual, then I got this behavior… but if instead I set it to “/” then things work fine.
This may or may not be related to the issue you are seeing.
I also have a similar problem. I installed Alpha 1.0 with a WP 2.6.1 install – when logging into WP now it just goes back to the login screen again, can never reach /wp-admin/. BBpress for me though, works fine at the login (but interestingly still can’t get to /wp-admin/ when logged in through BBpress – wasn’t it supposed to be integrated?)
Just a quick question here, not sure if this is the right thread though.
I have WP 2.6.1, and last night installed bbpress 1.0 alpha.
Now when I log in this morning I click the button to ‘Log in’ and it redirects me back to the login page. The bbpress installation however, I can login to as normal.
better not do it that way, as updates will break your work. create an .htaccess and put the following in:
Redirect 301 /yourbbpressdirectory/register.php http://yourdomain.com/yourwordpressdirectory/wp-login.php?action=register
Have I used the wrong version of bbpress?
Is there a file I can ftp down and alter so that we can get working again? How do people get around this brick wall?
Thanks Chris, I have filed a ticket on another issue I found, and I will file a ticket for this. But I’m more curious to find out if I’m really the only one seeing this issue. It seems like a pretty obvious issue, so I’m surprised no one else has noticed it… which leads me to believe that I must have done something wrong.
As a developer, I hate when people file bugs before looking for a minimal reproduce case… and so I was just trying to ask if someone else has seen this before I file a bug ticket.
Guys,
Something really strange in this problem, only happens when I do a SVN install.
Errors to:
svn co http://svn.automattic.com/bbpress/tags/1.0-alpha-1/ .
svn co http://svn.automattic.com/bbpress/trunk/ .
But if I download (wget) latest.zip or latest-alpha.zip extract and install it will work without the mentioned error. omg –confused–
Yes, bbsync is the closest to this right now. I imagine you could get a lot of ideas looking at that plugin.
If you have an issue with the alpha release, please file a ticket at trac.
https://trac.bbpress.org/newticket
You will need to log in before you can file a ticket. Be sure to choose the correct version when submitting the ticket.
If you have an issue with the alpha release, please file a ticket at trac.
https://trac.bbpress.org/newticket
You will need to log in before you can file a ticket. Be sure to choose the correct version when submitting the ticket.
Ok, more of a clue here…
It looks like the insert into term_taxonomy is failing during the upgrade process.
it appears as if, bb_term_taxonomy has a ‘description’ field which is NOT NULL in the schema:
// term_taxonomy
$bb_queries['term_taxonomy'] = "CREATE TABLE IF NOT EXISTS $bbdb->term_taxonomy (
term_taxonomy_id bigint(20) NOT NULL auto_increment,
term_id bigint(20) NOT NULL default 0,
taxonomy varchar(32) NOT NULL default '',
description longtext NOT NULL,
parent bigint(20) NOT NULL default 0,
count bigint(20) NOT NULL default 0,
PRIMARY KEY (term_taxonomy_id),
UNIQUE KEY term_id_taxonomy (term_id, taxonomy)
);";
but the upgrade code…
$bbdb->insert( $bbdb->term_taxonomy, array(
'term_id' => $term_id,
'taxonomy' => 'bb_topic_tag'
) );
does not set a description, so this insert is failing.
Not sure how this could be working for anyone else…
Am I really the only one seeing this?
digging deeper…
looks like something went wrong in the upgrade process… and tags didn’t get migrated properly into the new term_taxonomy structure.
bb_terms appears to have been filled.
bb_term_relationships has a bunch of rows.
But… bb_term_taxonomy is empty…
There will be a sort of super plugin that you will be able to integrate into bbPress to get most of the functionality of TalkPress. The working name for the project is “bbPress Channels”. It will be released after TalkPress.
I’d like to add a comment system to MediaWiki using bbPress as the backend.
I imagine it’d work like the following:
1. each mediawiki creates a bbpress topic in a specific forum
2. if logged in, users can comment from the mediawiki page.
anyone have any clues to this? is bbsync the closest system to this at the moment?
We have debated adding the wp-mail class to bbPress to get this functionality built in, but we balked at the sheer size of the code. What is a good lightweight replacement for php-mailer that we can consider adding to backpress?
Are tags expected to be working on the 1.0 alpha code?
I am playing around with the system, and it it appears as if tags are not being displayed. the bb_tag_heat_map() is displaying nothing, bb_get_top_tags() is returning an empty array. Individual posts don’t show tags either.
I am assuming this is related to the new taxonomy code… not sure if I did the upgrade incorrectly or what. When I logged into the admin system the first time, it did do a DB upgrade.
If there is no secure salt in WordPress then you don’t need one in bbPress. I think it says that in the note on that field in the installer.
Everything works on a localhost install, but when I try install on dreamhost I get the following error:
Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name](). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /bb-includes/backpress/functions.core.php on line 499
The message stays on the top of page, above header, seems that I can use everything but the message stays there. How can I get ride of this.
SVN INFO:
$ svn info
Path: URL: http://svn.automattic.com/bbpress/trunk
Repository Root: http://svn.automattic.com/bbpress
Repository UUID: 9866e705-20ec-0310-96e7-cbb4277adcfb
Revision: 1651
Node Kind: directory
Schedule: normal
Last Changed Author: sambauers
Last Changed Rev: 1651
Last Changed Date: 2008-08-13 12:13:00 -0700 (Wed, 13 Aug 2008)
Thanks,
Joel Teixeira
This is fixed in trunk and will be fixed in the next alpha release which will probably be in the next couple of days.
https://trac.bbpress.org/ticket/924
Let me add that I’m doing all my testing/installing locally using Xampp. https://trac.bbpress.org/ticket/928 made me think that maybe I’m having the plugin issue because of this problem? Just a shot in the dark perhaps? I think I’ll try uploading the latest trunk to my website (run on a unix server) tonight and see if it’s different in that environment.
