[deadlyhifi]

Have you looked into automating the procedure at all with the PayPal recurring payments system? I was thinking about creating a separate ‘advanced’ roles table, which WP and bbP check to see if that user should have access to certain content.

This table would log the user ID and keep the callback from PayPal, and when their time was set to expire so they would lose access should they cancel their auto renew payments.

[deadlyhifi]

They definitely have a different name.

wordpress_logged_in_TWOdifferentVALUES

tried to do the clear cookies thing in a function but, even though it’s running correctly, the cookie reset is getting ignored. Can’t figure out why

[deadlyhifi]

yeah, the cookie has a completely different name. Thats why I don’t understand the issue, but users are reporting they can’t log in unless they clear their cookies. thanks for your replies anyway, will give this a go.

[deadlyhifi]

Thanks _ck_. I’m sure it’s easy when you know how.

The cookie now has a different name.

my old cookies are:

$bb->authcookie = ‘wordpress_REPLACEDcabef’;

$bb->secure_auth_cookie = ‘wordpress_sec_REPLACEDcabef’;

$bb->logged_in_cookie = ‘wordpress_logged_in_REPLACEDcabef’;

I was messing with

setcookie('wordpress_logged_in_REPLACEDcabef','',time()-3600)

just placing in the head of my page but I get a headers already sent message.

[deadlyhifi]

thanks.

https://wordpress.org/extend/plugins/bbpress-integration/

[deadlyhifi]

excellent. It just came down the interpipes.

Modified: trunk/bb-includes/functions.bb-template.php (2276 => 2277)

thanks for all your hard work!

[deadlyhifi]

nice swan

[deadlyhifi]

Take a look at https://browserlab.adobe.com/ for basic (non interactive) testing.

[deadlyhifi]

Hi infected,

it looks as thought the ‘poststuff’ is the cause of the issue. If I apply a ‘float:right;’ to it everything wraps nicely.

Try moving it within the ‘post’ class, and amending the margins and padding to suit.

[deadlyhifi]

and the secret keys in both config files correspond?

[deadlyhifi]

Is the user-base being shared correctly?

have you checked that the cookies correspond?

[deadlyhifi]

Working Plugins:

• Human Test for bbPress 0.9.1
• Report Post 0.1.4
• Super Search 0.0.3
• C*nsor 0.1
• bbPress Smilies 0.0.7
• BBcode Lite 1.0.3
• BBcode Buttons Toolbar 0.0.9
• Allow Images 0.7.1

[deadlyhifi]

That fixes it instantly. Thanks very much.

[deadlyhifi]

The updated plugin has been working ok except it has major flaws

1 – The user displayname is not being put into the database – therefore all new users appear as a blank when they post.

2 – registration error messages aren’t displayed. (e.g. Invalid email)

The fix was straightforward. The bb_new_user function needed updating as so:

if (!function_exists('bb_new_user')) :

function bb_new_user( $user_login, $user_email, $user_url, $user_status = 0 ) {

global $wp_users_object, $bbdb;



// is_email check + dns

if ( !$user_email = bb_verify_email( $user_email ) )

return new WP_Error( 'user_email', __( 'Invalid email address' ), $user_email );



if ( !$user_login = sanitize_user( $user_login, true ) )

return new WP_Error( 'user_login', __( 'Invalid username' ), $user_login );



// user_status = 1 means the user has not yet been verified

$user_status = is_numeric($user_status) ? (int) $user_status : 0;



$user_nicename = $_user_nicename = bb_user_nicename_sanitize( $user_login );

if ( strlen( $_user_nicename ) < 1 )

return new WP_Error( 'user_login', __( 'Invalid username' ), $user_login );



while ( is_numeric($user_nicename) || $existing_user = bb_get_user_by_nicename( $user_nicename ) )

$user_nicename = bb_slug_increment($_user_nicename, $existing_user->user_nicename, 50);



$user_url = bb_fix_link( $user_url );

$user_registered = bb_current_time('mysql');

$password = wp_generate_password();

$user_pass = wp_hash_password( $password );



$user = $wp_users_object->new_user( compact( 'user_login', 'user_email', 'user_url', 'user_nicename', 'user_status', 'user_pass' ) );



if ( is_wp_error($user) ) {

if ( 'user_nicename' == $user->get_error_code() )

return new WP_Error( 'user_login', $user->get_error_message() );

return $user;

}



$user_id = $bbdb->insert_id;

$options = bb_get_option('approve_user_registration_options');

bb_update_usermeta( $user_id, $bbdb->prefix . 'capabilities', array('waitingapproval' => true, 'member' => true) );

approve_user_registration_send_pass( $user_id, $password );



do_action('bb_new_user', $user['ID'], $user['plain_pass']);

return $user['ID'];

}

