Not at the moment. It’s in the works though. See: https://buddypress.org/forums/topic.php?id=1304
Sorry for bumping this old post, but life is evoluting…
Such a plugin exist now:
https://wordpress.org/extend/plugins/buddypress-group-documents/
That’s awesome news. Trying to see how to best incorporate this.
I too have been searching for something like this. Perfection, for me, will be when we build a directory/library of sorts for all site or group members to take advantage of and promote finding and reading of docs. Also – I’d like to see some sort of in-site reading capability a la Scribd
The current “group documents” doesn’t support 1.2 as far as my testing goes.
I think most big BP plugins will need fixing for 1.2, mine don’t work out of the box.
Yup. I’m finding lots of plugins don’t work in 1.2. Lots of changes in both the core and the theme.
There will be a backwards compat plugin that will let these things work. Right now the trunk has removed all deprecated code.
Ah right. I recall you mentioning something about that before. That’s very cool Andy! Good to know.
Lots of changes in both the core and the theme.
I’ve noticed it’s mainly (?) name changes for functions. Is there/will there be a list of these name changes, so you can do search-replace in your custom theme/code/plugins and fix a lot of problems?
I’m one round behind, upgrading to 1.1.3, so hurray for this documents plugin! Making the groups more useful is priority #1 in this version of my project.
Well… the new default theme is pretty different from the old default theme. The templates are structured in a completely new (and better) way. I had built a child theme off the old default… and it took a fair bit of work to get the same child theme working with the new default. I imagine that any plugin which relied on you adding a folder full of template to your theme (like bp-events for instance) will have some issues with BP1.2 and the default theme. Unless the compatibility thing Andy is talking about will address that too.
FYI, making Group Documents work natively with 1.2 is on my to-do list. Hopefully I’ll have an update for it in the next couple weeks. Thanks for checking it out!
The update is up and it works great! Thanks!
Something that perhaps would be beneficial would be a bit more visibility on the stream. Right now it’s only the text “uploaded the file” which indicates that there’s a new file on the website.
If possible perhaps the description of the file could be added as the “message-text” in the stream?
Great plugin! I get php warnings when deleting a group with buddypress-group-documents plugin activated. Has anyone else had this problem when deleting a group? No problem when plugin is deactivated.
Warning: Missing argument 2 for BP_Group_Documents::get_list_by_group(), called in /public_html/wp-content/plugins/buddypress-group-documents/index.php on line 470 and defined in /public_html/wp-content/plugins/buddypress-group-documents/include/classes.php on line 251
Warning: Missing argument 3 for BP_Group_Documents::get_list_by_group(), called in /public_html/wp-content/plugins/buddypress-group-documents/index.php on line 470 and defined in /public_html/wp-content/plugins/buddypress-group-documents/include/classes.php on line 251
Warning: Invalid argument supplied for foreach() in /public_html/wp-content/plugins/buddypress-group-documents/index.php on line 471
Warning: Cannot modify header information – headers already sent by (output started at /public_html/wp-content/plugins/buddypress-group-documents/include/classes.php:251) in /public_html/wp-includes/pluggable.php on line 865
Mark – Thanks for catching that error! I made some function tweaks when I added paging, and a regression popped up! I’ll remember to test for group deletion in the future. This has been fixed in version 0.2.4 now available
Tore – I like you idea of more details on the stream. I’ll add that to my list of feature ideas.
@peter-anselmo, thanks for the fix. FYI- during my auto install process the activation is said to fail (but doesn’t) and the error below is generated. The plugin actually is activated:
Fatal error: Cannot redeclare bp_group_documents_check_prereqs() (previously declared in /public_html/wp-content/plugins/buddypress-group-documents/index.php:56) in /public_html/wp-content/plugins/buddypress-group-documents/index.php on line 67
@Mark
I find that happens a lot when you click ‘upgrade’ – I know it says it disables the plugin first, but something obviously gets loaded. It’ll probably not occur if we disable a plugin manually, then select upgrade, then re-activate it.
hey, great plugin. Along with better activity stream info, it would be great to be able to set the path for the uploads folder in the plugin admin page.
Putting the uploaded files in the plugin directory itself is questionable. Maybe uploaded files could be organized by folders according to groups. Perhaps it should default to a different location? blog.dir for WPMU or uploads for WP.
Hi Peter
I’ve sent you an email but thought it might help to post the message here too in case it’s relevant to others:
Hi Peter
Many thanks for the great Group Documents plugin for BuddyPress, which I’m testing with BuddyPress 1.2 RC3.
In my testing, I’ve come across the following error when uploading a document to a group:
Warning: Invalid argument supplied for foreach() in /home/richbest/public_html/wp-content/plugins/buddypress-group-documents/include/notifications.php on line 23
Do you know what might be causing that please?
Would be grateful for your help.
Many thanks.
Best regards
Richard
@nzde, I have the same error even though files upload fine.
@Dwenaus – The next version will have a way to easily override the the default document folder by simply using a DEFINE statement in your bp-config.php. I’ve thought about putting files in sub-folders for groups, but didn’t envision most people benefiting from the hierarchy. I’m open to suggestions though – How many files are too much for one folder? 500? 10,000? 100,000?
@nzde & @pjnu – I’ve been able to replicate the error, and should have a fix out in the next few days. It showed up somewhere between 1.2-rare and 1.2 rc2.
@peter-anselmo:
I’d like to see uploads segregated by group and also user id.
eg. /upload-folder/GROUPNAME/USERID/_FILES_HERE
Great suggestion Ray.
Too my for one folder? 20-30 before being to clogged up. But that depends on what’s in them.
Are people using or accessing the files directly? I guess what I’m asking is: do we want additional file heirarchy for aesthetics and portability? Or for performance?
From a performance standpoint, I would think the ideal files/folder ratio would be much higher than 20-30. I could be wrong; I haven’t run any tests.
I’m leaning toward folders for the group level. But really, to make an informed decision, I’d like to know how people are using the plugin. For my client, It’s just 3-5 PDFs per group. With such a low volume, I didn’t anticipate the need for much heirarchy.
