Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'notification user id'

Viewing 25 results - 576 through 600 (of 638 total)
  • Author
    Search Results
  • #64010
    D Cartwright
    Participant

    Hi Paul,

    The full code is in this (small) plugin here:

    https://wordpress.org/extend/plugins/buddypress-group-activity-stream-subscription/

    The url is created with the following code:

    class Group_Activity_Subscription extends BP_Group_Extension {

    function group_activity_subscription() {
    global $bp;

    $this->name = 'Notifications';
    $this->slug = 'notifications';

    // Only enable the notifications nav item if the user is a member of the group
    if ( groups_is_user_member( $bp->loggedin_user->id , $bp->groups->current_group->id ) ) {
    $this->enable_nav_item = true;
    } else {
    $this->enable_nav_item = false;
    }

    $this->nav_item_position = 91;

    $this->enable_create_step = false;
    $this->enable_edit_item = false;

    add_action ( 'wp_print_styles' , array( &$this , 'add_settings_stylesheet' ) );

    }

    #63809

    Hi,

    But that plugin only emails the stream notification. I want the option to email users as a standalone feature or may be I can adapt from that plugin.

    Will have to check it now. Thanks!

    #63200
    Bowe
    Participant

    yep! so far it works pretty darn well.. For certain social networks it imports photos and basic info.. I’ve integrated it with my custom login widget and so far I haven’t seen any major problems besides not storing the user his email, which makes receiving updates/notifications through email impossible… I need to think of a way to solve that problem..

    #62694
    D Cartwright
    Participant

    Hi there. Thanks for the feedback :)

    1. That is correct, yes. I have a few plans to streamline this a bit/make it more user-friendly.

    2. Something I’ve missed. I’ll add support for removing elements :)

    3. “added something new to the group” is just what I chose as a general catch-all in the case of the plugin running into an activity type that it doesn’t recognise. Will make this more obvious and customisable.

    4. That should indeed mean no delay. I’ll double-check this and update the wording.

    5. Good point again. I originally made this with hardcoded support for my groupwiki plugin. I’ll get rid of this.

    6. It isn’t at the moment but this is also on the list of things that i want to get in there asap. I’ll let you know as soon as I can get it sorted (shouldn’t be too hard as there isn’t *that* much text in there)

    Thanks again. I’ll check out your site later today :)

    #62685
    Michael Berra
    Participant

    I say it again: GREAT plugin – thanks alot!!!

    A couple suggestions/questions:

    1. Do I get it right: I can set the default in the backend, but eyery user (not the group admin) sets/changes the notification for themselves?

    2. Forum-Notification: I don’t want forums activated on my site, but I cannot get it off (no CSS classes for display:none). It is also not dynamically I guess, for I disabled forums in the backend, but still shows forum-notifications… Any solution to this?

    3. What exactly means “added something new to the group”? Is that comments? Is that another plugin like gallery, group-documents etc?

    4. Member must be registered for option: When I type 0 in the field, that would mean no delay, right?

    5. “You can also specify a minimum gap in time between updates regarding group wiki page edits.” This sentence does not make sense to all the users who haven’t wikis installed. It’s hardcoded. Any solution to get rid of it?

    6. Last but not least: Is it translatable??? I really would love to do that for german (at least try it as my first :-)) – could you provide a POT-File?

    Thanks for all the work. This is REALLY IMPORTANT for us and well/simple made!

    Ps: This is my test-install-site: http://wp.graphic-studio.ch/network – there I am testing your plugin :-)

    #62475
    Boone Gorges
    Keymaster

    D – I was getting errors when I tried using the plugin the latest 1.2. Had to do with call to undeclared function get_group_member_ids in order to populate $user_ids. I commented it out and put in the following instead:

    $thegroup = BP_Groups_Member::get_all_for_group( $group->id, false, false, false, true );
    $user_ids = array();
    foreach ( $thegroup['members'] as $member ) {
    $user_ids[] = $member->user_id;
    }

    and it seems to be working now. Am I missing something?

    Mike Pratt
    Participant

    @snark didn’t realize you are single user WP so no activation email

    Mike Pratt
    Participant

    @snark You forgot to mention the Activation email. Is your new user not receiving one? I just did a test registration and immediately received an email. While I agree with @Peter that plain text isn’t so bad but I also think it’s not so necessary to send the password the person literally just chose. The always have the Forgot Password link if they forgo it seconds after the fact. No real need as I see it to add a filter.

    r-a-y
    Keymaster

    Here’s the rationale behind disabling the welcome email as quoted in bp-core-activation.php:

    * Since the user now chooses their password, sending it over clear-text to an email address is no longer necessary. It’s also a terrible idea security wise.

    I’m going to sway a little to Peter’s side and say that BP should leave this option to the site admins. I actually think there should be more options for the administrator on a fresh install.

    peterverkooijen
    Participant

    1) By default, an email isn’t sent to the user because the user password is sent via plain text (not a good thing security-wise).

    That makes absolutely no sense. If you use the forgot password feature, the password is sent via plain text as well. Why is that OK and sending a password upon registration not?

    Most big sites, Facebook, LinkedIn, newspapers, have no problem sending passwords via plain text. Online security is always a balance between security and convenience.

    Buddypress is a social network. It’s not a banking website. If you start using credit card payments or paid membership, those scripts usually come with the own security.

    Who is going to steal a password to someone’s account on a blog network? Has that ever happened? What would they do with it?

    Just my 2 cents. Flame away…

    snark
    Participant

    Still not working. I did find the filter itself in the file /plugins/buddypress/bp-core/bp-core-activation.php:

    add_filter( ‘wpmu_welcome_user_notification’, ‘bp_core_disable_welcome_email’ );

    I suppose I could just delete that line to remove the filter, but then every time BP is updated it’ll probably get overwritten and I’ll forget all about it. Not sure why your filter hook didn’t work. Any ideas?

    Thanks a million for your help — I really appreciate it.

    #62403
    catinw12
    Participant

    okay, tried adding our mailserver info and user login and password and changed the port in the file class-pop3.php in wp-includes.

    sent a bunch of messages, using different configuration.

    nothing solves the default server from line.

    looking at the wpmu forum per DJPaul’s recommendation. I had found a plugin there and tried to install it – didn’t work. Looking again.

    #62334
    catinw12
    Participant

    Perhaps a clue – in looking at WP Mail, it references a file called class-pop3.php. In that file, I see that the $MAILSERVER = ‘ ‘

    and the $user and $pass are both ‘ ‘

    assuming that the email specified in admin panel of wpmu general->settings is reliable for the email, perhaps I just need to fill in those data.

    awaiting word from my hosting service for their opinion.

    if it is true, was this an upgrade or installation problem that the system does not query these critical pieces of data? I seem to be the only one with this problem or who cares about it in terms of wanting to change the sender email address.

    perhaps something to add to the configuration and installation setup guide?

    #62206
    D Cartwright
    Participant

    @mikepratt

    I was originally going to make use of one of the forum subscription plugins but our students have requested to be “spammed to death” with updates regarding their collaborative group work – much like facebook. Of course, now that they have got their wish they realise that receiving a huge raft of emails regarding your work each day isn’t quite as fun as hearing about what your friends did on facebook… ;)

    I’ve posted an update on where I’m at with the plugin and what I’m planning to implement before release this weekend. The link is below but I’ll also cut+paste the content as it’s probably going to get more people reading it if it’s on here rather than my small dev site.


    Update:

    Current bugs fixed. Will be adding the following requested features in the next couple of days with planned release on fri/sat/sun:

    1) User’s have to be registered X amount of time for their activites to email people. Warning about this in the notifications screen. Amount of time defaults to 1 week but controllable in wp-admin backend.

    2) Mention of the need to check these notification settings in the sidewide notifications area. Perhaps a list of links to the group notification settings for each group the user is a member of too.

    3) Default behaviour for the plugin will be for activity updates to be off or at least infrequent. This default behaviour controllable by wp-admin backend.

    4) Possibly change all notification settings to be time based as per the current group wiki edit ones

    5) Enable group admins + mods to send out a group update that overrides group user settings in regards to not receiving updates. This will be done by ticking a box on the update screen, an extra “what’s new” bit in the group notifications area or a screen in the group admin area.

    6) Finish the implementation to allow plugin authors to add their own action type handling

    The aims of these changes are:

    1) Keep the interface as simple as possible for all the site users

    2) Have default behaviour that isn’t too spammy

    Possible future updates:

    Ability for users to have update ‘digests’ received at a specified time daily. Allowing users to choose the time they receive the update should help spread server load.


    http://namoo.co.uk/blog/2010/02/01/group-activity-stream-email-notifications/#comment-11

    #62190
    D Cartwright
    Participant

    Thanks, r-a-y,

    Basically what r-a-y has said is completely correct. It hooks into the action for recording an activity and then emails everyone in the group with a notification of the activity. The idea of this is that it can catch pretty much anything related to a group – so forums, ‘wire posts’, group joins, wiki edits, etc can all be included. By default it will support the buddypress basic functions + our groupwiki functions but I’m also trying to build in an easy way for people to extend this to support their own plugins with just a small amount of additional code to their plugin file.

    Even without building in specific support for a plugin this will grab an activity update for a group and email it out, with a generic description for the activity type rather than something specific.

    The feedback I’ve had so far suggests that users want a bit more control over default behviour/settings of the plugin and for a way for group admins/mods to post ‘must have’ alerts. I’m hoping to add this in the next couple of days and get the plugin out by Friday or some point over the weekend.

    #62003
    dennissmolek
    Participant

    I think a better situation would be groups of groups.. IE

    Superuser Group: Admins, Mods,

    Midlevel Group: Testers, lower mods,

    User level Group: All users..

    I have been working with this concept with my “sitewide ID” idea.. It’s in the works for my image plugin and I bet it could be used from groups as well..

    Right now a user or a group can have a album assigned to it by a specific ID number that no two users or groups can have(imagine a phonebook with companies, people, government ETC. They all have numbers but arnt JUST people, or JUST companies).

    I thought if I switched the groups from tracking the User ID and switched to the sitewide ID you could potentially have a group IN a group..

    Then a check would be made to see if a User was apart of a group that was inturn apart of a group.. (in actuality all users would be added to the root group w/o notification)

    #61332

    In reply to: Wire Posts in bp 1.2

    Ezd
    Participant

    +1

    I just want to agree on the confusion between user- and display names. I don’t think this will ever be crystal clear to a regular user. Like if I was to @ myself on testbp.org – not knowing about the difference between user- and displaynames – and a totally different name showed up in the message-textfield, I would probably get confused and think something like:

    – Is this notification being sent to the intended user?

    – Should I rename @nameA to @nameB because @nameB is the name I see in the profile? (When in fact the right answer is @nameA)

    – This is too confusing to continue (fallout).

    Just trying to imagine how users would react on this feature. Not saying this feature is bad, but I’ve said from the beginning that it should be more user friendly and I probably don’t need to say that the user- and displaynames confusion are bugging a whole lot of users.

    #60945
    peterverkooijen
    Participant

    I’d like to know this as well. You could probably put this on activate.php somehow.

    Also the standard WPMU welcome email is sent on first login. That works via a function in wpmu-functions.php:

    function wpmu_welcome_user_notification($user_id, $password, $meta = '') {
    global $current_site;
    ...

    wp_mail($user->user_email, $subject, $message, $message_headers);
    return true;
    }

    I don’t see a hook in that function. It’s called/triggered from function wpmu_activate_signup in the same php file.

    wpmu_activate_signup is called from function bp_core_screen_activation in bp-core-activation.php.

    Perhaps you could add a redirect there to the mandatory extra fields? There are already some if statements there, one with this:

    bp_core_redirect( $bp->root_domain . '/' . BP_ACTIVATION_SLUG );

    You could add your own? Just guessing, wouldn’t know what it would look like…

    #60929

    In reply to: Wire Posts in bp 1.2

    Bowe
    Participant

    Because if I would mention your name somewhere for no important reason you would get annoyed by all the notifications you’d receive.. For example if I wrote a heavilly discussed blogpost on my site and people are talking about it around my network I would go crazy with the amount of notifications I would receive ;)

    you need a character for this to make it work and @ is the best one ;) By the way I certainly like this feature and I don’t think it’s that confusing for a user (apart from the displayname/username issue). But I do think it would be good if site admins could enable or disable this feature from the admin panel, just for those we don’t like it.

    #60891
    peterverkooijen
    Participant

    The welcome email is generated by this function in wpmu-functions.php:

    function wpmu_welcome_user_notification($user_id, $password, $meta = '') {
    global $current_site;

    if( !apply_filters('wpmu_welcome_user_notification', $user_id, $password, $meta) )
    return false;

    $welcome_email = get_site_option( 'welcome_user_email' );

    $user = new WP_User($user_id);

    $fullname = $meta[field_1];

    $welcome_email = apply_filters( "update_welcome_user_email", $welcome_email, $user_id, $password, $meta);
    $welcome_email = str_replace( "FULLNAME", $fullname, $welcome_email );
    $welcome_email = str_replace( "SITE_NAME", $current_site->site_name, $welcome_email );
    $welcome_email = str_replace( "USERNAME", $user->user_login, $welcome_email );
    $welcome_email = str_replace( "PASSWORD", $password, $welcome_email );
    $welcome_email = str_replace( "LOGINLINK", wp_login_url(), $welcome_email );
    ...

    I’ve added the FULLNAME lines. It works if used in the welcome email text in the wp-admin options.

    But haven’t figured out how to get the right password…

    Is there a way to put this customized function in bp-custom.php? And let the system use that one instead of the original in wpmu-functions.php? Forgot how that worked.

    #60881

    In reply to: Double passwords

    peterverkooijen
    Participant

    The password in the welcome email, if you restore it…, is generated by this file in wpmu-functions.php:

    function wpmu_welcome_user_notification($user_id, $password, $meta = '') {
    global $current_site;

    if( !apply_filters('wpmu_welcome_user_notification', $user_id, $password, $meta) )
    return false;

    $welcome_email = get_site_option( 'welcome_user_email' );

    $user = new WP_User($user_id);

    $welcome_email = apply_filters( "update_welcome_user_email", $welcome_email, $user_id, $password, $meta);
    $welcome_email = str_replace( "SITE_NAME", $current_site->site_name, $welcome_email );
    $welcome_email = str_replace( "USERNAME", $user->user_login, $welcome_email );
    $welcome_email = str_replace( "PASSWORD", $password, $welcome_email );
    $welcome_email = str_replace( "LOGINLINK", wp_login_url(), $welcome_email );
    ...

    So I guess you should replace $password with something else from BP? Or maybe add $bp as global (whatever the hell that is…)?

    EDIT: Adding $bp does nothing. :(

    BTW, the wrong password in the welcome email is the same number of chars as the password that was entered, so I assume it’s an encryption issue. Unfortunately the ‘forget password’ function resets the password, it does not send the stored one. That’s probably more secure, but I don’t see where else I could find code that retrieves the stored password.

    #60753

    In reply to: Wire Posts in bp 1.2

    Mike Pratt
    Participant

    Excellent point. Not all is lost but I will take this opportunity to provide some feedback to @jjj and @apeatling re 1.2 in it’s current state

    1. I get the use of the Twitter @ metaphor and adding “mentions” to the filters. Cool. BUT, it introduces a potential UI snag for users. Throughout 1.2 you make nice use of Display Name which users will become accustomed to and identify with. Now, you are identifying users by their user name as well (mixing metaphors, so to speak) as in ->

    John Doe

    and

    @jdoe

    Given people’s tendencies to use whacky usernames, thee is a big risk of confusion when both start popping up around the site. Not sure what the solution is but I think it’s not a trivial point, imho.

    2. Now that the wire has disappeared and along comes the concept of “Send Public Message” (I get it) let’s look at what vehicle we’re making use of and what it may mean to users. As it currently stands in 1.2, to “Send Public Message” you click that button on someone’s profile and you are taken to your own Status Update field with an @username filled in.

    a. the cursor is highlighted just before the @username not after (don’t forget to include a space) – this will only cause people to write the pubic message and push the @username to the end of the message. clunky

    b. You’ll probably need to include a @mentions on each person’s profile page otherwise, you’ll never be able to easily see the public message to @username you just wrote. The key point being, you want this to show up on THEIR profile.

    c. Probably worth considering including a notification to @username of said public message via email (make optional)

    d. Q: Will these @’s be co-mingled in your own status updates and, thus create confusion. Maybe that doesn’t matter and i am overthinking it.On the activity stream, it says John Doe posted an update, when he really sent @username a public message. In Twitter when @ leads a message as 1st character, it has different context than everywhere else in the Tweet. Perhaps -> John Doe sent @username a public message ? or something.

    I know I am getting fine grained here but theses (excellent) feature adds need to be over the top intuitive when introduced or they will breed unintended usages.

    #60617

    In reply to: Moderate members

    Tom
    Participant

    Seems that only fixed the admin panel problem.

    However it’s throwing up errors on the front end now.

    To be honest I think this plugin is maybe outdated.

    I’ll list here my site’s configuration, and what errors I’m getting in-case anyone fancies making this plugin work as it should.

    OK.. Groups and Blogs are disabled site-wide (Except for the main site blog).

    The setting “Allow new registrations” is set to “Only user account can be created.”

    And “Registration notification” set to “Yes”

    1st problem (As previously mentioned in this thread)… When I go to the admin panel and try to edit the options for the plugin, and hit save, it throws up the errors that I posted here:

    https://buddypress.org/forums/topic/moderate-members?replies=1#post-33514

    I managed to get rid of those errors by doing as mentioned here:

    https://buddypress.org/forums/topic/moderate-members?replies=1#post-33517

    However… it turns out that was not a fix for the plugin, so I reverted the file back to original state.

    OK, I couldn’t edit the emails that would be sent out due to those errors, but I could of worked around that (editing within the file itself)… so I continued to the next step, which was to try and create a new account, to see if the plugin actually done what it’s supposed to.

    After entering all my required fields, and hitting the submit button, I was taken to the upload avatar page. I was also shown the “Check your email address for your activation email” notice. Also, at the top of the page these errors appeared:

    Warning: implode() [function.implode]: Invalid arguments passed in /home2/puezq/public_html/mysite.com/v2/wp-content/plugins/bp-registration-options/bp-registration-options.php on line 639

    Warning: implode() [function.implode]: Invalid arguments passed in /home2/puezq/public_html/mysite.com/v2/wp-content/plugins/bp-registration-options/bp-registration-options.php on line 642

    Since I know only very little php, I had a look to see what those lines were in the plugin php file, but done nothing with them. Here are those lines:

    639 $bp_groups_str = implode(",", $bp_groups);

    642 $bp_blogs_str = implode(",", $bp_blogs);

    So I’m guessing these errors are showing because I have blogs and groups disabled on the site?

    However the plugin php file is full of terms relating to blogs and groups, so I saw no point just removing those lines from the file as other errors would appear from somewhere… surely?

    Anyway, to see what happened next- I then uploaded an avatar, successfully. The errors at the top of the page disappeared when it was uploaded.

    I then clicked on the activation link in the email I received, and logged into the site. I was able to EDIT my profile and browse the site pages normally, but not able to view member profiles, my own public profile, or even view the members search page.

    I then received an email saying there was a new member registration (to my admin email)… and the notice also appears in the admin panel saying there’s a user awaiting moderation.

    And that’s where Im at.

    Come to think of it, and after having read through this post several times now- It seems that the plugin’s actually working… with the exception of those errors that are flagging up in the admin panel (when editing the emails that will be sent out), and at the top of the front end page. Hopefully one of you guys can tell me how to get rid of those errors… or at least the ones on the front end. :-)

    This truly does sound like a fantastic plugin, but with non-existent support at the forum link in the README.txt file, I think it can only carry on living if one of you geniuses are willing to fix the bugs.

    Unless anyone knows of another plugin that will allow new member moderation? (I have searched, but couldnt find anything).

    #60124
    kineda
    Participant

    Thanks. That clears things up. The only other problem I’ve encountered is after I deactivate the BuddyPress plugin and re-activate it, I’ll get the follow db errors:

    WordPress database error: [Duplicate key name ‘useritem’]

    ALTER TABLE wp_bp_notifications ADD KEY useritem (user_id, is_new)

    WordPress database error: [Table ‘wp_bp_activity’ already exists]

    RENAME TABLE wp_bp_activity_user_activity_cached TO wp_bp_activity

    WordPress database error: [Duplicate entry ‘1’ for key 1]

    INSERT INTO wp_bp_xprofile_groups VALUES ( 1, ‘Base’, ”, 0 );

    WordPress database error: [Duplicate entry ‘1’ for key 1]

    INSERT INTO wp_bp_xprofile_fields ( id, group_id, parent_id, type, name, is_required, can_delete ) VALUES ( 1, 1, 0, ‘textbox’, ‘Name’, 1, 0 );

    #60081
    David Carson
    Participant

    Erich73, The notifications tab alerts users to more than the latest private messages. But it’s up to you whether you want to remove it or not.

    FYI – I just checked the Inbox Widget plugin into the repository –

    https://wordpress.org/extend/plugins/inbox-widget/

    Screenshot –

    https://wordpress.org/extend/plugins/inbox-widget/screenshots/

    This is not a stable version and it will only work on sites running the latest trunk version of BP (2243+) with the bp-default theme enabled. It’s just something to build on and I’m hoping to add improvements soon.

Viewing 25 results - 576 through 600 (of 638 total)
Skip to toolbar