Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 76 through 100 (of 167 total)
  • @aekeron

    Participant

    Ah, thanks Boone. I’ll sort that out now :)

    I’m glad this will be useful for you. Your plugin updates + posts have always been extremely helpful for me.

    @aekeron

    Participant

    Hmm. Not a great start. I’ll try installing it on a fresh BP install and get back to you :)

    @aekeron

    Participant

    @aekeron

    Participant

    Incredibly easy with javascript.

    First google result: http://www.webmasterworld.com/forum91/1560.htm

    @aekeron

    Participant

    My experiences with the premium plugins/themes in the past hasn’t been good to be honest. I can understand them wanting to be reimbursed for their work though.

    @aekeron

    Participant

    Just an FYI for everyone.

    I’ve had to revert to DJPaul’s code for the plugin I’m working on currently as the method JJJ posted appears to have stopped working.

    No insult intended towards anyone’s code btw.

    @aekeron

    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

    @aekeron

    Participant

    Has the db format changed that much for xprofile stuff from bp 1.0 to 1.2? I kind of got the impression that xprofile is something that has been on the back-burner for a while, what with lots of other features getting more attention (which is fine by me).

    If this is the case you could try creating fields in seperate 1.0 install and then exporting the mysql + importing it into your 1.2 install.

    I’m not sure if this is worse practice than install 1.0 and upgrading, but I personally don’t really like the idea of installing a very old version of BP on a system and later upgrading it. It feels ‘cleaner’ to just go straight to 1.2 :)

    @aekeron

    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.

    @aekeron

    Participant

    Please do. It would be a very useful base for a lot of very nice features :)

    @aekeron

    Participant

    Thanks again both of you :)

    @takeo

    1. Ah yes. I think we opted for that as we though it made the content more obvious, but it’s a fair point.

    2. Yeah. I’m not a fan of the overhead layout page links layout either. It will be changed soon, though possibly not in time for the first release.

    3. I think it was already mentioned on namoo that these should be shorter so it looks like people agree with you there ;) I’m sure we can limit them to something more suitable.

    @aekeron

    Participant

    Hmm… The forums ate my reply (twice!) :/

    If you can test on the http://namoo.co.uk site for now and provide some feedback I should be able to release the plugin this week :)

    In regards to your other question – it should be possible but it’s not something I can look into for a couple of weeks due to workload sorry.

    @aekeron

    Participant

    Hi again.

    Just letting everyone know that the latest version of the plugin is now on the site. Various issues have been fixed, including:

    CSS issues for the edit buttons/etc on pages

    WordPress image edit plugin for tinymce now implemented (still a few css issues there though)

    Wiki ‘blogs’ appearing where they shouldn’t is fixed

    Lots of other stuff I’ve forgotten or not aware of because Stuart/Ryo have fixed

    I’ve also added support for wiki edits and wiki comments in the activity stream filters.

    I doubt the plugin will be released this week but I’m hoping for early next week. Once again, any feedback would be greatly appreciated :)

    If anyone is interested in getting email notifications for group activities/updates, please also check out this: https://buddypress.org/forums/topic/new-plugin-group-activity-stream-email-notifications

    In reply to: BP developer docs down

    @aekeron

    Participant

    Seem to be back up now.

    @aekeron

    Participant

    Not at all. I was trying to provide credit for your code as I pretty much just copy-pasted it rather than work out the problem for myself.

    Don’t be so touchy :)

    ( Trust me, once the groupwiki plugin is out and you see the dodgy code in there, it will be quite obvious that I wouldn’t critisize the code of the helpful people/plugin developers on here )

    edit: Ah, I can’t edit my original post to make sure it’s clear that I’m not trying to be insulting about your code DJPaul. Apologies.

    @aekeron

    Participant

    Ah great. Thanks for clearing that up :)

    For the time being, our groupwiki plugin requires multiple blogs anyway so I won’t rush out to change the code. I’ll make sure that the version that is released in a week or two is correct and up to date though.

    @aekeron

    Participant

    Looks like a cleaner way to do it than the old cold I saw DJPaul post a few months back. Is the below incorrect in some way? I’ll probably move over to this way of doing things but we’re literally just about to launch a site with bp-groupwiki and the latest buddypress/wpmu (seems fine in terms of usability):

    /* Check that BuddyPress is loaded before Wiki, from DJPaul */

    function wiki_load_buddypress() {

    if ( function_exists( ‘bp_core_setup_globals’ ) ) {

    require_once (‘bp-groupwiki-main.php’);

    return true;

    }

    /* Get the list of active sitewide plugins */

    $active_sitewide_plugins = maybe_unserialize( get_site_option( ‘active_sitewide_plugins’ ) );

    if ( !isset( $active_sidewide_plugins[‘buddypress/bp-loader.php’] ) )

    return false;

    if ( isset( $active_sidewide_plugins[‘buddypress/bp-loader.php’] ) && !function_exists( ‘bp_core_setup_globals’ ) ) {

    require_once( WP_PLUGIN_DIR . ‘/buddypress/bp-loader.php’ );

    require_once (‘bp-groupwiki-main.php’);

    return true;

    }

    return false;

    }

    add_action( ‘plugins_loaded’, ‘wiki_load_buddypress’, 1 );

    @aekeron

    Participant

    @Bowromir

    That sounds rather useful indeed. Any ETA? :)

    @aekeron

    Participant

    No worries. Until recently I was the same…and as of next week I’ll be the same again. Woo :S

    @aekeron

    Participant

    Prob not the best way to do things, but FTP into the site and rename all your plugin dirs/files. It’ll deactive everything. Not sure re the theme side of things – you could try the same in the theme dir but it may mess up.

    @aekeron

    Participant

    @aekeron

    Participant

    @21cdb and @bpisimone

    That mockup looks nice. It definitely seems a good way to go but I don’t think we’ll be able to change to that just yet. Once our project site has launched I should have a bit more time to polish up things like this though :)

    /re edit2: You’re absolutely right. I found that a lot of our students never really looked at the ‘extra buttons’ options so I was hoping to give them as many functions that they would recognise from MS Word as possible. I’ll definitely include instructions on how to modify this to suit people’s needs/tastes though :)

    @takeo

    Pah, me and Ryo have been waiting for your feedback. What’s going on? :p

    @everyone

    Latest version of the plugin uploaded to the demo site. Updates include: a warning if you’re editing a page and someone else saves, various bits of cleanup, Stuart has started to add the comment deletion code (not finished yet though, so don’t be surprised when it doesn’t work), sorted some weird behaviour in the activity stream for wiki updates, fixed attached image/file display in the revisions area, various other little fixes and bits.

    We’re in bug-fix mode from here on so please mention anything remotely dodgy you notice :)

    @aekeron

    Participant

    Great, thanks for testing it.

    As mentioning on Namoo, the loading image and ajax implementation for that particular piece of page creation is something that will be improved further down the line – once time isn’t such an issue :)

    @aekeron

    Participant

    @mercime

    1) I think you’ll still see a lot of activity stream updates but it should only consist of actual updates (e.g. when you add a new line of text/etc)……hopefully anyhow :)

    2) Unfortunately the workaround for this has been to make it so that the main admin account (assuming account #1 in the WP db) gets lumbered with this. Hopefully I’ll get something nicer sorted in future. It doesn’t look that hard to do but would just involve a bit more work using the lower level functions rather than the higher level wpmu ones.

    3) Lol. No worries. I do have a few plans for improvements in that area but nothing too drastic. Warnings about (other) people saving and slightly quicker updates regarding people no longer editing the post might be nice.

    @everyone

    Frontend wiki page creation for non-admins

    Test group here: http://namoo.co.uk/groups/frontend-page-creation-testing/

    I’ve implemented initial support for frontend page creation by non-group admins. This feature is disabled by default in groups but can be enabled at group creation or in the group admin screen. Basically this allows members of groups to create their own wiki pages at will.

    Warning: Currently only group admins can ‘remove’ these pages and group members aren’t limited in any way in regards to how many pages they can create. Also worth noting: the navigation styles have *not* been built with this in mind. As this feature is outside of the scope of our current project I can’t guarantee that decent styling will be forthcoming anytime soon either (my css skills are le suck and Ryo has way too much work on to be distracted by me getting carried away with extra features this late into the project) :)

    @aekeron

    Participant

    @mercime

    Ah..I think I realise part of what you meant now. I’ve hopefully fixed this issue. Please can you re-test and let me know? Thanks :)

Viewing 25 replies - 76 through 100 (of 167 total)
Skip to toolbar