[shansta]

Hello,

I think I have these two integrated and working but seems to be a problem with the bbpress keymaster having access to the wp-admin area. The only solution I have so far is to have 2 admins…

one for WP ( a:1:{s:13:”administrator”;b:1;} )

&

one for BB ( a:1:{s:9:”keymaster”;b:1;} )

I have set the role in the bbpress-admin for wp-admins to be keymasters but it doesn’t seem to work…

Am I doing something wrong?

Thanks

[radovanx]

When I installed bbpress I am trying login in to administration but its imposible with this code

Deprecated: Assigning the return value of new by reference is deprecated in C:xampplitehtdocsbbpressbb-settings.php on line 186

Deprecated: Assigning the return value of new by reference is deprecated in C:xampplitehtdocsbbpressbb-includesbackpressfunctions.wp-object-cache.php on line 108

Deprecated: Assigning the return value of new by reference is deprecated in C:xampplitehtdocsbbpressbb-includesbackpresspomomo.php on line 171

Deprecated: Assigning the return value of new by reference is deprecated in C:xampplitehtdocsbbpressbb-includesfunctions.bb-l10n.php on line 484

Deprecated: Assigning the return value of new by reference is deprecated in C:xampplitehtdocsbbpressbb-includesbackpressclass.wp-taxonomy.php on line 581

Warning: Cannot modify header information – headers already sent by (output started at C:xampplitehtdocsbbpressbb-settings.php:186) in C:xampplitehtdocsbbpressbb-includesbackpressclass.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at C:xampplitehtdocsbbpressbb-settings.php:186) in C:xampplitehtdocsbbpressbb-includesbackpressclass.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at C:xampplitehtdocsbbpressbb-settings.php:186) in C:xampplitehtdocsbbpressbb-includesbackpressclass.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at C:xampplitehtdocsbbpressbb-settings.php:186) in C:xampplitehtdocsbbpressbb-includesbackpressclass.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at C:xampplitehtdocsbbpressbb-settings.php:186) in C:xampplitehtdocsbbpressbb-includesbackpressclass.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at C:xampplitehtdocsbbpressbb-settings.php:186) in C:xampplitehtdocsbbpressbb-includesfunctions.bb-pluggable.php on line 232

[Nuul]

I think there is more going on behind the scenes then we know. Sam leaving all of a sudden, no one continuing this project and no reaction from any wordpress developper (or Matt). Seems like they are letting this project die (and just gonna buy simplepress in the near future??).

It’s a shame…

For _ck_ any change we can acces the forum (but lock all topics and dont allow new ones to be created) so we can still benefit from the knowledge already posted there?

Greetz Nuul,

Damn, just as I am on the edge of releasing a cool new plugin

[Olaf Lederer]

… just checked simplepress, looks much more like a forum than bbpress

[Olaf Lederer]

Thanks Steven, for posting this announcement.

Really bad that it looks like that bbpress has not some great future.

Actually I think about to convert my bbpress forum into a wordpress site using a theme that looks like a forum

Can’t be so difficult, the whole structure of bbpress looks too much like wordpress

(… another XX hours lost in the development of bbpress plugins)

[Steven Hodson]

I just tried to drop by bbShowcase and found this waiting for anyone visiting

---

The bbPress Showcase has been discontinued.

The removal of Sam Bauers and the halting of bbpress.org 2.0

was a clear and final sign that there is no interest in allowing

bbPress to become a mature, robust program and community.

By now bbPress 1.5 could have been in alpha but instead

bbPress development has been deliberately stagnated,

which should be a very alarming warning to everyone.

In addition, bbShowcase had only six donations in 2009,

which indicated to me there was no interest in my work.

My code will remain on bbpress.org as open source GPL

for those that wish to use it, however I caution you to

consider bbPress’s lack of leadership before continuing to use it.

---

[frooyo]

Also, how to I file a code patchset to fix this bug for others?

[frooyo]

@hatter

Changing $empty_format = ””;

to

$empty_format = ”/”;

make’s it work.

MANY, MANY thanks. Anyway of me being able to make this work now without having to modify the core bbPress code? My concern is that I want to be able to upgrade bbPress in the future without having to remember I made this modification to the core function.

[hatter]

Ok, I think I see the problem now. If you look at the source code for the page 1 link, it generates an empty href element, which by default will link back to the current page. This is generated in the bb_paginate_links function in bb-includesfunctions.bb-core.php. Can you try something real quick, as a possible fix? Around line 244, you will see the following:

$empty_format = ”;

Change this to:

$empty_format = ‘/’;

This will generate an href of “/” which should lead to the root of your forum. Please let us know if this works.

