Forum Replies Created
-
Idotter –
Couple questions – Is your avatar upload process working? Group Documents shares some code with avatars, particularly with the directories is uses.
Also, you mentioned this occurs after you upgraded to 0.3.1 – Did you have version 0.3.0 working? Or did you go straight from 0.2.5 to 0.3.1? The reason I ask, is that 0.3.1 didn’t change anything in that section of the code from 0.3.0.
Sorry, that was a lot of numbers to keep straight
In reply to: Is anyone using Buddypress-Ajax-Chat?Wow! That is sweet. It’s working fine for me in firefox as well. This would totally be a awesome plugin.
In reply to: Custom Page that Filters GroupsWhat specifically is stored when a group is marked as “featured”? Do you give your radio buttons a value attribute? How are you storing it (is the actual variable name $bp_featured_group?).
In reply to: Custom Group PagesI don’t know of any existing efforts to customize group images or backgrounds, but it does sounds like a good idea for a plugin. Using the group exension API (https://codex.buddypress.org/developer-docs/group-extension-api/) it’s fairly easy to add another page to the group admin menu. You could call this menu “Display options” and let group mods change settings. You’re plugin could then check the settings, and display stylesheets/banners as appropriate. It would take some development time, but I think it could work smoothly.
This would of course be heavily theme-dependent, not only for the implementation (div position and such) but also for the design (changing the backgrounds while keeping the feel of the theme).
This has now been fixed. I wrote a post detailing the 0.3.1 release here:
https://buddypress.org/forums/topic/group-documents-031-tracking-sorting
Cheers.
Nice!
In reply to: I need helpnickmy,
Theme development is fairly involved, in order to get the most out of these forums, you should make your question as specific as possible.
If you wan’t to customize a theme, but don’t know any PHP, you’ll probably need to hire a developer.
Rossagrant, I wrote a plugin for a client to make a default forum topic when a new group is created. I’ve been thinking about putting it in the repository, but in the meantime, you can download it from my personal site:
http://www.code-zen.net/2010/buddypress-default-forum-topic/
Note, you need to open up the PHP file and modify the title and text to what you’d like to use.
Please note, this will likely not work with the SQL script you’re using, it depends on a trigger event that is fired when the group is created with BP.
Edit: this was in response to default topics, three posts up
Wow,
You are right my friend (I get the same error). Thanks for pointing it out, this is a bug.
WHAT DO I PAY MY BETA TESTERS FOR?!?
Oh wait, I don’t

This will be fixed in the 0.3.1 release, which will come out sometime in the next few days.
In reply to: Group Documents 0.3.0 ReleasedYou are correct, public groups are available to everyone, and private groups are only available to people who have registered AND joined the group. There really is no “site registered only” option.
In reply to: Group Documents 0.3.0 ReleasedThanks for the feedback, I’ve had someone else suggest that as well. My thinking is that documents are currently consistent with the group access levels. For example, if you can seen forum topics and members of public groups, you should be able to see documents. If there’s group content you only want group members to see, then it should be a private group.
I see your point for encouraging outside users to sign up, I’ll consider adding an option for that behavior.
@pjnu, Yes, it won’t be an issue anymore. Thanks for your patience.
In reply to: Group Documents 0.3.0 Releasedit varies slightly depending on your configuration.
For WPMU:
wp-content/blogs.dir/blog_id/files/group-documents
For WP
wp-content/uploads/group-documents
Also, they are now stored in subfolders according to the group id they were uploaded to.
In reply to: Group Documents 0.3.0 ReleasedPjnu,
Well. Um. It means your documents folder has been deleted in the automatic upgrade process. One of the major changes for this release was to move the document storage to a different place for that very reason.
I’ve been trying to get the word out to everyone to manually upgrade, but I’m sure you’ll be amongst a great many people who opt for the automatic upgrade.
The error your seeing is a byproduct of the automatic upgrade that I didn’t catch in testing. I’ve updated the repository, so any freshly downloaded versions won’t have that error.
In reply to: 404 on every linkHmmmmm. Is there a URL we could check out?
In reply to: Invite Friends From ProfileYou have mail.
In reply to: New Plugin: Friends-Only Activity StreamAwesome! Sounds super useful.
In reply to: Invite Friends From ProfileI just finished something similar for a client. They wanted group admins to be able to invite people to their group via email.
My plugin adds a text field below the standard group “invite friends” section for an email address. It then sends a message via email to the person, guiding them to the site registration page. It also tracks their email address to the group they were invited to. When the new user registers, it skips the whole send-and-approve-group-invite step; they are automatically added to the group.
Let me know if it sounds like there’s overlap, I’d be happy to post code or whatever.
In reply to: Group Documents 0.3.0 ReleasedThanks everyone so far.
-I’ll look into the info you posted about displaying previews. Other people have suggested previewing. My main concern is kepping the UI clean. It’s been added to my list.
– Sorting is definitely on my to-do list
– I hadn’t thought of the per-group permission settings. I like it though. I’ll look into it.
– Thanks again for the French translation.
– I think at this point, the name is pretty ingrained. It would take a lot of code-rewriting to change it. I would encourage people to edit/create local translation files if they want to change the menu display text.
In reply to: Accessing media redirects to 404 errorWow. After 3 days of banging my head against a wall, I finally figured it out. It was so simple.
There is in fact no difference in the way BP 1.1 or BP 1.2 handle the redirects and files directory.
My code was appending a slash to the file name (during storage) in BP1.1 (I had to do conditional code because 1.1 doesn’t have bp_core_avatar_upload_path).
Thus, in my BP1.1 installation, I was trying to access a directory.
When I had verified the file was on the server, I was using “ls -l”; I was so busy looking at filenames and permissions, I missed the little “d” at the start of the line.
D is for “Doh”.
FYI, I found in my research that blogs.php is in fact being called, but of course, rewrite URLs aren’t shown in the actual URL, so it was silly to come to the earlier conclusion.
Or just a plugin that loads a stylesheet wrapped in an IE6 conditional comment.
In reply to: Accessing media redirects to 404 errorRay,
Thanks for the replies. I was using the full wp-content/blog.dir/group_id path as that’s what avatars and several other components use. Which brings me to your next question – files outside of group documents. Yes, they’re working, even with a very similar path.
Check out the avatar for this group (The dog photo):
http://wpmu.sixtysixinc.com/wpmu2.8.6/groups/my-group/documents/
It has the exact same url structure as the documents:
Yet, it’s not getting redirected, and it works fine.
In reply to: Accessing media redirects to 404 errorI’m not a RegEx pro, but looking at the above rules more carefully, something still doesn’t seem right to me.
RewriteRule ^(.*/)?files/$ index.php [L]
– URLs ending with ‘files/’ go to the home page. (doesn’t apply)
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
– Make an exception for urls in the plugins folder (doesn’t apply)
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]
– Urls with ‘files’ get directed to blogs.php?file=… This seems closer, but it’s not actually being directed to blogs.php (or maybe it is, and it’s being directed back to the image the the file variable still appended).
In reply to: Accessing media redirects to 404 errorRay,
Yes, that was my first instinct as well, and yes, there is something similar in the .htaccess file.
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]Here’s my issue: I have another test install with the exact same .htaccess file, and it’s working fine.
WPMU 2.8.6/BP1.1 – Doesn’t work
WPMU 2.9/BP1.2 – Works
Same .htaccess
Here’s an example of the same path, in a different install, that’s working:
In reply to: Request to all developers and plugin writers+1, not only will this make your markup not validate, but it can also cause problems when trying to extend using Javascript & CSS. It’s not difficult, just remember, don’t use id’s inside loops. And if you do, append something unique to the string.
In reply to: Deep integration of Google DocsNo news from here. I still find it interesting, but haven’t had any time to take a closer look.