I've got some isues with acidfree which I need to solve... (been bussy with a comunity site where 1000+ users can upload their photo's, video's and sound... )

maybe there are a few here who have the same isues and can help a bit ? :-)

my current isues are with acidfree "Per user albums" enabled
version: acidfree.module,v 1.62.2.53 2006/09/08
version: filemanager.module,v 1.18 2006/09/14
drupal 4.7.3

1.
When a user selects no album (Standard when you hit "create content/acidfree media") the uploaded photo goes to the root album, and is not tracable for the curent user, so the photo seems lost for the user.
Also the photo doesn't show up in the root album.
2.
File path is incorect ".../files//active/0/20_large.jpg"
3. (not so sirious but still)
When a photo is created it gets the type "acidfree album" wasn't there a type "acidfree photo"?

I've also posted these isues here: http://drupal.org/node/84868
But maybe people at the forum have a faster sollution/work-arround :-)

Comments

Jeff Burnz’s picture

Yes it's rather a pity about the current state of AcidFree, totally unusable in a community site imho. I really like AF but it has to be fixed before it becomes usable.

The rather heavy handed branding doesnt help either, I wanted to use it in a Swedish website, but no one has a clue what the hell 'acid free' means, and it's a mare to change it.

Sorry cant help you out, I went with Gallery2 after a long and dissapointing search for decent user galleries in Drupal, very sad that I was basically forced to do that, however it was a cake walk to set up and theme etc and does what I need.

And before we hear the compulsory 'if you want it do it yourself' comment - not everyone has the time or the budgets to do that. I would do that, if I wasn't already working 15 hours a day...

jorisx’s picture

Hmm Yes, Acidfree is really nice (when it works) and G2 is not really an option.
so the waiting is on ... can't wait for 5.0 though :)

Http://www.reloadmedia.com

criznach’s picture

It's a pitty that I've spent 3 hours trying to get it to work! It does mostly work for single images, but mass import isn't working - which is what I needed most. I find Gallery2 extremely cumbersome. Acidfree is appealing because it's lightweight. Hopefully 5.0 will be the same idea.

vhmauery’s picture

jmburnz,

Of course Acidfree is unusable in a community site -- it wasn't written for that. That is something that other users have requested and I have kind of cobbled in. Being the only major contributor to the project (with a couple patches here and there from others), I know what you mean about not having the time. I too work a full-time job and don't get a red cent for the work I do on Acidfree. I wrote it for myself and thought other people might like it. So I shared.

As for the heavy handed branding, it doesn't really matter if you are making a Swedish site. Acidfree doesn't currently have a swedish translation, so you would have to translate it anyway. In the translation, you could just debrand it; as others have done in the past for English installs. All the branding is done within t() calls, so it is trivial to debrand it.

And don't complain about all the problems if you aren't going to contribute. That's just plain rude.

Sorry it didn't work out for you though. I wrote Acidfree for the same reason you switched to Gallery2 -- because nothing else worked for me. But to each his own.

Jeff Burnz’s picture

Didn't mean to offend you, sorry about that, I didn't mean to sound like I was complaining about it.

As stated I really like Acidfree, I think you've done a great job and I would love to have the time to contribute to projects. But I don't, that's just the way it is. My wife would kill me if she heard I was on yet 'another project'...

My main gripe was, and still is, that there is basically no decent user album type module for Drupal.

When I said 'sorry state', i didnt mean the state of your code etc. Just that it would be a real boon if Acidfree was usable in community sites - and that it's sad that it's not. Thats all.

So, yeh, take your break. I do not want to come accross as rude or unappreciative, I am very thankful for the code I have been able to freely access, modify and use. I'm just sorry I don't have the time to put much back right now, which is why I try to help out in the forums when I have a spare half an hour here and there.

It may be trivial for you or other programmers to debrand, but not for non programmers. They would find that challenging. I actually did debrand it, but decided not to use it for other reasons. For a non community site, I may well use it.

criznach’s picture

It's working fine for me now. I got it to import 1300+ photos from my existing filesystem, so that's cool. I had to write some code to do it on cron though, because it couldn't do that without timeouts, etc... Thanks for the cool module - I really dislike G2, but I may still use it for certain things.

criznach’s picture

I've managed to fix the no parent album problem. The form element that specified the parent wasn't being created if you only had the default root album. I'm new to the drupal community, so I'm not familiar with the process to generate a patch, but I'll past the code here... If anyone could point me in the right direction to generate a proper patch, I'd be happy to do so.

In acidfree.module, line 2047, change:

    } else {
      return '';
    }

to...

    } else {
      return Array(
                '#type' => 'hidden',
                '#default_value' => $root->nid,
            );
    }
jorisx’s picture

I Still have problems with the filemanager and acidfree

When rotating images I get these errors:
- The selected file files/active/0/33_small.jpg could not be uploaded, because the destination files/working/0/33_small.jpg is not properly configured.
- image rotate failed for files/working//

My filemanager settings are set:
- public file systempath: files
- public filesystem url: http://www.site.com/new/files/
where "new" is the drupal directory...

I don't get what I'm doing wrong here...

sunfish62’s picture

I do not know whether you still have problem #2, but I was seeing the same thing (i.e., the path to the images included an extra forward slash), and I posted a patch to filemanager that may or may not help with the problem. That patch is found in: http://drupal.org/node/104045

HTH,
David