[@kawauso Member 15 years, 1 month ago]

Do you actually mean on your blog or on a given topic? Could you elaborate more on exactly what you’re trying to accomplish?

[@kawauso Member 15 years, 1 month ago]

I can’t say I’ve used bbratings, but knowing IE, it’s probably terrible CSS or JavaScript support in the browser.

[@kawauso Member 15 years, 1 month ago]

I have to agree it’d be good for bbPress to add support for more basic forum functions like merging topics. As it stands, it’s rather silly to need plugins for such basic things. The majority of use does seem to be with bbPress as part of a community package with buddyPress and WordPress though.

It’d be nice too if WordPress (plugin) support could be implemented through an interface layer or something similar that could be added as a plugin or similar to bbPress when it was installed via WordPress, so keeping the core codebase as clean as possible.

bbPress 1.0 was already written to use BackPress functions (WordPress essentially) so I’d imagine it’d just be a case of changing how it outputs content and handles URLs when under WordPress.

[@kawauso Member 15 years, 1 month ago]

michayu:

1. SimplePress looks horrible, and the cleaner bbPress codebase is, the better. It also implements a lot of what in bbPress mentality would be plugin-based.

2. vBulletin is clunky and the opposite of what bbPress aims to be (light, adaptable, etc.)

3. WordPress IS a blogging platform. It has supplementary CMS features such as pages, and can be adapted into a CMS, but it’s primary focus and purpose is blogging. I pray it never gets turned into yet another CMS (and look on discussions on the WordPress support forums about its current shortcomings when used as a CMS if you want proof it’s not one).

[@kawauso Member 15 years, 1 month ago]

Take out the whitespace from the plugin PHP file(s), and try again?

[@kawauso Member 15 years, 1 month ago]

Could you try explaining that again in more clear language?

[@kawauso Member 15 years, 1 month ago]

The Warning message is because forwards depend on sending headers. Different headers are sent automatically however if there’s any text returned by a PHP file that’s loaded, which is a common problem created by whitespace around the <?php ?> tags. If text headers are sent, you can’t send a redirect header, thus the warning and the breaking of redirects.

[@kawauso Member 15 years, 2 months ago]

I’m afraid I don’t take on paid work, since I simply can’t guarantee the time needed to write code on demand, ensure it’s to a standard expected of paid work and to be honest, I don’t need the money anyway.

As I said, I’d be more than happy for someone else to use my code as reference on how to implement such a feature, since it’s pretty much just butchered up parts of core bbPress code, but as it stands I simply don’t have the time to work on the plugin and guarantee it’s to a production standard, paid or not.

As to the requesting login details later part, I think that was requested before, and I did look into doing it, but because of the way bbPress is structured internally, you have to bypass so many checks against the referring page and carry over the post data to be passed later on. Do-able yes, but not really a 5 minute job, since as far as I know you’d still need to re-do the post function as I did previously.

It’s nice to know there’s still interest in this though, and I’ll look into trying to implement it more cleanly later on with requested features. Having pulled and learnt the login and post system once, it should be easier a second time. Really, really wish we had a bbPress codex, so it could be documented more.

[@kawauso Member 15 years, 2 months ago]

You have a space or a line return around your code tags.

[@kawauso Member 15 years, 2 months ago]

I bypassed the activation email requirement for the first post (the one made with the plugin), so the post is added immediately and the registration can be taken of later. Other option is to use an anonymous posting plugin. I’ll be around to do support possibly, and that’s the case with most plugins for bbPress, try looking at how many are abandoned… otherwise, pay someone for support, that’s the only real way to ensure it’s there.

[@kawauso Member 15 years, 2 months ago]

anabelle: The code that I’ve posted is fully working as a proof of concept, so you could use it. I’m not sure if this would ever be implemented into the core code though. I’ll look into re-doing it with an interstatial page at a later point if I have the time.

[@kawauso Member 15 years, 2 months ago]

Since there’s been no other interest and feedback on this plugin, I don’t think I’d be too inclined to try and do that as functionally this is fine. Someone else is quite welcome to use how I modified things as an example for implementing that though, it’d probably be quite easy if you get your head around how things work.

[@kawauso Member 15 years, 2 months ago]

Correct. There’s been various other incidences of this too:

