foxly

I only know about twenty Russian words, but “at-lich-nah” (thanks) for the bug report.

You’re the first person who has ever reported this problem. I suspect it was cause either due to your web host or your ISP. If you can make it happen repeatably, follow up with us via our issue tracker on Github:

https://github.com/BP-Media/bp-album/issues

The task you’re describing is a major undertaking. There’s no simple way to take a data dump from a site like Ning and import it into BP-Album. You’ll have to hire a developer, have them take a look at our source code, and write an importer script. I’d estimate it would be a full day of dev time.

It depends on what you mean by “full sized image”. BP-Album resizes uploaded images to fit within the maximum image dimensions you set, to save disk space. If we didn’t do this, users could upload huge files (20MB+) and use up all your disk space.

The code above that @deepbevel posted is what most users would be looking for in this situation. Thanks!

I’m the lead developer of this plugin, and last I checked its still supported … ??

BP-Album’s code is stable now and rarely needs updating. But, on the rare occasions when WP updates do somehow manage to break it, we’ll fix it as soon as possible.

Disable all the plugins on your site, then re-enable them one at a time until you find the cause of the problem.

^C^

This is the strategy my team has adopted as well. Calling something “BuddyPress-MyCoolPlugin” is just too long, and it distracts from our brand.

^F^

The links you provided return 404’s. Please post valid screen caps of the problem.

^F^

Please add this as a ticket on BP-Album’s Github page, and post all of this info (including the trac ticket) into it.

Thanks!

^F^

Resolved.

BP-Album is the most popular, most reliable, and best supported media hosting plugin for BuddyPress.

We created a next-generation plugin for media hosting on BuddyPress that included Audio, Video, and PDR capability, as well as multiple albums and group albums, and named it “BP-Media”.

Unfortunately, a year into the project, some web dev shop in India decided to release a much less capable plugin and also name it BP-Media. This was very confusing. So we changed the name of our plugin to a new secret name, and will be releasing it under the new secret name in a few months once we have the name copyrighted and have all the domains and social network handles locked-down.

^F^

Well isn’t that clever … ??

I like that strategy. We’ll add it as an option to Razor for developers who don’t use transactions in their test fixtures.

^F^

PS: We’re now writing documentation for Razor. Look for it on Razor’s GitHub Page

Alright, since there’s clearly some interest in the plugin, we’ll write some documentation.

To answer your questions:

Do I always need the testplan.php file?

Yes. When you call razor using the –plugin=my_plugin option, it looks for the /plugin_name/unit-test/ folder and loads the ‘testplan.php’ file inside it.

Does WP Razor automatically wrap DB queries in a transaction, like the official unit tests do, or do I have to manually clean up the database?

No. And I doubt the WP database class wraps queries in a transaction, either.

1) This would make it impossible to test any MySQL table type other than “InnoDB”.

2) It would make it impossible to test database queries that involve transactions because MySQL doesn’t support nested transactions.

3) It would make it much harder to debug queries, because you wouldn’t be able to examine the table state following a test, or if a test crashed mid-test.

Razor uses a separate database, typically called ‘unit_test’, and loads a WordPress image of your choice into it. Tests are run against this image, and the image persists in the database following a run so that you can examine it if necessary. A fresh image is loaded at the beginning of each run, and you can load a fresh image before a given test if you need to.

How does QUnit fit into all of this?

qUnit is used for testing JavaScript used in a plugin’s front-end and admin screens. qUnit tests are currently run from a special page in the plugin’s admin back-end, but we’re probably going to build an engine that runs them using node.js or zombie in the future.

^F^

The current version of BP-Album requires at least WordPress 3.5

^F^

You cannot make albums for groups using BP-Album.

^F^

Marked as resolved.