Hey great work, I know you're still in pre-production stage, but you've saved me some time and I wanted to toss notes in on what I've found already and things which may be on your list but would be great to see fixed.

First, the caption size on the image is set to 255 chars in the column, but the form field limits you to 128. I know it's just an option in the forms array, but it'd be nice to get those in sync.

Also, while you have the weight field in the form going from -20 to 20, the column is set as UNSIGNED, so you really only can use 0 - 20 ;)

I'd like to hear what else you want to see as default information for the different content types, as I'd love to see more standard fields for each type by default, for example credit, exif info, and notes on each image, bitrate, encryption, length, credit for audio and video, publication and release data for dang near all etc.

That would then work well for allowing many other ways to generate galleries, exposing data, sorting for use and such without everyone having to go in and create custom fields on each type, and naturally just ignoring them if they aren't used. I'll be happy to help contrib more too once I get this current site out the door and can breathe again.

Thanks for the module!

Comments

konfuzed’s picture

konfuzed commented

Also, the preferred size for viewing does not seem to be working in the folder listing, even when I've manually created derivative images (which works in the media attach tab though) so that large prepress size images we link to with derivatives QUICKLY fill the screen and browser cache (think 2meg files each).

I'll have a live site in a week to show you what I mean directly at least.

rhys’s picture

rhys commented
Status: Active » Fixed

Ok, I fixed up the discrepancy within the database table and the weight (I like the negative numbers also), it's now a signed integer. I think I've solved the caption size form problem, and on the details for the attached media, I'm still progressing on improving the media_attach module as soon as possible. It will have a default derivative display mode for each of the various types.

You can start a new issue on the the question of default fields. I'm sticky currently to the way the database is designed, although having the fields can be done through the metadata process, and quite a few of those mentioned will probably make it in. But definitely start a new Issue for that since it's a different question than these others you've referenced.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.