Thanks. I added this to the header.php and ran some diagnostics.
<meta name=”description” content=”<?php if ( is_single() ) {
single_post_title(”, true);
} else {
bloginfo(‘name’); echo ” – “; bloginfo(‘description’);
}
?>” />
This appears to solve my Tag Description problems, but it creates another.
I get a php error when accessing the forum
Fatal error: Call to undefined function is_single() in /home/xxx/public_html/Forum/bbpress/bb-templates/kakumei/header.php on line 16
Would anyone be so kind as to help identify a work around?
Thanks. I added this to the header.php and ran some diagnostics.
<meta name=”description” content=”<?php if ( is_single() ) {
single_post_title(”, true);
} else {
bloginfo(‘name’); echo ” – “; bloginfo(‘description’);
}
?>” />
This appears to solve my Tag Description problems, but it creates another.
I get a php error when accessing the forum
Fatal error: Call to undefined function is_single() in /home/xxx/public_html/Forum/bbpress/bb-templates/kakumei/header.php on line 16
Would anyone be so kind as to help identify a work around?
I checked the syntax of the RewriteEngine. The redirect works:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^forum.mysite.com$
RewriteRule (.*)$ http://www.forum.mysite.com/$1 [R=301,L]
I am not using WP only bbPress installation.
The problem is the login into ppPress.
bbPress login does not recognize: http://www.forum.mysite/bb-login.php.
It needs: http://forum.mysite.com/bb-login.php.
I tried permalink settings none and name based, same issue.
Does anyone uses redirect and how can I eliminate “double” content and redirect permanently to http://www.forum.mysite.com?
I checked the syntax of the RewriteEngine. The redirect works:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^forum.mysite.com$
RewriteRule (.*)$ http://www.forum.mysite.com/$1 [R=301,L]
I am not using WP only bbPress installation.
The problem is the login into ppPress.
bbPress login does not recognize: http://www.forum.mysite/bb-login.php.
It needs: http://forum.mysite.com/bb-login.php.
I tried permalink settings none and name based, same issue.
Does anyone uses redirect and how can I eliminate “double” content and redirect permanently to http://www.forum.mysite.com?
Jumping the gun a little here but…
When/if the default theme for the bbpress plugin is setup, can it be more like here or the wordpress forum and absolutly nothing like the buddypress forum? (please!!)
Did you do a WordPress/bbPress integration?
Did you do a WordPress/bbPress integration?
Hi, i installed all, (wordpress-bbpress) in the same directori, (/test/wordpress – /test/bbpress), and when i try get into the admin panel of bbpres i only get a redirection to the index of my forum. (i put /test/bbpress/bb-admin/index.php and i will be redirected to /test/bbpress/index.php).
What i am doing wrong??
So much thanks!
Well nevermind, just saw this thread
not working in buddypress
I’ll try over there again…
Well nevermind, just saw this thread
not working in buddypress
I’ll try over there again…
Hello,
I’m running bbpress which was installed by Buddypress and I’m having an issue. I originally installed buddypress on GoDaddy hosting and everything was working well. I switched over to a VPS about a week ago and everything works except for the forum. When I try to go to the url http://www.intennis.com/forums I am redirected to the homepage.
Now I’ve tried deleting bb-confing.php and dropping the tables out of my DB, which appears to clean everything out. Then I reinstalled the forums via BuddyPress and I still get the same redirection error.
In bb-config.php it has the line which sets the uri of “Forums” to /wp-content/plugins/buddypress/bp-forums/bbpress/. I’ve tried to check the server logs to see whats going on but I just see a GET for /forums and a GET for /. I’m really at a loss, if someone could give me an idea of what to look at I’d greatly appreciate it.
Thanks
Any idea how to remedy this issue?
I have tried everything and cannot get passed this. Having the same exact problem after changing the TZ to UTC-5.
Any help would be greatly appreciated!
FYI, using the latest version 1.0.2
That’s because there’s a bug in the plugin. Or rather the plugin was probably written for an earlier version of bbpress.
To fix the “redirect” issue, you need to edit avatar-upload.php and change line 7 from:
bb_auth(); // logged in?
to:
bb_auth( 'logged_in' ); // logged in?
Now it’s off to do more testing.
That’s because there’s a bug in the plugin. Or rather the plugin was probably written for an earlier version of bbpress.
To fix the “redirect” issue, you need to edit avatar-upload.php and change line 7 from:
bb_auth(); // logged in?
to:
bb_auth( 'logged_in' ); // logged in?
Now it’s off to do more testing.
I am wondering what the risk is still of installing at this point and losing all of the existing posts, at a later date due to a new release?
Will I be able to carry my current installation over to the new plugin version? With all users and posts intact?
Will I be able to carry my current installation over to the new plugin version? With all users and posts intact?
I certainly could use a sidebar in my BBPress. If I was able to install WordPress widgets in it.
So without all this, it´s mostly the header thats new..?
I certainly could use a sidebar in my BBPress. If I was able to install WordPress widgets in it.
So without all this, it´s mostly the header thats new..?
Thanks, Zaerl. I followed your advice and modified the error reporting. I just replaced
error_reporting( E_ALL ^ E_NOTICE );
with
error_reporting(0);
I know this could cause some headaches later on, but I’m not sure exactly how to make it specific, and in what way to modify the reporting. It definitely works, though!
Thanks, Zaerl. I followed your advice and modified the error reporting. I just replaced
error_reporting( E_ALL ^ E_NOTICE );
with
error_reporting(0);
I know this could cause some headaches later on, but I’m not sure exactly how to make it specific, and in what way to modify the reporting. It definitely works, though!
Actually speaking PHP core function parse_url does generate a E_WARNING when the URL cannot be parsed. This happens if the server is running PHP < 5.3.3.
You really should turn off error reporting modifying bb-load.php line 25 (the error_reporting( E_ALL ^ E_NOTICE ); line).
After a quick (very quick) look at bbPress code it seems that they are using urlencode in urlencode_deep. I think that the right approach for the “re” GET variable is to use rawurlencode like it happens with “_wp_http_referer”.
Actually speaking PHP core function parse_url does generate a E_WARNING when the URL cannot be parsed. This happens if the server is running PHP < 5.3.3.
You really should turn off error reporting modifying bb-load.php line 25 (the error_reporting( E_ALL ^ E_NOTICE ); line).
After a quick (very quick) look at bbPress code it seems that they are using urlencode in urlencode_deep. I think that the right approach for the “re” GET variable is to use rawurlencode like it happens with “_wp_http_referer”.
So far I’ve had no issues just adding the contents of functions.php, all the new template files and the tag to my existing theme.