Is there any way to create or set the parent dropdown used by acidfree to show just a main category or categories? For example currently our intented list of catorgies was set to four options, however whenever an album is created using one of the categories a sub album is created thus making the listed categories huge. Category one currently has 40 sub items listed before category two is shown with its 60 sub items listed (see example below).

If acidfree is unable to just show the main categories from one taxonomy is there a way (an if so how) to show multiple category/taxonomy's to choose from when creating an album?

ie:

What is currently going on:
Add album

Parent:

-Category 1
--sub item 1
--sub item 2
--sub item 3
-Category 2
--sub item 1
--sub item 2
--sub item 3
-Category 3
--sub item 1
--sub item 2
--sub item 3

What we want:
Parent:
-Category 1
-Category 2
-Category 3

Will live with:
Parent:
-Category 1
--sub item 1
--sub item 2

Parent:
-Category 2
--sub item 1
--sub item 2

Parent:
-Caategory 3
--sub item 1
--sub item 2

Comments

rhylos’s picture

Ayone have any good ideas or is this not possible?

xaa’s picture

Indeed limit the dropdown could be very helpfull. Have you finally found a solution ?

rhylos’s picture

No not at all, which is a real bummer. So far the only thing I could come up with was to install the Form Filter module to hide the dropdown from visitors but it's only avail for drupal 5.x

mwheinz’s picture

Status: Active » Closed (won't fix)

5.x is no longer supported, but I'm going to open this as a feature request for 6.x - I like the idea.

mwheinz’s picture

Version: 5.x-1.x-dev » 6.x-1.x-dev
Category: support » feature
Status: Closed (won't fix) » Active

First, 6.x behavior does not (or should not) include all albums, regardless. Instead, it only lists albums you have the right to upload to. For admins, this could mean a very big list....

I'll have to think about this.

rhylos’s picture

Right, the list would get huge without the ability for sub menus. Esp with sites allowing others to post into all albums.

rhylos’s picture

The only option I can come up with without majorly modifying the code is to make the album the default album while using core taxonomy and views to control which albums are viewable in a list/page.

Currently, however; the album is not the default album, acidfree album is. Perhaps either an option to:
-select which album is the default album
-make the default album
-On create new acidfree album, show only top level albums
-Show only the next level album one deep

mwheinz’s picture

Well, we're also moving towards the quick-links model for adding content. If we do that, there's no need to show the album list at all for most "add" operations. You'd only show it in the case where someone directly creates an image or video.

Ringomassa has been working on code to support creating items that could be in an acidfree album, but don't have to be. What if we configured something like this:

1. Make displaying the album selector when adding items a configurable setting.
2. If the item is being added via the quick links, the album defaults to the current album.
3. If the item is being added via "Create Content", the default album is either the user's per-user album or the default album.

This still lacks two things: How do we handle the case where the user doesn't want the item to be in any acidfree album? How do we handle the case where there is no default album, or the user doesn't have "update" access to that album?

ringomassa’s picture

To reduce clutter it would probably be a good thing to make it possible to disable the album selector (taxonomy) when using the quicklinks. This can be done easily by checking for the presence of an acidfree album as parent (code posted previously).
For handling the case where a user doesn't want to add an image to an album, see http://drupal.org/node/1045822. All that is left to do there is altering the update in acidfree.install . I'm not really sure how to do this cleanly.
As we are moving to the quicklinks system i think it would be best to not select any album at all when using "Create Content" as the image content type can be used for many other functions besides an acidfree gallery.

mwheinz’s picture

Assigned: Unassigned » mwheinz
ringomassa’s picture

Attached a patch to handle this. Following code should be added to acidfree.install to change functionality with an update.

function acidfree_update_6002() {
  $ret = array();
  if ($vid = variable_get('acidfree_vocab_id', 0)) {
    db_query ("UPDATE {vocabulary} SET required='0' WHERE vid='$vid'");
  }
  return $ret;
}

If this change is committed, do we also want to do the same for using a quicklink to create an album?

ringomassa’s picture

StatusFileSize
new2.7 KB

And the patch...

ringomassa’s picture

StatusFileSize
new2.83 KB
new2.83 KB

Found an error in the patch. It was not putting the image in any album. So here's a new one.

mwheinz’s picture

StatusFileSize
new3.42 KB

Ringo, your patch works great, but there's already an acidfree_image_form_alter() function. I think it would be better to add your change there, because eventually we will have to make similar changes to the video module as well. (modified patch attached.)

rhylos’s picture

Ref #11

If this change is committed, do we also want to do the same for using a quicklink to create an album?

Yes, I def believe we should do so especially for the sanity of the web admin/dev during the update process.

We'll prob need to move this notion as a new issue for tracking.

mwheinz’s picture

Agreed. Each of the supported types should do this.

mwheinz’s picture

Status: Active » Needs work

I've applied Ringo's patch, plus I've added the code to do the same for albums. We will eventually need to do the same thing for the video module, the change should be similar, but I'm not set up to test that right now.