BuddyPress.org

@jordashtalon

We do not currently have the plugin linked to the global search function, but we’ll get it added as we continute with development.

^F^

RE: Hey Foxly is it possible to use NetBeans to edit files live on the server? Was just curious because I want to test it out, I currently use GVim.

It depends what you mean by “Live on the Server”.

If you mean “Live on a LOCAL development server”, yes, NetBeans excels at this job. It even automatically refreshes modified files, so if you’re dumping debug info to a text file and have it open in NetBeans, added text will show up in the display sort of like a terminal window.

On the other hand, if you mean “Live on a remote server”, yes it can do that as well. Ideally just by mounting the remote server HTTP directory as a network drive.

I think NetBeans might also have FTP functionality, but I haven’t tried it yet.

^F^

@jivany

BP Album+ has a very straightforward roadmap: systematically clone the media management features of Facebook, Flickr, and YouTube …and do it as quickly as possible.

In order of priority, we’re working on the following features:

1) Batch file uploading (2 -3 days)

2) AJAX image sorting (about a week)

3) Demo templates (that show all the features, emulate facebook and flickr, etc) (about 10 days)

4) Albums for groups (about 2 weeks)

5) Streaming audio and video (about 3 weeks)

Then…

6) Disk quota

7) Tight integration with BP’s tagging and search functions

Photos widget, “your friends’s recently updated media”, etc

9) “Like” feature on media items. (Possibly dependent on BP, as I think they’re adding capability to the BP core)

10) Inappropriate content flagging

Then…

At that point we basically match Facebook, Flickr, and YouTube feature-for-feature.

I’m sure after that we’ll get lots of site-specific feature requests (can you add a feature that lets users doodle on their photos, etc) but the core features give you what you need to run practically any website.

^F^

@gian-ava

1) You can’t just “switch” from version 0.1.7 to 0.1.9.2, because 0.1.9.2 doesn’t have an upgrade routine (because its a beta). If you install it on a server that already has a 0.1.7 install, all sorts of strange things will happen.

If you really, really want to upgrade to 0.1.9.2, you’ll have to delete all of your user’s uploaded images, delete all of 0.1.7’s database tables, then install 0.1.9.2; but for systems with existing users that have uploaded a lot of media, it’s probably just better to wait until we put out the next release version.

2) BP Album+ works just fine when you install WP in a subfolder. The reason it doesn’t work properly on *your* installation is because you’ve used some “hack” posted on the Internet to modify your installation to hide the subfolder from the URL displayed in the browser.

Guys, there is a lot of VERY BAD advice posted on the Internet about how you can cut and paste code into WordPress to do various things, and a lot of this advice is incomplete or wrong. The hack you’re using only handles *one* way plugins get the base URI, and as you install more plugins you will start to get all sorts of problems.

If you want to install WordPress in a subdirectory, the correct way to do it is to set it up as a virtual host in your apache config file, or using a redirect:

Redirect: (OK) http://www.youtube.com/watch?v=pC_HNbly6mI

Virtual host: (Best) http://www.youtube.com/watch?v=HW2xWJpjKQk

3) It’s relatively easy for us to make the URI’s to media items in BP Album+ configurable, no matter how somebody sets up a WP installation, if that’s what you guys want.

…but based on my research so far, we *cannot* fix the problem with images not showing up in the activity stream on WP installs that are a) in a subdirectory and b) not using a redirect or virtual host method of URL shortening, because of the way *BuddyPress* stores activity stream attachments.

How BP Album+ stores an image URI:

[$offset] + [ / album / 04 / kittens_15.jpg]

How the BuddyPress activity stream stores an image URI (last I checked…. I will research this more when I have time):

[ http://www.example.com/wp-content/blogs.dir/01/album/04/kittens_15.jpg ]

So when you use a hack to dynamically change your base URI, BP Album+ can handle it (because we dynamically generate the full URI), the BuddyPress activity stream cannot handle it (because it uses a static URI) and the activity stream post items break.

But the bottom line is, all of this is happening because you haven’t set up your WP installation properly and are using “hacks” off the Internet to mess with your site.

Set up your WP install properly, and you won’t have problems.

Thanks!

^F^

@gibbyesl

RE: “testing the new beta. can’t remove someone who tagged themselves I click remove but nothing happens”

Defect has been confirmed on my dev system. We will add it to the queue.

Thanks!

^F^

@gian-ava

Okay, well clearly you’re smart and you’ve put some effort into debugging your system.

I will add a config option to the next BP Album+ beta that lets users set a custom path for activity stream items. But… it will not fix your existing activity stream items, and if you ever change your directory structure after using the option, you’ll lose all your activity stream items again.

Remember, this is a limitation in BuddyPress, not BP Album+

Still, your best options are:

1) To put your WP installation at the HTML root, which will give you the best compatibility with plugins.

2) If you’re running multiple installs in a single HTML root, use virtual hosts.

3) And if you don’t want to learn how to use virtual hosts, you can probably use a redirect in your .htaccess file as you described (that’s what cPANEL does). Note that there could be SEO implications with using a redirect.

Thanks!

^F^

@Xevo

We’ll certainly try.

But remember, we are *not* adding “embed content from fifty different free streaming video sites” type functionality.

More like the top 5 sites, and that’s it.

Depending on free sites to host your media content is BAD …because every time the other site changes something, it breaks the plugin, and then *we* have to figure out how to fix it for the changes the other site has made.

We can do that for a few sites, but not all of them; otherwise we’d never get any work done on other features. This is why Facebook only allows embeds from a few selected sites, and hosts most of their content themselves.

If you’re running even a moderate sized social community, eventually you will have to do the same, start hosting your own media files.

^F^