[@boonebgorges Keymaster 16 years, 6 months ago]

An opt out link is a good idea but it will take a little time for me to implement it.

[@boonebgorges Keymaster 16 years, 6 months ago]

I’m fixing both things right now. Sorry for sucking!

[@boonebgorges Keymaster 16 years, 6 months ago]

Crap, I had fixed the other-people’s-profile thing and then reverted something at the last minute. I will roll a new version shortly with the fix.

I’m surprised about the is_email_address thing. I guess function_exists doesn’t work the way I thought it did. I’m going to have to move email validation to a different file that only gets required on WPMU. I’ll do that right now and check in another release shortly.

[@boonebgorges Keymaster 16 years, 6 months ago]

Excellent – and very glad to hear about the period-of-membership thing. If you have more ideas about how to allow admins to restrict visibility, let me know. I think it’s especially important for a plugin like this, which could quickly devolve into spammishness if left unchecked.

[@boonebgorges Keymaster 16 years, 6 months ago]

Hi Anton. I have not tested on single WP, but the invite-by-email functionality should work, as far as I can see. The only thing that won’t work is the email verification, which is built on MU-native functions. But I have put those inside of a function_exists conditional, so it shouldn’t break.

Over the next few days I will get a single WP install up and running and I’ll give it a go, but I don’t foresee any big problems.

[@boonebgorges Keymaster 16 years, 6 months ago]

Well duh, Andy is smarter than I am

[@boonebgorges Keymaster 16 years, 6 months ago]

OK, I tagged it – hope it really is stable Thanks for the help, gang!!

[@boonebgorges Keymaster 16 years, 6 months ago]

Hello to everyone following this thread. I just released version 0.4 of my Invite Anyone plugin, which, as promised, adds the invite-by-email feature.

https://wordpress.org/extend/plugins/invite-anyone/

Here’s what’s new:

– “Send Invites” tab added to the Profile section

– “Send Invites” has two subsections: Invite New Members and Sent Invites

– On Invite New Members, users can enter email addresses, a custom invitation message, and check off some groups that the invited member will receive invitations to when they join the site

– On Sent Invites, users can see all the invitations they have sent, as well as whether or not the member has accepted yet

– When a user accepts an invitation, they receive invitations to all groups to which inviter(s) have invited them, as well as a friendship request from each individual who sent an invitation

– A link is added to group Send Invites pages that goes to the profile Send Invites page and pre-checks the group’s box

– There’s a Dashboard panel for sitewide admins that allows them to control some of the default behavior of the Send Invites page, as well as the visibility of the Send Invites tab. You can create a blacklist of users who are not allowed to send email invitations (good if you have spammers in your community!), limit by blog role, or by length of time since joining the site.

It’s been fairly thoroughly tested, but it’s possible (likely even!) that there are still annoying bugs. Please let me know if you find issues or have suggestions.

[@boonebgorges Keymaster 16 years, 6 months ago]

Last-viewed pages are saved in a cookie. So if I set the filter on the activity stream to “Show Blog Comments”, a cookie to that effect is stored in my browser. Next time I load the page on the same browser, “Show Blog Comments” is shown.

In global.js, I believe the function that handles this is bp_init_activity(). If you comment the call to this function out (around line 15 of global.js), it should stop the cookie from overriding your default settings.

[@boonebgorges Keymaster 16 years, 6 months ago]

Good call, Anton. I’m going to overhaul the visibility rules before tagging it stable. Obviously the Send Invites tab should only be available to logged in users of their own profile, as you say. I will also make it possible for site admins to limit a bit further who should see the link – by blog role, maybe by time since joined.

[@boonebgorges Keymaster 16 years, 6 months ago]

@gregfielding To change text strings (like the ones that populate the nav tabs) you’ll need to create a custom language file. See the “labels and messages” section of the page that r-a-y linked to. (It’s a bit of a pain to set up at first, but once it’s in place you’ll find that it’s a very powerful, future-proof way to customize your site.)

[@boonebgorges Keymaster 16 years, 6 months ago]

hnla – Let me make sure I’m understanding correctly. When you paste a link into the message box, it shows up in the email that gets sent out? Or is it merely that you’re able to type a link into the box?

Very peculiar about the error – I haven’t gotten it on any test installation. If you copy the require( ‘db.php’ ) statement from the top of by-email.php and paste it right above the call to invite_anyone_record_invitation (around line 490ish) does the error go away? Or perhaps there’s a problem with the relative path to db.php – could you try hardcoding the path, just to see if that makes a difference?