https://bbpress.org/forums/topic/admin-link-doesnt-take-me-to-dashboard

https://bbpress.org/forums/topic/admin-link-redirects-to-front-page

Can’t find any others offhand, but it’s not an isolated matter

[@kawauso Member 15 years, 2 months ago]

If you click on Admin, it redirects back to the bbPress core directory if you’ve logged in on the WordPress side, but works fine if you log in on the bbPress side. Clearing browser cookies has no effect.

[@kawauso Member 15 years, 2 months ago]

I have this problem, always ended up concluding bbPress admin just doesn’t like login cookies set from the WordPress side. It’s a relatively common problem too, so it’s probably worth checking if it’s ever been reported to Trac.

[@kawauso Member 15 years, 2 months ago]

Are you using any/all of the same plugins as the above?

[@kawauso Member 15 years, 2 months ago]

https://trac.bbpress.org/report

That bug sounds oddly familiar, so it might have already been reported, but otherwise, you need to file a bug report on Trac

[@kawauso Member 15 years, 2 months ago]

The words are stored in a file called logged-in.php in your theme.

In Kakumei (the default), it looks like this:

<p class="login">

<?php printf(__('Welcome, %1$s'), bb_get_profile_link(bb_get_current_user_info( 'name' )));?>

<?php bb_admin_link( 'before= | ' );?>

| <?php bb_logout_link(); ?>

</p>

Using __( translates into the appropriate language, and %1$s is a placeholder that gets replaced by the user’s name

Not sure why it’s saying Welcome twice though

[@kawauso Member 15 years, 2 months ago]

This might be a cleaner solution

<?php

switch ( $topic->forum_id ) { // Ignore these forums

case 29:

case 30:

case 18:

case 15:

case 4:

continue 2;

}

?>

or for including only certain forums

switch ( $topic->forum_id ) { // Include only these forums

case 29:

case 30:

case 18:

case 15:

case 4:

break;

default:

continue 2;

}

?>

but using that if statement, you need to change the line

<?php if( $topic->forum_id != 29 && $topic->forum_id != 30 && $topic->forum_id != 18 && $topic->forum_id != 15 && $topic->forum_id != 4 )

and you can find the forum ID from looking at its Edit URL in the admin panel (under Forums)

[@kawauso Member 15 years, 2 months ago]

Normal method is to create a WordPress with the same name (slug), which will load the forums instead and skin the forums to match the WordPress install, either using CSS and modifying the template, or deep integration as well. There isn’t any way to integrate bbPress into a standard WordPress page apart from iframes.

[@kawauso Member 15 years, 2 months ago]

You don’t need to uninstall to move bbPress as such, since it’s not installed in any way apart from the the .htaccess file settings and the database settings.

You need to change the uri setting under bb_meta in the database to the new forum URL, and then change the .htaccess file so it matches the new directory.

The .htaccess file can probably be fixed by turning off Permalinks and then back on. Don’t forget to log out and in again too.

The options might be changeable by using __ck__’s All Options, but I have a feeling the URI isn’t editable from there.

[@kawauso Member 15 years, 2 months ago]

Is it integrated with WordPress? I have this issue in that scenario, only solution is to login in from the bbPress side instead.

[@kawauso Member 15 years, 2 months ago]

Edit the style.css file in the copy, that’s where all the name/description data is stored

[@kawauso Member 15 years, 2 months ago]

Not the cleanest way of doing it no doubt, but I’d use something like this modified version of the breadcrumb function:

<?php

$separator = ' -- ';



if( bb_is_forum() ) :

$trail = '';

$trail_forum = bb_get_forum(get_forum_id());

$current_trail_forum_id = $trail_forum->forum_id;

while ( $trail_forum && $trail_forum->forum_id > 0 ) {

$crumb = $separator;

$crumb .= get_forum_name($trail_forum->forum_id);

$trail = $crumb . $trail;

$trail_forum = bb_get_forum($trail_forum->forum_parent);

}

$title = substr( $trail . $separator . bb_get_option( 'name' ), strlen( $separator ) );

else :

$title = bb_get_title( array( 'separator' => $separator ) );

endif;

?>	<title><?php echo $title?></title>

[@kawauso Member 15 years, 2 months ago]

It’d be better to add width: 500px to the CSS class used by topic titles rather than adding it by instance.