BuddyPress.org

@intimez

Interesting. Okay, I had this issue with BP 1.2.5, 1.2.5.1, and 1.2.5.2 on WPMS 2.9.2 and WPMS 3.0. I just saw a note from @nuprn1 on that Trac ticket that he did not have this issue specific issue but a related one that the suggested patch fixed.

@intimez

Which versions of BP and WP are you running?

@intimez

Will this provide complete privacy for all of the users info? Or just on their profile?

@intimez

We’re in the process of moving BP Album+ from the WordPress SVN to Google’s SVN because it’s a much better setup.

Nightly builds will resume soon.

^F^

@intimez

do you have your Forum-component activated or deactivated ?

@intimez – Per BP Roadmap – BP 1.4 Import/Export of all BuddyPress user data
– unless of course someone makes a plugin for that function beforehand 🙂
Even so, nothing beats database backups

“–notification when using @mention in wordpress side (blog, comments, etc.)”

@intimez i’d imagine easy to set that up – just reuse the notification/atmention functions and hook it into wp. – the comments already hook add_filter( ‘pre_comment_content’, ‘bp_activity_at_name_filter’ );

@intimez I don’t know if I understood what your idea is, basically you want that every member generated content has to be approved before displaying in the site?

@thekmen @intimez Keyword tagging functionality in BP Album+ has not been completed yet, so trying to use tags at this point can result in totally unpredictable behavior.

^F^

@intimez Defect has been confirmed on my test system. We are working to fix it.

^F^

@intimez Each time you activate and deactivate the BP Album+ nightly build, it will add duplicate entries to the sizes table. So somehow, it got activated/deactivated a couple of times while you were experimenting with it. Just go to the cache screen and delete the duplicate sizes. Or deactivate the plugin, empty the image sizes table, […]

@intimez

Wow, your web server just does *not* like us… 🙂

Okay, I have added error suppression to the filesystem command that is running on line 640. So try tonight’s build when we post it, and hopefully the error should be gone.

Thanks!

^F^

@intimez Because you forgot to delete all your bp-album DB tables and files before upgrading to the next nightly build.

Thanks!

^F^

@intimez

Okay, well delete all bp-album DB tables, cache directories, plugin folder, etc. Install latest nightly build.

Does it still do it? Then try creating a new album, not uploading any content, and viewing the member’s list of albums. Does the default album image (purple question mark) display properly?

^F^

@intimez

I tracked this error down, and it looks like it’s being caused by the server not being allowed to write to your wp content directory.

Please check the file permissions on these directories and report your results.

Thanks!

^F^

@intimez Its a lot more sophisticated than you think. It limits to a certain number of posts per day. It groups by album. If you don’t post for a while it makes a new post with less than the max number of items in it. Basically, it acts like Facebook’s activity stream. If you run a […]

@intimez

+ +

= 11 pictures.

Version 0.1.9 groups images in activity stream posts to avoid flooding the stream with posts. It’s fully configurable on the admin menu. Play with it … 🙂

^F^

@intimez You probably have a really cheap web host or a server that is not set properly. Go to the “Debug Tools” screen, and paste a message with a copy of the information it prints out.

^F^

@intimez @thekmen That’s normal. Error #1: It happens because I’m using that screen to run test code right now. I think it also dumps your cache and I think it adds a bunch of extra image sizes. lol. Just delete all the BP Album+ DB tables, delete all your uploaded content, delete the cached image directories, deactivate, […]

@intimez That’s a fantastic error and we’d love to fix it! But, you need to post a list of steps needed to make the error happen. What did you do, upload, click …what settings did you change?

Thanks!

^F^