Thanks as always.

[@boonebgorges Keymaster 16 years, 6 months ago]

Anton and hnla – thank you so so much for your very helpful comments. (I take it that most of the big functionality is working properly, since these are relatively small issues – that’s good news!)

Anton – Great point. I had originally not hardcoded the register link, but then had to hardcode it for some testing purposes and forgot to change it back. The latest trunk version creates the accept_link with site_url( BP_REGISTER_SLUG ), which is the same code used in BP core. Please let me know if it works for you.

hnla – Very sorry about my American date formatting I have changed it so that the format matches the setting in Dashboard > Settings > General. As for markup in the welcome message: I didn’t manually strip tags because I’m using $wpdb->prepare to write to the database, which means that all tags are escaped and therefore presumably not harmful. But I thought about it, and I think you’re right that it’s a good idea not to allow HTML in that box – it tends not to work well in email. The latest trunk version strips tags before sending the email/saving it to the db.

Finally, hnla, I’m guessing that your problem with /register/ redirects may have had something to do with one of the following:

– Anton’s problem (/register/ was hard coded into the accept_link)

– You are clicking on the link while logged in. BP redirects from the register page for logged in users. Log out, or try another browser.

– You’ve disabled registrations. In WPMU, look at Site Admin > Options; in WP I think it’s Settings > General > Anyone can register.

Thanks again for your help. I should be able to put a stable tag on it in the next day or so thanks to your feedback.

[@boonebgorges Keymaster 16 years, 6 months ago]

@anointed – Do I get to be a Master? http://startswithabang.com/wp-content/uploads/2008/07/he-man.jpg

[@boonebgorges Keymaster 16 years, 6 months ago]

Are you using WP or WPMU? If the latter, do you have registrations turned on at Dashboard > Site Admin > Options?

Have you tried the bundled bp-default theme to see if the same thing is happening there?

[@boonebgorges Keymaster 16 years, 6 months ago]

Thanks a lot for sharing your experiences – I bet this’ll be helpful for a lot of folks out there.

[@boonebgorges Keymaster 16 years, 6 months ago]

hnla – The plugin should work fine on 1.2.2.1. I tested it there briefly myself (though I developed it on BP trunk) and everything seemed to work OK.

Sorry about the email problems I’m using the exact same code as BP core (wp_mail, to be specific), so if you’re experiencing more general BP mail problems, then it’s probably not this plugin’s fault.

[@boonebgorges Keymaster 16 years, 6 months ago]

hnla – Would you mind checking to see whether the table wp_bp_invite_anyone exists in your database? The “sent invites” information comes from there.

I didn’t know about the spammer issue!! I will have a look at it.

[@boonebgorges Keymaster 16 years, 6 months ago]

PS – don’t forget to deactivate and reactivate when you get the new version

[@boonebgorges Keymaster 16 years, 6 months ago]

1) Table problem was my stupid mistake. I forgot to merge the code completely.

2) Warning message: another stupid mistake

I just rolled another trunk version up that should fix both problems. Download it in about five or ten from the repo, or immediately from here https://plugins.svn.wordpress.org/invite-anyone/trunk/.

thanks for your patience!

[@boonebgorges Keymaster 16 years, 6 months ago]

Can you check your db to see if the table wp_bp_invite_anyone exists? Either the table’s not there, or it’s there but not getting written to.

The table’s supposed to be created when you activate the plugin.

[@boonebgorges Keymaster 16 years, 6 months ago]

You have the 0.4-bleeding version? There should be a link on your profile (just to the left of Settings). Try going directly to http://example.com/members/anton/invite-anyone

[@boonebgorges Keymaster 16 years, 6 months ago]

What’s the wrong link?

[@boonebgorges Keymaster 16 years, 6 months ago]

Good call, r-a-y. My function doesn’t hook to wp – it’s the core function that’s causing me problems. But changing the priority on bp_core_setup_message does the trick. https://trac.buddypress.org/ticket/2270

[@boonebgorges Keymaster 16 years, 6 months ago]

I don’t think there’s an easy way to do it. I’m planning on building a tool that allows blog authors to send certain posts to different blogs on the same WP install (or for admins to pull from another blog) but it won’t be ready for another few weeks.