Forum Replies Created
It looks funny in the bottom picture because the CSS styles in your theme aren’t taking BP-Album into account.
We designed the plugin to be easy to integrate into themes …everything is in a single div and all our styles are namespaced. Figure out how you want it to look and update your CSS to put bp-album’s content where you want it to be.
The edit and upload pages are algorithmically generated inside includes/bpa.screens.php
In the interest of preserving your sanity, do not modify that file! Unless you have a deep understanding of PHP you’ll probably break the plugin, and even if you do, your changes will be overwritten on every plugin update.
Instead, use your browser’s debugging faculties “Right Click” -> “Inspect element” in Chrome, to learn about the CSS styles we use, and then add appropriate CSS to your template CSS files to modify the look of the page as you desire.
Is it *only* in es? Contact us via our GitHub page.
We’re doing just fine, thanks …
The reason the sources haven’t been updated in over a year is because the app is mature and nothing has needed updating. That’s a good sign in my books. It means you can build on top of our stuff without having to worry about it breaking.
For fast responses (like 24 hour turn time) contact us on GitHub:
People post random support questions about BP-Album all over the Internet, and it can take *months* for us to find them.
We were of the opinion then that we must create a basic usable version and start on WordPress.org plugin repository. When we submitted the first very minimal version, we weren’t aware of the GSOC project till WPMU wrote a blog post about it.
I can accept that we both may have started using the same name without knowing about each other. But actively trying to take the BuddyPress Media mark from us after we’d clearly established it as our brand and had been using it for almost three years, was a bad thing to do. If this were anything other than an open-source project, you would have gotten sued.
True that. Let’s merge WordPress, Drupal, Joomla and all other popular CMSes and create this superhero CMS. Let’s merge BuddyPress, elgg, Social Engine into one and have the best social networking solution.
That’s not possible now. All of those platforms have diverged so far from each other, its impossible to even reuse code between them. …But imagine what could have been achieved if, before they went their separate ways, all those developers said “let’s build a common core, so we don’t need to repeat the same work for hundreds of different things” and then “based on that common core, let’s each add our own 20% code to make it into what we each need”. That could very well have killed Facebook.
The way we deal with our users is diametrically opposite to yours. We want a leaner, lighter and tightly integrated with WordPress plugin. You want a plugin that has minimal dependency on WordPress or BuddyPress. We want to release features as and when they are finished. You want to release everything, at once.
No, its not. We are both on the same journey, but your team is where our team was 26 months ago …before we learned about unit testing, before we hit the scaling and cache problems, before we had to throw out our entire codebase and start over. We do not have minimal dependence on BP and WP because we are arrogant, we have it because it allows the BP and WP teams to change large parts of their plugins without breaking our plugin. You need to do all of these things too, or your users will think you are bad developers when your plugin breaks again, and again, and again.
Like you, we strive to release “as early as possible, and as often as possible”. But before we could get to that point, we had to solve the Unit Testing Problem, the Scaling and Cache Problem, the Front End API problem, and the Page Routing Problem (which because of the …trouble… earlier, I can’t provide a link to right now). And don’t even get me started about RBAC, ACID, and cache coherency, all of which are fundamentally broken in WordPress.
It took man-years of work, and over $100,000 in developer time to solve these problems.
Your team is welcome to use what we have created to help you get your project working faster, but I think we can do even better than that…
Your team has independently solved the Transcoding Problem, but lacks a back-end WordPress framework to properly control it. Our team has that framework.
And then there’s all the requests we get from people that want customizations for BP-Album, well over $100K worth so far. We’re so busy with BP-Media, we just send them to jobs.wp.org right now. Maybe you could provide these services.
Your team’s monetization strategy seems to be “write a base platform and sell premium plugins that increase its functionality”. We’ve built this model into BP-Media, but have made it very easy for other developers to extend the core platform, so we get rapid growth and everyone can share in the profits.
So stop hiding over there in the corer and come join us. This is GPL code. If you want to go in a different direction two years from now, you can fork it and move on while still being able to re-use code.
In the worst case you’ll get very good at coding very fast and skip 2 years’ of development work in the process. In the best case, we’ll write an amazing plugin together in a matter of weeks, and perhaps some day get bought-out by Facebook or Google for millions of dollars to prevent us helping their competitors.
In open-source, the best strategy is NOT to compete, it is to work together. If the ten thousand developers that have made large contributions to Linux had tried to create ten thousand different operating systems instead of working together to build something awesome, the Internet as we know it probably wouldnt exist.
If people in this community spent more time writing code, less time writing BS on the forums, and cooperated with established projects to get a given problem solved, BuddyPress could be a world-class social media platform.
Im going to get back to coding now. I really wish more of you would do the same.
I work 14 hours a day 7 days a week. Today is my only day off for the next two weeks.
I wanted to add group-albums capability to BP-Album today, but instead I had to spend half of it dealing with other plugin developers trashing my team on the forums and the other half trying to find actual BP-Album bug reports amidst the ruins of bp dot org.
Q and A:
@oceanwidedesigns The twitter feed hasn’t shown any updates since before Christmas, I can’t get the tracker to load, and the google code site is all broken up
Thats because Google removed RSS feeds for Google Code projects in December 2012, and we cant publish updates from the new projects GitHub repository for legal reasons.
@hnla And an honest appraisal of when they think bp-media may see the light of day as a RC or Stable, it’s been in development for nearly three years, yes it’s complex dealing with media but three years, even in a OS volunteer project should be close to producing a stable version or at least a core principle.
Its coming along just fine, and the finished product will rock your world. We need to have BP-Medias parent project online by 2013-06-30, so we might consider letting developers that we consider trustworthy have access to the BP-Media Git repo around that time.
@saurabhshukla The second BuddyPress Media has never been released, officially. BP-Album was released after BuddyPress Media. General common sense dictates that if you have an existing plugin by the same name, you go ahead and change the name. We all do that. It’s obvious that otherwise the users will get confused and all three parties lose out, both the development teams and users. Which is what just happened here.
I agree. A media manager for BuddyPress will logically be called BuddyPress Media. And that is why when we started off, our plugin was called BuddyPress Media.
After this happened, BP-Album developers also decided to expand BP-Album into a higher realm and for some reason decided to disregard the fact that a plugin by that name, already exists.
Except, your plugin wasnt called BuddyPress Media, it was called Kaltura BuddyPress Media Component. Lets not be spreading incorrect information here …
Could you please set up and clear up what the heck we can expect? Honestly? I’m finding it very odd that you’re responding to stuff in the plugin repository after a year and a half of telling people you ignore those threads and only respond to ones here.
The bp.org team deleted the 3rd-party plugin forums and moved them to a tag-based search several months ago, taking away our ability to moderate posts. Then rtCamp flooded the keyword search by tagging all their posts with bp-media, and then rtCamp started claiming they were the BuddyPress Media dev team.
So we just said screw it, let them burn …and focused on writing code instead.
But darn it, you guys are so persistent. Everyone started posting on BP-Albums wp support page and 2 weeks later theyd turned into our new support venue.
And you know what …secretly, we really like it …it works a lot better than bp.org.
BP-Media has not been abandoned.
Its been temporarily closed-sourced …and you have the developers at rtCamp to thank for that.
Before I get into that, lets get our open-source history straight:
Late 2008 – A developer called talk2manoj creates bpPicture Album, the first image hosting plugin for BuddyPress.
2009-10-05 -talktomanoj posts last update to bpPicture Album, and abandons it. Developers francescolaffi and foxly independently fork bpPicture Album and start building new image hosting plugins.
2009-11-10 rtcamp posts first version of BuddyPress Kaltura Media Component to wp plugin repo
2010-03-11 – francesolaffi and foxly merge their plugins, and release bp-album.
2010-09-01 – foxly and francescolaffi launch buddypress-media, and begin using the short form bp-media as the plugin stub in development versions.
2010-09-25 – rtCamp posts final update to BuddyPress Kaltura Media Component and abandons it.
2010-09-26 to 2012-08-2 – Over the next TWO YEARS, the BP-Media team continues development on BP-Album and BP-Media, enlisting two new core developers, posting over 1,864 commits, 13 releases, and handling 475 different support threads. Nothing is heard from rtCamp.
2012-01-02 – BP-Media moves their main code repository from Google Code to Github, claiming the BP-Media project name.
2012-08-03 – rtCamp releases a plugin called BuddyPress Media on the wp plugin repository.
2012-08-22 – Ohloh contacts the BP-Media team, asking about somebody trying to register BuddyPress Media 2 on their site. It turns out to be rtCamp.
2012-09-07 – rtCamp users begin posting help requests for rtCamps plugin on the BP-Media team’s Google Code page. We help them anyway.
2013-01-05 – BP-Media publicly invites rtCamp to join the BP-Media development team. They decline.
2013-01-08 – After seeking legal advice, BP-Medias parent company switches the project to a closed-source development model until its ready for release under a new brand name.
2013-02-01 – BP-Media hires @wickedwolf, their second full-time developer.
2013-02-08 – @modemlooper joins the BP-Album and BP-Media dev teams.
Why don’t we just merge our dev teams together, use your current BuddyPress Media as an intermediate step, between “BP Album” and “BP-Media 2.o”, and get a better product out faster?
Are you sure you’re using the right templates, or have the code pasted in your template file? It’s working perfectly well on several sites I upgraded today.
On BP-Album’s config screen, don’t put “0” as the max_whatever_value for a given upload category.
If, after changing these values to something other than zero, you still can’t upload, then there is something wrong with your server or base WordPress installation.
I’m just going by what jjj said when we were chatting on Skype last week.
We’ve already forked significant parts of WordPress, and it’s our eventual goal to have BP-Media able to operate without WordPress installed on the server at all (although still be able to interact with it if it is).
As for progress on BP-Media, we’ve started releasing blocks of code as individual plugins as they get completed:
..so, overall I’d say there’s been a fair bit of progress on BP-Media …
Complain as you will about the build time, we’re not releasing the next version of BP-Media until it works efficiently and reliably, has been thoroughly tested, and is properly documented.
If the WordPress team had our level of discipline, 90% of their so-called releases wouldn’t be necessary.
Vote for us
We’ve posted an updated version of BP-Album that fixes all reported problems.
They did it for the top 20 or so plugins.
BP-Media has more threads than half the top-level support forums on the site, and the most out of any plugin.
Buddypress.org has always been our primary user support venue, and adding us to the forum tree will help our team continue to deliver the best possible support to the largest number of users.
Site could be considered NSFW.
…depends where you work…
Compared to some help requests I’ve answered, this site’s rather tame.
CSS design is a very complicated subject. The base BP theme’s CSS file is almost 2,500 lines long and has a vast and intricate style tree. Answering a RFC (request for comments) on a given set of changes to it is many hours of work, and is beyond what can be handled on these forums.
If you have a specific problem, eg: “When I set style X to Y, the level 2 menus explode” or “How can I invert the color scheme”, the users here will be happy to help you.
Also, be aware there are sweeping changes in the works for BuddyPress’ template system. The core development team is currently re-designing the entire template system to use page-fragment injection. In theory, this will allow BuddyPress to use almost any WordPress template set – not just ones designed specifically for BuddyPress.
I’d estimate they’re about 6 months away from release on this.
`Fatal error: Call to undefined function wp_create_thumbnail() in /home/content/xx/xxxxxxx/html/wp-content/plugins/bp-album/includes/bpa.screens.php on line 394`
This one is happening because WordPress REMOVED a function from the WP core that BP-Album uses.
We’ll code around it.
This is at least the 10th time in the past year that either WP or BP has broken our plugin, and I’ve had enough of it… as of today, with the exception of the admin back-end, we will begin modifying BP-Media such that it does not use ANY functions in either WordPress or BuddyPress.
As we have already achieved with Razor, the goal will to be to have BP-Media capable of operating WITHOUT WordPress or BuddyPress installed on the server, but still interact with them if they are.
Actually, because of the popularity of BP-Album/BP-Media, the BuddyPress team has hard-coded us into the site.
This forum will remain our primary support resource for the foreseeable future.
A new version of BP-Album, which fixes the “Missing argument 2 for wpdb::prepare()” defect will probably be released in the next few hours.
The beta version of BP-Media is probably 1-2 months out.