[hatter]

This may sound kinda stupid, but after looking at the code, can you add topics to your forum to create a page 3 to see if you still have the issue? I’m just wondering if this issue only occurs when you only have 2 pages worth of topics. Can you test this real quick to see if this is the case? I will keep looking into it in the mean time.

[hatter]

Not sure why your site would break with that code. Did you add it to the end of the file, before the ?> ? Also, have you tried turning off permalinks to see if that works for your site?

[frooyo]

@hatter

I went into the Admin panel and re-selected to use the “example.com/forums/first-forum” type of permalinks.

This then regenerated the appropriate code for my .htaccess file; HOWEVER, I’m still experiencing the exact same issues.

Also, when I added the “$bb->mod_rewrite = false;” code to my bb-config.php file, my entire site broke. So I remove the “$bb->mod_rewrite = false;” code.

[Steven Hodson]

First off I figured out what the problem is. It seems that when you have a self-contained plugin folder installed into the bb-plugins and my-plugins folder the link to that plugin in the Admin area to active (and I imagine de-activate) has a double backslash between the plugin folder name and the actual file

Example:

…. plugins.php?plugin_request=all&action=activate&plugin=user%23smiley-choice\bb-schoice.php&_wp ….

as you can see there is a double backslash between the ‘smiley-choice’ folder name and the actual file ‘bb-schoice.php.

Now @Nightgunner5 I had a look at the patch file code .. my question is what file is this added to?

[frooyo]

@hatter

The code you have above is exactly what I have.

You can view the code live at: http://bit.ly/8yfVim

Notice this is Page 2, when the “Previous” link does not work correct. The “Previous” link links to the same page (page 2) and not the frontpage.

[hatter]

Are you using the kakumei template? Here is what I have in my front-page.php file:

<?php endforeach; endif; // $topics ?>

</table>

<?php bb_latest_topics_pages( array( ‘before’ => ‘<div class=”nav”>’, ‘after’ => ‘</div>’ ) ); ?>

<?php endif; // $topics or $super_stickies ?>

and have not had any issues.

Can you paste the html code generated for your links to provide more information?

[frooyo]

I’m running bbPress 1.0.2.

I’m having problems with the “PREVIOUS” link when using the “bb_latest_topics_pages” function.

I have the following code on my frontpage.php

---

<?php endforeach; endif; // $topics ?>

<?php bb_latest_topics_pages( array( ‘before’ => ‘<div class=”nav”>’, ‘after’ => ‘</

div>’ ) ); ?>

---

It display paged frontpage topic links (1, 2, 3, Next) but whenever I’m on a page other than the frontpage … for example, Page 2, both the Previous and Page 1 link points to the current page and not the previous page.

[TimBurden]

adam’s fix will mean backslashes will be stored in the database. Worse, on upgrade, his changes will be lost and there all the backslashes will be.

Better to do this as a plugin, and filtering content before it goes in the db.

Just write a plugin, upload it and activate it. Like this:

<?php

/*

Plugin Name: Strip Slashes

*/

add_filter('pre_topic_title', 'stripslashes', 40);

add_filter('pre_post', 'stripslashes', 40);

add_filter('bb_add_topic_tags', 'stripslashes', 40);

?>

[johnhiler]

Ah wow, only six donations huh.

_ck_ already said three months ago that if things didn’t change by December, she wouldn’t be doing plugins upgrades for 1.0:

http://bbshowcase.org/forums/topic/suggestion-to-ck-regarding-donations#post-1641

I can’t understand why Automattic doesn’t send her a $5-10k donation… bbPress would lose so much momentum if she stopped contributing.

[buddha-trance]

@Nightgunner5 – Thank you for the tip. I will try to do as you suggest. It’s so much better to leave the core files in their original state. I have never tried to create a plugin, this is a good reason to start!

[soundgnome]

Hey there, just had an issue with the “favorites” RSS and wanted to share my solution in case anyone else was having the same problem. Maybe it was just a Firefox thing, but the favorites URL (e.g., rss.php?profile=1) was interpreted as “unformatted XML”–there was an error message and the entire markup was displayed. I eventually discovered this was caused by an <a> tag inside the channel’s <link> tag. By changing the “bb_get_profile_link” call to a “get_user_profile_link” call in rss.php I got the URL without the tag, and the feed was interpreted correctly.

Incidentally, I also noticed a couple other things about the script that seemed a bit off–

1) There are a number of calls to “die()” if the feed turns out to be empty–seems like either an empty feed or an error page would be preferable to this silent failure.

