Conflicting with Buddypress Docs!

I am having the same problem. Any movement?

No – no help, or movement on this issue.
Please let me know if you end up finding a solution of fix. I will do the same.

Cheers

Thanks for the report. It looks like it is a CP issue (rather than BuddyPress Docs). I’ve corrected it here: https://github.com/WebDevStudios/CollabPress/issues/24 If you’d like, you can apply that patch manually to your CP installation – it’ll be fixed in the next release.

Boone, you are an animal. thanks for doing this (and I’m watching the bptrac. getting very excited)

@boonebgorges
Boone – are there any plans to integrate CollabPress and BuddyPress Docs, btw? That would be a potential game changer. Right now I’m designing around BP/WPMU so I can keep the task attachments for different groups in different media libraries – i.e private from each other, as each group is a separate organisation. This means using CP on a separate site per group.

Using BP docs instead of, say, Word attachments might solve that as there is privacy built in. Just hoping…

Cheers, Roger.

Ardibee – No near-term plans, but it’s an interesting idea. Can you explain in more detail what you’re envisioning?

Hi Boone – sure thing.

I’m building a WP/BP site for small teams of volunteers in social housing, to help them manage small projects and organize their team meetings. The projects involve reviewing lots of documents, each of which will be attached to project tasks as an item to review. Projects will also involve each group writing up their findings – ideally saving their work-in-progress [a document] as an attachment to a project task (e.g. “Write up review findings”).

Both the input documents and the output document will contain sensitive information so I can’t leave different groups’ documents all stored in the same media library – not without some pretty hefty restrictions on accessing media… which would probably prevent users attaching stuff in the first place.

The second part of each project (writing up a collaborative document as a team) is an obvious candidate for BuddyPress Docs but I would like it to be attached to a task so that over time the users don’t lose it. In other words, if they can remember the title of the project then they can find their documents again. That might sound odd to seasoned IT users but the target audience for this site are _not_ good at filing stuff.

The first requirement (attaching various documents provided by a housing authority) still requires a bit of thought as these are likely to be pdf, Word, Excel and PowerPoint… (I’m not sure how I can manage these other than to auto-categorise them somehow with CPT-Onomies based on the parent task and review.) Even with decent taxonomy I still can’t think of a way to keep the attachments private to each BP group, so I may have to go for multisite in addition to using BuddyPress for the community networking between the different groups.

I’d love to keep it all BuddyPress though. Any ideas?

Thanks,
Roger.

… so to summarize the easy win:

An option to “Attach new BuddyPress Document” to a task in CollabPress would be nice. Users can kick ideas around through the regular comments feature but when it comes to creating a structured document at the end of a project, it would be great to let them collaborate without leaving the comfort of a structured project and to-do list.

I’m still open to suggestions on keeping the other attachments private… any chance of introducing group-specific (private) media libraries to BuddyPress? ??

Thanks for the additional details, Ardibee.

> An option to “Attach new BuddyPress Document” to a task in CollabPress would be nice.

This is a good idea. Would you mind posting it at https://github.com/boonebgorges/buddypress-docs/issues? (I’d put it in Docs, and allow it to hook into CollabPress.)

> any chance of introducing group-specific (private) media libraries to BuddyPress? ??

It just so happens that I’m about to start work on extending BuddyPress Docs to handle file attachments, and in the process I’ll be building out an API for upload access-control that will tie into BP groups. So, if you wait a couple months, it’ll be publicly available in Docs. That doesn’t help much with CollabPress (at least not right off the bat), but at that point you could probably start using Docs for uploads rather than task attachments (and maybe a bridge could be built in the future).

Sweet! Thanks Boone. GitHub issue opened.

Back to the drawing board on my website now…

Boone Gorges
Member
Plugin Author
Posted 1 month ago #
Thanks for the report. It looks like it is a CP issue (rather than BuddyPress Docs). I’ve corrected it here: https://github.com/WebDevStudios/CollabPress/issues/24 If you’d like, you can apply that patch manually to your CP installation – it’ll be fixed in the next release.

Hey, I’m having this problem too, but the link the plugin author directed to at github (quoted above) is primarily a redirection back to this thread so it was really not very helpful — well at least not for those of us who are not coders (well, me anyway), sorry. I know enough to be dangerous so if you put up specific instructions of what code to mod where to accomplish what you mention so briefly in github, I can do that I believe.

Also, and I’m not sure if its because of this conflict or not, but when I click on the group’s listing/icon on my home page or from any other listing of groups on my site, it goes to a 404 error page. The reason is because it’s adding the term “forum” AFTER the actual url for the group. For example … https://www.websiteurl.com/groups/groupname/forum when it should be https://www.websiteurl.com/groups/groupname. How do I fix this?

Thanks.

Does CollabPress and BuddyPress Docs work fine now?