Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'notification user id'

Viewing 25 results - 1,001 through 1,025 (of 1,072 total)
  • Author
    Search Results
  • #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.

    #59997
    peterverkooijen
    Participant

    Found this in bp_core_activation.php:

    /***
    * bp_core_disable_welcome_email()
    *
    * 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.
    *
    * This will only disable the email if a custom registration template is being used.
    */
    function bp_core_disable_welcome_email() {
    if ( '' == locate_template( array( 'registration/register.php' ), false ) && '' == locate_template( array( 'register.php' ), false ) )
    return true;

    return false;
    }
    add_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );

    So I guess I could just remove this function?

    Is sending that password really such a “terrible idea security wise”? Are criminal gangs intercepting these emails to break into WordPress accounts?

    EDIT: Yes, removing that function works. A regular WPMU welcome email is sent.

    But the password in the email is eight numbers instead of the eight letters password I’d entered. Why?! Does Buddypress do its own encryption on the password? Does it use other tags or “placeholders” or whatever they’re called to call the password?

    Going to sit in a corner and cry…

    #59996
    peterverkooijen
    Participant

    Does anyone know how to get a welcome email in BP 1.1.3 without resorting to the Welcome Pack plugin?

    There are some clues here, but I have no idea what to do with them and if this would even apply to Buddypress registration process.

    Should I just stick this in a template files somewhere? Where?

    <?php wpmu_welcome_user_notification($user_id, $password, $meta); ?>

    Would it take the text from the Options in the admin area?

    Or does BP have its own function for this?

    #59092

    I’d ultimately love to see things go in that direction, and have been sifting through code the past few days thinking of how to get more red in the trac than green.

    However, if this was the case, and activity had a component scope and a serialized array of return values, then you could replace private messaging with a threaded activity stream that only the users involved in that thread can view. You could send activity to multiple groups at a time, or only 1, or all of your groups, or the entire site, or any other registered components serialized set of values that mean whatever they mean.

    You can almost replace the notifications class all together too, because if you take a count of the number of activities a user has directed at them and store it in usermeta, when the user returns if that number is higher, there’s your total notifications. Filter those new activities and now you can see how many of each. Actually, the code already exists within both WP and BP to do this.

    In that regard, the activity stream does start to replace core communication components like forums, private messages, status updates, notifications, and the wire. At that same time, BuddyPress becomes less about separate components with their own API’s and classes and subsets of functions, but more about creating new methods for users to interact with each other in specific scopes of communication.

    You could take things like twitter lists and make them work both ways, where you could send a message/comment/update/picture to only specific users instead of only viewing tweets from users. You could create an endless array of ways and names for collaborative tools to develop the platform from within the platform. It’s basically the blog post_types concept attached to people’s activity instead of re-categorizing blog posts.

    The way to further develop groups would need a whole new topic, but I’ve got some ideas for that too. :)

    @mrmaz, what you propose is the fundamentals of how I’ve approached my development before finding WP; start with small basic classes and work my up in functionality. There very easily could be a basic “bp_component” class where every new component just extends off of that, and sets the needed vars and assigns the needed functions accordingly.

    #58772
    stripedsquirrel
    Participant

    Hi DJ Paul.

    as far as I can see, nobody is complaining that the sky is falling, that would be a quite silly thing to do. Well I guess technically it is, but at least the earth is stopping it from doing so ;-)

    Just pointing out an inaccuracy in thinking, I am sure that this is allowed without immediately posting PHP to fix it?

    Back on topic; the question should also be: how could this spammer get access to all the usernames automatically? Of course everybody is listed, but somehow the were harvested and added to the pm list.

    – Anyway, I think a very good start is that you can only message your friends. Thought that this would be already ths case, that is why I wondered how we could get spammed?

    – Additionally: a maximum of PM’s per user per x amount of time (seems that 1/minute should be enough, + 50 per day. of course this should be optional and configurable with error notification (site options or plugin?)

    – Maybe a maximum mailbox size, which included sent messages. So that at least spammers have to clean out their sent box before being able to send new messages.

    – Also a maximum of adressees per PM, else the other 2 are useless

    – maybe a minimum age of user (meaning time since registration), before he can send out PM at all?

    Of course, any of these can be worked around, but at least it might slow spam down, at least from strangers..

    Cheers, Harry

    #7943
    5609856
    Inactive

    I was just wondering if it is possible to set it up so that a user can follow a blog.

    So basically I’ll have multiple blogs on my site, and when a user sees one they would like to follow/join, they press a button and then everytime that blog makes a post, they will get a notification in their profile.

    Are there widgets for this? I’ll have another look.

    Thanks.

    #58363
    Paul Wong-Gibbs
    Keymaster

    Welcome Pack did originally auto-accept Friend invites but someone made the suggestion that letting users respond to the notification also taught them how to use the site. I changed it a few versions back.

    Devil’s advocate: if you friend everyone with everyone automatically, what’s the point? You haven’t got any not-friends to be not-friends with ;)

    buddypresser
    Participant

    I was having a problem where ‘Membership Request Accepted’ notifications weren’t being deleted when clicked. It might be the customised theme I’m using, or it might be a bug, but either way…

    Here’s a solution I found – not sure how good it is, but it seems to work.

    Drop this into bp-custom.php (if you don’t have one, create it and put it in the main plugins directory):

    function bp_custom_fix_group_notifications() {

    global $bp;

    bp_core_delete_notifications_for_user_by_type( $bp->loggedin_user->id, $bp->groups->slug, 'membership_request_accepted' );

    bp_core_delete_notifications_for_user_by_type( $bp->loggedin_user->id, $bp->groups->slug, 'membership_request_rejected' );

    }

    add_action( 'groups_screen_my_groups', 'bp_custom_fix_group_notifications' );

    Hope this helps somebody.

    thomasbp
    Participant

    Hi!

    I should like to present http://sheepworld.de, a website based on wordpress-mu and buddypress.

    About my client and me


    Sheepworld is a German company designing and selling postcards as well as various gifts with sheep design. I was working as webdesigner while I was studing. Now I am a lawyer soliciting webdesigners, but work part-time as designer and coder for sheepworld in order to stay in the subject.

    About the goals


    Sheepworld had in the past many different websites. A Blog, a shop, a children & youth community, corporate page and many more. The aim was to bring them all under one roof. Another aim was a simple maintenance as well as handling of the content by sheepworld’s staff.

    Choosing the plattform


    I’ll write only about those on the short list. We didn’t choose between free and paid software. The only requirement was an open code.

    Since we had experience with typo3 we rejected the idea of using this software, because it was too difficult to handle. Actually I was the only one writing typo script so in emergency no one could fill in. Further it was anything but easy to handle different templates for different pages. And typo3 doesn’t provide many extensions for a community. No offence, it is a great piece of code, but rather for “serious” websites with many domains and editors.

    Another candidate on the shortlist was Drupal. And if buddypress had not popped out of nowhere last spring, we would have chosen it. It is in my opinion more complicated, though. And the template handling is not as easy as that of wordpress. In addition sheepworld used wordpress already for blogging and thus there weren’t any reservations among the staff (the editors as well as the technicians).

    I confess that I had some doubts as to the development of buddypress, for it was brand new. But after watching Automattic’s or better Andy Peatling’s passionate work on it and its rapidly growing community I was sure it won’t become a flash in the pan.

    Ups and Downs


    The most prominent advantage of buddypress & wordpress is the simplicity of the development process. After one week of study you can develop own plugins and templates, which will allow you extending buddypress easily and safely. However, basic knowledge of html, css, php is necessary. I recommemd to get acquainted with jQuery as well. Sure thing, one can install buddypress w/o these languages, but in case of problems it might become an ordeal to find a solution.

    Further buddypress is transparently written and allows finding solutions w/o having a code documentation. For instance, if you want to understand how an avatar is displayed you first search in the template files for a function that does this. Than you look for the function in core files (or just enter it on google) and see how the function is applied.

    Thirdly, updating of wordpress and buddypress is a dream. As long as you follow this procedure “backup-deactivate plugins-update-activate buddypress-activate other plugins” there shouldn’t be any trouble.

    The downside of this simple and understandable code is that it doesn’t go quite easy on resources. Thus we had to install a caching solution (we chose “W3 Total Cache”-plugin, which runs really well and supporty gzip as well as eAccelerator on the server in order to cache compiled php code. This is not a big deal, though. The issue is that pages for logged in users cannot be cached. Imagine you would get cached activities or an admin bar with cached notifications of someone else. So the caching speeds up the page only for non-logged-in users. This may take the load from your server and speed up the whole page, but my wish is a caching system for logged in users (don’t ask me how ;) ).

    Another downside results from the young age of the project. There are still features missing (native gallery, native privacy options, no Ts&Cs checkbox during registration) and the documentation isn’t very extensive. But these features are coming up and the community delivers a lot of solutions.

    Combining with other Software


    Beside to wordpress and buddypress we are using the OXID shop system for the shop, PHPlist for the newsletter and osTicket for the support system.

    Implementing osTicket was quite easy. All I head to do was including wordpress’ header and footer into the contact form. ;) However this didn’t work with the Shop, so we had to create a static version of the header and footer and include them as html into the shop’s templates (we do it every 24h by using a cron job). The downside: There are no user features (login fields, notifications) within the admin bar on that page.

    There are also plugins that allow connecting PHPlist with wordpress.

    User & Staff Experience


    The users adopted fast the new page as well as the editors. However, I cant say anything about using buddypress as platform for a blog network, since we don’t use this feature. Our users may only create groups and forums. Summing up my client and me we are very happy and recommend buddypress.

    STOP TALKING!


    Alright, I stop my monologue here, a far more extensive version (German) can be found in my blog: http://www.advisign.de/webdesign/2009-12/sheepworld-de-ein-schafiges-projekt-mit-wordpress-mu-und-buddypress

    If you have any questions, plz feel free to ask them.

    Thanks


    A big thank goes to the whole community and especially to Andy Peatling for the great work and the support! Our sheep appreciate your involvement in creating their new meadow. ;)

    Catherine
    Participant

    When a user gets an email notification they have a friend request, if they are not logged in, they get redirected to the 404 page –

    since i cannot figure out why this works from the bp login bar

    http://successiqu.com/wp-login.php?redirect_to=http%3A%2F%2Fsuccessiqu.com

    and the resulting click from the email doesnt

    http://successiqu.com/wp-login.php?redirect_to=http://successiqu.com/members/gingerburr/friends/requests/

    below does work, so for some reason the :// are causing a 404

    http://successiqu.com/wp-login.php?redirect_to=http%3A%2F%2Fsuccessiqu.com/members/gingerburr/friends/requests/

    so, if no one knows why or how i can fix THAT error- where do I change the email that goes out?

    #56995
    Oliver Wrede
    Participant

    Hello.

    I do have spam user registrations even with registration option set to:

    [*] Only logged in users can create new blogs.

    I understand this option to say that new user registrations are DISABLED but registered users may create blogs. Unfortunatly the “Register”-Button appears in the welcome widget with that setting — even though clicking it will redirect back to the homepage.

    To disable the above option also disables the blog creation — which I do NOT want.

    For an unkown reason I do see spam registrations (a couple per week) but it seems those users are not able to login and create blogs (or comment). I also do NOT get the usual notification mails for new user registrations.

    It seems like a bug to me.

    #56990
    dpolant
    Participant

    Here is one way to do it I believe. Put this filter and function inside a plugin or your custom.php.

    add_filter('bp_blogs_activity_new_post', 'my_process', 2, 3 );

    function my_process($activity_content, $post, $post_permalink){

    $activity_content = sprintf( __( '%s wrote a new blog post: %s', 'buddypress' ), bp_core_get_userlink( (int)$post->post_author ), '<a href="' . $post_permalink . '">' . $post->post_title . '</a>' );
    $activity_content .= "<blockquote>" . bp_create_excerpt( $post->post_content, 25 ) . "</blockquote>";

    return $activity_content;
    }

    I think this is the most efficient way of doing this. Basically, this code snippet overrides the content of the activity notification for a new blog entry. It is unfortunate that you have to write all the other crap again, but as you can see the thing you want to change (bp_create_excerpt) doesn’t have its own filter.

    The good news is, unlike some approaches to this problem, this solution doesn’t require that you alter the core.

    Try it and see if it works. Sorry ’bout the layout overflow :(

    #7607
    grosbouff
    Participant

    Hi…Big news here.

    But (in parts) bad news :

    I was cleaning the code of my plugin, which is at this point almost finished.

    I was trying to find a reliable way to handle categories and tags : my code is working but categories and tags are in 2 different custom tables (the code is a little dirty); there is no admin page to manage them…

    Well, I was looking at how WordPress was handling them because I wanted the code to be strong enough to keep maintaining my component in future easily.

    Then I start to look at the taxonomy system.

    Then I saw that WP 2.9 will include custom post types…

    And then… I’m half disappointed, half excited :

    Half excited, because “custom post types” means that you will be able to define new post types (-actually, there is just “pages” and “posts”), like, let’s say … “classifieds”.

    That means that you will be able to use the WP dashboard to write a classified like you write a post, and use categories and tags for those classifieds as you do for a post. Those categories or tags will not be those you use for your posts but custom ones just for your “classifieds” post type.

    The wire for a classified is no more necessary as you can will be able to use the core comments system with your classified.

    Idem for pictures that you will be able to upload and attach directly from there.

    That also means that you will be able to search,filter and display those classifieds with the same functions that you do for your posts.

    Well, well, that means that this is a big step for WordPress…

    But this is also a disappointment for me because that means that lot of the time (several months so far – not full time of course, and i’m an autodidact) I spent to write my plugin was useless as now, the WP core will be able to do by itself a lot of what I wrote in my plugin.

    So I think that it would be a wide decision to wait that the custom post type stuff came and to… almost start writing a new plugin from scratches.

    Yes, some pieces of my work will still be reusable to make all this “buddypress-friendly” (attach classifieds to groups, notifications, etc), but 95% of my actual code will potentially be useless as WP core function will do the same, and better.

    But from what I read, we don’t know exactly when all that stuff will came. Some parts of the functions will be available in WP 2.9 but it’s not sure that the whole thing will be usable in that version, neither we know when WPMU 2.9 will be out : in the trac, they say

    I really see no reason we cannot get this into 2.9 since a large majority of the work has been completed already. Even if we only get some of the basic functionality of this into 2.9 it would still be a big help and a basis of something to build off of for 3.0.

    .

    Well… think the best thing to do should be :

    STEP 1 :

    Sleep. Cry. Sleep. Howl. :)

    STEP 2

    -restart from scratches if I feel the courage for it :)

    -write a new plugin that creates a new blog just for Classifieds at the plugin’s activation.

    -All the members of the BuddyPress installation would be members of that blog and so have the capability to write posts.

    -Use the posts on that blog as the “classifieds” displayed in the BuddyPress site.

    -Control the data sent – number of images used in the post, number of chars, post boxes displayed, etc).

    -Add the BP features for notifications, activity, “attaching” classifieds to groups and so.

    -use that blog as the basis of my plugin; then

    STEP 3

    This will be able to make the component ready for WP 2.9 or WP 3.0…

    There shouldn’t be lots of stuff to modify in the code. change the post types of the posts in the custom blog to “classifieds”, move them to the main blog and add specific capabilities to decide who can do what. Example : you could be able, as subscriber, to write classifieds but not posts or pages.

    And why not differenciate classifieds written on the main blog and classifieds written on a user’s blog, if any (ex. company blog).

    STEP 3b

    Add a BP-friendly posting system ?

    So here’s where I am.

    As I said I’m feel a little sorry.

    Maybe I should have though of handle the data from my component from a blog from the beginning. But that when we make mistakes that we go further !

    The good thing is that I learned a lot about WordPress & BuddyPress and that I know now what I can do with it, and i’ll release my own BP project soon or later. And that once that custom post type system will be available, writing the classifieds component should be a piece of cake, or almost.

    If I feel it, i’ll start to rewrite it soon as I explained it in step 2. But I have a lot of work now so I’m not sure I will be able to do this at this moment. I’ll tell you about it in a few days.

    Anyway, RIP (for the moment) my-custom-component :) You can still see some pictures of the work achieved here : http://dev.benoitgreant.be/2009/11/18/classifieds-component-postponed/

    #56598
    stwc
    Participant

    OK, created a trac enhancement request per Jeff’s suggestion. Hope I did it right ;-).

    Here.

    By the way, I wasn’t thinking that this would be implemented as something required or anything like that, or even that it would be used for quoting excerpts of what people have said. But when people did use it (and once they noticed the functionality, further use would presumably just emerge) without really thinking about it, as they already do, it would be kinda delightful to have it provide notification functionality (which could be turned off, too, I guess).

    Just a simple link to the posted item, wherever it might appear, that has @myusername in it as notifications in my buddybar and maybe a stream in my messages inbox area somewhere. But those would be implementation details, if the general idea is deemed a good one.

    #7541
    stwc
    Participant

    I’ve been noticing a lot of people here are using the @user notation (most recently popularized by Twitter) here in the forums. It doesn’t actually do anything, of course, but I was thinking it would be very cool if it actually did.

    What I’m thinking is that if someone actually used the notation @stwc somewhere on the site (for example), a notification would be fired off (appearing on the buddybar) to that user (ie me, in this case), and clicking on the notification would take the user to the item in question, whether it’s a wire comment or a forum thread or [anywhere else]. I think it would really help pull together the kind of… loosely-coupled… way that various communication channels on a BP install work. It could also appear as a stream in the user’s messages area…

    This might be something better implemented in a plugin than in core, but I thought I’d throw it out there.

    #7423
    5268532
    Inactive

    I recently added buddypress to my wordpress MU account and used http://codex.buddypress.org/how-to-guides/upgrading-a-buddypress-1-0-theme-for-buddypress-1-1/ to add buddypress functionality to my wordpress theme (which was modified from wordpress single users) My only problem is that none of the links in MyAccount>Notifications>or Visits work. They all are looking for /members/admin and I can’t find the location of these files on my server. I assume the hugest reason I get the 404 Page not found error is because the directory doesn’t exist. How do I resolve this issue?

    #7421
    acvanrijn
    Participant

    I’m really impressed by the buddypress development and am strongly considering it for future websites. One of the upcoming features mentioned on the http://buddypress.org/about/ is the support for status updates. Will there be any support to auto-sync status updates through twitter/facebook/myspace/ping.fm/etc?

    I notice a lot of people don’t want to update their status on all the social networks they are part of (which can be quite a few), and as buddypress generally will be running a secondary social network to a person’s primary social network (usually facebook/myspace/twitter), auto-syncing would be a great option for the average user that doesn’t want to go crazy updating their status everywhere all the time.

    PS – Clicking the New Topic button while not being logged doesn’t do anything. Maybe it would be better if it forwarded to a notification that logging in is required to post in the forum along with a register/login links?

    #55022
    chewbaker
    Participant

    I am not sure if this is the proper way to do this, but to fix this problem, I changed the code in the bp-core-adminbar.php on the following lines from:

    echo '<li id="bp-adminbar-notifications-menu"><a href="' . $bp->loggedin_user->domain . '/">';

    to

    echo '<li id="bp-adminbar-notifications-menu"><a href="' . $bp->loggedin_user->domain . 'messages/">';

    Hope this works for others who might have had this problem

    Cheers

    Chew

    #54317
    Tore
    Participant

    Hi again!

    This is a picture of how it looks in my page right now:

    http://skitch.com/tore/nnsxq/profile-page

    [Ändra profile] [Byt bild] [Allmänna inställningar] [Epost-notiser]

    means

    [Change profile] [Change avatar] [General settings] [Email notifications]

    You can set any name and skinning of course.

    #7032
    Tore
    Participant

    Perhaps you’re rebuilding the BP-theme to your liking and find that you want to link to specific pages for the user. This is how you do to get the users to those pages:

    <a href="<?php global $bp; echo bp_core_get_userurl($bp->loggedin_user->id); ?>profile/change-avatar">Change avatar</a>

    You can change profile/change-avatar to the pages in the bp-theme.

    activity/

    just-me

    my-friends

    profile/

    change-avatar

    edit

    index

    settings/

    general

    notifications

    With this you can for example put everything from “settings” on the user profile page. That way you’ve got one page less and one thing less on your userbar.

    You can make things dissapear from the userbar/optionsbar with using the css-command display:none. Google for it.

    KISS!

    #54270
    wekko
    Participant

    Hi guys, I’m having the same problems. When I do not add the $bb->bb_xmlrpc_allow_user_switching = true; line to the bb-config file it works, but just for the admin. After adding it, bbpress keeps coming up with the famous ‘There was an error posting that topic.’ notification. Since it’s dificult to debug a message like that I just can’t find out what can be wrong…I just updated the BBPress installation to 1.0.2, but I still have the same problem.

    I hope somebody can help me out, thanks :).

    quaker-oats
    Participant

    This is a followup to a post that I don’t think was resolved: http://buddypress.org/forums/topic/private-message-issue-mulitple-receipents-email-notification-empty-content#post-7103

    Essentially: the link to messages in email notifications do not go to the message thread.

    The reason the links are not working are possibly because of an error in the bp code.

    In the function messages_notification_new_message() (in bp-messages-notifications.php),

    line 15 says:

    $message_link = site_url() . ‘/’ . BP_MEMBERS_SLUG . ‘/’ . $ud->user_login . ‘/messages/view/’ . $message->id;

    This is incorrect. Instead of having $message->id at the end, it should be putting in the *THREAD_ID*.

    If I change this to the thread-id, then the link successfully goes to the message thread. Otherwise it doesn’t work.

    Can someone experienced in the buddypress code please confirm this? Or am I doing something wrong/mis-understanding something?

    Thanks!

    #54184
    David Lewis
    Participant

    I think it’s a great feature and should be available to everyone… but perhaps should have more messaging around it and/or made an option that an admin can disable. Personally… in my case… this feature would be invaluable and it would need to be available to everyone. It all depends on the nature of the group. For a giant group… maybe you don’t want it. But let’s say you form a group that is a small collection of committee members using the wire to talk about ideas or what have you… in that case… the mass notify is great. Also… users who get annoyed with these kinds of notifications always have the option to turn them off!

Viewing 25 results - 1,001 through 1,025 (of 1,072 total)
Skip to toolbar