Posted by rhylos on February 4, 2011 at 6:27am
4 followers
Jump to:
| Project: | Acidfree Albums |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Recommend a section is created in the acidfree admin interface to customize the text "This album is empty". This option will allow the admin to enter their own text in this field such as, "Use the mass import link above to add your own images".
Comments
#1
As a work around, both of the places this phrase is used is in theme functions:
function theme_album_grid_view($tid, $nodes, $teasers = false, $links = true) {}
So you could write your own theme function and do something like
function mytheme_album_grid_view($tid, $nodes, $teasers, $links) {$output = theme_album_grid_view($tid, $nodes, $teasers, $links);
$output = str_replace("This album is empty", "Use the mass import link above to add your own images", $output);
return $output;
}
#2
Replace the hard-coded text for certain acidfree actions with strings that can be customized via the user interface.
This should include:
* The default body for new albums.
* The message displayed when an album is empty.
* The name of the acidfree vocabulary.
What else?
#3
Mass import tab text
Mass update tab text
#4
Add Acidfree items:
#5
Okay. The current list is:
* The default body for new albums.
* The message displayed when an album is empty.
* The name of the acidfree vocabulary.
* Mass import text
* Mass update text
* Add acidfree items
#6
#7
Looks good and tested well. Love the AF admin fields area. Can we add the following two menu items to the list? These are found if the Add Acidfree Items menu is enabled in the album:
Add an image
Add an album
#8
Sure, shouldn't be hard.
#9
Heh. Turns out it's slightly harder than I thought. Each media type (album, image, video) declares its own "addme" string.
I'm going to try and figure out the best way to handle this using the existing type structure.
#10
Proposed structure:
1. Each media type hard-codes the default string.
2. Each media type is responsible for storing the replacement string as a drupal variable.
3. Each media type will provide an accessor function for setting the replacement string.
4. The main admin/settings page will iterate through the types and provide fields for updating each string.
#11
Done.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.