endif;

although I am using a fairly hacked together install with some bleeding edge stuff in there so you may need to experiment a little.

[deadlyhifi]

All new users in bbpress are being automatically set to “inactive” instead of “member”

I found this happened if I tried to pull in wp_head() or anything else WP related into bbP. You’re best replicating the theme…

[deadlyhifi]

Wonderful. Thank you very much. I’m sure many will appreciate this.

“site larger than recommended” in that 1.6 isn’t recommended for anything live…

[deadlyhifi]

…it does keep the paging intact but counts for all the forums (fora?), even the excluded one(s).

To get round this requires amending the function bb_latest_topics_pages() in functions.bb-template.php.

$bb_latest_topics_count = $bbdb->get_var('SELECT COUNT('topic_id') FROM '' . $bbdb->topics . '' WHERE 'topic_open' = 1 AND 'topic_status' = 0 AND 'topic_sticky' != 2 AND 'forum_id' != 3;');

//  AND 'forum_id' != 3 - filters out forum 3 on front page paging count.

[deadlyhifi]

Thanks for the reply _ck_.

I’m actually using it on a larger site than recommended and we have pretty strict forum policies so ban people for 24 hours when they slip up using the Ban-Plus plugin. The problem is people just set up another account and instantly start posting again.

We recently had a spammer, a human one who would deliver actual advice to a discussion, but then follow it with links to escort agencies and the like. We banned him but he just signed up again – 5 times in a row!

The 24 hours approval rate would solve all these problems. Just need to find some time!

[deadlyhifi]

Excellent, thanks for posting this. Just tried it on latest ‘bleeding edge’ release and it keeps the paging intact.

[deadlyhifi]

yes. that update solved the issue of the tags not appearing immediately.

[deadlyhifi]

the latest bleeding edge release (from subversion) adds paging to the ‘Latest Discussions’. But if any of the arguments are used in ‘get_latest_topics’ the paging doesn’t work.

from functions.bb-topics.php

function get_latest_topics( $args = null ) {

$defaults = array( 'forum' => false, 'page' => 1, 'exclude' => false, 'number' => false );

so I’ve tried it with

$topics = get_latest_topics('forum=-3');

and

$topics = get_latest_topics('exclude=3');

both have same results but no paging.

[deadlyhifi]

Modified: trunk/bb-admin/admin-ajax.php (2016 => 2017)

Fix adding of existing tags to a post via AJAX. Tags used to be added but didn’t have any UI response.

Perhaps this was the issue and not my mod (see above post). Not tested it out yet…

[deadlyhifi]

It’s probably slightly more complex than you think.

For each forum you’ll have to fetch the latest post and then its details. I’m not sure how to go about that. Maybe someone else can shed some light on it. Sorry…

[deadlyhifi]

i’m not entirely sure what you are trying to do here since forum.php (used to display specific forum) shows information in the same way as front-page.php (used to display a summary of all posts)

i.e.

<?php if ( $topics ) : foreach ( $topics as $topic ) : ?>

<tr<?php topic_class(); ?>>

<td><?php bb_topic_labels(); ?> <a href="<?php topic_link(); ?>"><?php topic_title(); ?></a></td>

<td class="num"><?php topic_posts(); ?></td>

<td class="num"><?php topic_last_poster(); ?></td>

<td class="num"><a href="<?php topic_last_post_link(); ?>"><?php topic_time(); ?></a></td>

</tr>

<?php endforeach; endif; ?>

[deadlyhifi]

What are the odds that I will be able to keep all my topics and accounts by the time bbpress hits 1.0 stable?

I’d say that this would be the most fundamental aspect of backwards compatibility, and since the accounts table is based on WordPress there should be no issue there. Equally, topics, posts, times, etc. can’t have too many differences to warrant non-compatibility.

Things will be accelerating for bbPress soon due to some internal work at Automattic. This is occupying a lot of my time right now, but it will all be fed back into bbPress in the near future.

It’s really good to hear this. May I presume the folks over BuddyPress are getting involved?

As it stands I am running v1.06 on a fairly large website (due to various reasons I had to do it) and have found it to be very stable at high volume. My biggest issue has been fending off feature requests from the users. The biggest being ability to sort by topic id as well as last response time.

I’d also like to take this opportunity to thank everyone who is working on bbPress. I think it is a very promising and exciting project that will, coupled with WP and BuddyPress, be a very powerful software.