2) The “bb_send_304()” call doesn’t take into account that the feed itself may have changed recently, e.g. threads added to a “favorites” list won’t show up until activity on one of the threads causes the feed to be refreshed. (Which is not totally illogical, but it can be confusing for the user to add a favorite, refresh the feed, and still not see the newly-added thread.)

I thought about working up a patch to address these issues, but decided to post this first–maybe the script’s working exactly as intended and I’m just not understanding it correctly.

[buddha-trance]

I am sharing this, just in case it may help someone else looking to implement this feature. There is a great plugin that does this, bbAvatars, but it was interfering with other functions I wanted to implement, so I had to find a workaround (bbPress 1.0.2).

With the premise that I really don’t like to edit core files, because you have to remember to edit them each time you upgrade, this time I had no choice, as any avatar plugin I tried did not work out for my purposes. There are a few simple steps you can use to set your own custom avatar, when users have not set a gravatar account.

1 – I have noticed that the “blank” choice in the settings is the only one that refers to an internal image, so you just want the code to point to your own custom image, rather than “blank.gif” (which may be also used for other calls, so I wanted to leave that one alone and not replace it with another custom blank).

In “bb-includes”, look for the file “functions.bb-pluggable.php”, and edit around line 895, where it says

case 'blank':

$default = bb_get_uri( 'bb-admin/images/blank.gif', null, BB_URI_CONTEXT_IMG_SRC );

and change blank.gif with your image, default.jpg or any other name.

2 – Upload your custom image in bb-admin/images (if you store it somewhere else, change the path in the code above accordingly).

3 – In your Admin Dashboard –> Settings –> Discussions, set the choice to “blank”.

Voila!!!!

To change the avatar size from the bbpress default size, in post.php of your templates, look for

<?php post_author_avatar_link(); ?>

and add the number of pixels inside (), for example:

<?php post_author_avatar_link(80); ?>

Hope this helps!

[sockmoney]

I’m a new bbPress user for about 10 months now. I’ve been promoting bbPress in all the other forums I participate in. Love the product and would love to help out in any capacity I could.

I work for myself as a web publisher. I’m a developer at heart (Computer Engineer), but I mostly do community management and marketing these days.

Would not even know where to begin in regards to where I could help. I would like to see the product get a bit more mainstream usage. Every forum I bring it up in or recommend it, no one seems to know anything about it. I find myself sticking up for it against the big hitters like vBulletin, etc. Perhaps a volunteer marketing/advocate role might be useful…

Regards,

Max

[chrishajer]

2. – apparently none is just shorthand for noindex, nofollow. I’ve always explicitly set them, and there’s really just 4 combinations.

index, follow

index, nofollow

noindex, follow

noindex, nofollow

In any case, looks like you sorted that.

Never having tried to do what you’re doing, I’m not sure what the answer is to making the Hidden Forums plugin work for you.

Making the whole installation require a login is not that big a deal. Sometimes you can protect a whole directory in your host’s control panel. The bigger problem (for me) is getting the password to everyone you want to have it, unless it’s a group that communicates in other ways, then you can distribute it there.

[yaysloths]

1. Thanks for the lower-case tip; actually not sure how they ended up in all caps. I’ll blame it on the cat.
2. I hadn’t heard of robots=none either, but a fairly net-savvy friend said it was easier than entering the various individual instructions (since apparently there are some obscure ones besides noindex, nofollow?). A Google search turns up pages that seem to agree (see # 4), but maybe I should change it back to be safe.
3. The intranet idea is a neat one, but I think it’s beyond the scope of my capabilities right now (inasmuch as I have no idea how to go about it). I think I’d feel ok with just the Hidden Forums plugin, but I don’t know how to configure things such that it doesn’t keep crashing the site when someone not authorized (or not authorized yet) tries to log in. I don’t know PHP well enough to manipulate the code such that a person would just be directed to a “sorry, this site is private” page instead of causing the infinite redirect loop. Bummer.

[chrishajer]

I would use the Hidden Forums plugin.

For the meta tags, since bbPress tries to use XHTML 1.1 strict, you should make those lowercase and self-closed:

<meta name="robots" content="noindex, nofollow" />

<meta http-equiv="cache-control" content="no-cache" />

<meta http-equiv="pragma" content="no-cache" />

Also, I’ve never heard of robots =none – read up on that to be sure you have it right. noindex, nofollow is how I’ve seen it.

The meta robots tag and the robots.txt just tell search engines that listen to not index the content. Some search engines still might index the content if they don’t obey the robots ‘standards’. So, you need to ensure the content is not visible to anyone unless that individual is logged in. I would use hidden forums for that. Or password protect the whole installation, like an intranet, and give everyone in your group that login.