|
18 | Bug Report | Backend / Core | Stop using predictable filenames | Closed | 2006-06-06 |
Task Description
For things like photo imports, exports, and whatnot, we use predictable sequences in our filenames. These should be properly randomized. |
|
113 | Bug Report | Backend / Core | camera edit doesn't respect owner | Closed | 2006-11-25 |
Task Description
someone can edit a camera they don't own. |
|
183 | Feature Request | Backend / Core | Rip out "shopping" and everything associated with it. | Closed | 2007-03-21 |
Task Description
* There's a lot of it. * I don't fully understand how it works. * It's complicated and has internal dependencies all over the place. * Does anyone really use it? * The "client" distinction is flawed. I want PO to be an organizational tool first, and any e-commerce bits need to be carefully thought out. |
|
193 | Bug Report | Backend / Core | figure out why e-mail templates are broken. | Closed | 2007-04-18 |
Task Description
They're not getting evaluated properly. |
|
334 | Bug Report | Backend / Core | cannot delete users that have folder/album thumbnails s ... | Closed | 2008-03-26 |
Task Description
via the admin.user.del pages. the problem is due to a dependency. |
|
62 | Feature Request | Backend / Core | Rewrite installer to use *anything* other than tcsh | Closed | 2006-09-26 |
Task Description
TCSH is a gawd-awful pile of crap, and the install script reflects that. Code duplicated all over the place... yuck. No functions! Yuck! (And no, parameterized aliases don't really count..) These days one is also more likely to have perl than tcsh installed.. |
|
90 | Bug Report | Backend / Core | Times are lost when editing an image's details. | Closed | 2006-09-07 |
Task Description
The 'Exposure date' thing strips the time off of the image when you click submit. This is bad.. |
|
111 | Feature Request | Backend / Core | Use PHP's builtin session support | Closed | 2006-12-20 |
Task Description
The builtin session stuff, especially where shared logins are enabled, is rather kludgy. I'd much rather use PHP's builtin session support, and eliminate PO's cobbled-together one-session-per-user nonsense. |
|
197 | Feature Request | Backend / Core | Add an option to ignore the "exif title" tag. | Closed | 2007-04-18 |
Task Description
Some cameras store the 'ownership string' in the 'title' exif field. This means that every image ends up getting the same comment. It's a pain to go back and fix. Add an option to the camera listings to explicitly ignore this field. |
|
322 | Bug Report | Backend / Core | 'transfer metadata' isn't working for RAW images. | Closed | 2008-02-17 |
Task Description
This is because we try to transfer the metadata from the 'hires' image, but that's the output of the raw decoder rather than the original image. So, fix this. |
|
440 | Bug Report | Backend / Core | Possible to set an album/folder's parent to itself. | New | 2010-10-05 |
Task Description
We need to enforce that rule to prevent the DB from going nuts. Either via SQL: 1) Trigger to test that parent != id 2) the (folders|albums)_and_sub(folders|albums) function needs to abort if it sees it or in PHP: 3) Test the values in the php pages [[ (album|folder).(add|edit).2.php ]] and kick back an error. I don't think there's another way to mangle things. This can result in a DoS. |
|
4 | Feature Request | Backend / Core | Hierarchical bulk Input | Closed | 2006-06-08 |
Task Description
PO currently requires a flat file layout when it does a bulk import. It would be very nice if the import could recurse through subdirectories and automtically add folders as needed, thus preserving the original hierarchy. |
|
5 | Feature Request | Backend / Core | Bulk update improvements | Closed | 2006-07-15 |
Task Description
The bulk update functionality is nice, but unfortunately it has a fundamental flaw. Each field should have a corresponding checkbox that tells the backend to update or ignore that field. This way we can ensure that only the fields we want are updated. Also, allow it to work against arbitrary lists, and support albums as first-class citizens. |
|
6 | Feature Request | Backend / Core | Specify/store RAW image parameters | New | 2008-02-17 |
Task Description
Currently the RAW settings are shared across all images. It would be nice if each image would contain with it the settings used to process the image. The problem is that the decoder often has defaults which change over time, and re-generating the same image can result in differences. |
|
7 | Feature Request | Backend / Core | Generate a hi-res JPEG from RAW images | Closed | 2008-10-27 |
Task Description
We generate "thumbnail" and "preview" images for all images we upload, and we can download the original, full-res version. However, with RAW images, this is suboptimal, as we'd then need to process the RAW image into a usable JPEG. Add the ability to generate a full-res JPEG from RAW images, and make the RAW download itself optional. Perhaps we could implement this using the whole "image version" thing? |
|
8 | Feature Request | Backend / Core | Better permission hierarchy | Assigned | 2008-09-18 |
Task Description
Right now there are three permissions -- public, private, and "protected", which equates to "public only to all of my clients" This is pretty lousy; I can certianly envision scenarios where you'd want a client to only see stuff that's specific to that client. To do this now, you have to create separate accounts and mark clients for those specific accounts. I'd like to see a more generic hierarchical user/group model. Only the photo owner can make changes to their images, but the permission model would break down as follows: Permissions would be granted on a per-group basis, and individual users can be members of various groups. "Guest" access would just be another group, and would default to assigned. A permission is inherited; so if "guest" is granted access to the top-level folder, they would be allowed to see everything below it unless a more restrictive permission was specified. This is sort of similar to unix permissions with the "sticky bit" turned on. This gets a little tricky when talking about folders vs albums, as a user may not be allowed to browse the folder, but the image could be included in a public album. When viewing the image from the folder perspective, it would be disallowed, but from the album perspective, it would be allowed. EDIT: see http://po.shaftnet.org/new_permission_model |
|
10 | Feature Request | Backend / Core | Add generic key=value preference system | Closed | 2007-02-09 |
Task Description
There are a lot of places where we could use the ability to arbitrarily store data points; things like custom fields for images, raw decode parameters (they're always changing!), or per-album/folder sort order (for things like subalbums, not just images!) In any case, I'd definately like to see things like the image processing options moved out of their rigid, fixed database table. |
|
11 | Feature Request | Backend / Core | Clean up database conventions | Assigned | 2008-10-03 |
Task Description
Most database results are being indexed by position in a fixed array, rather than by column name. This may be slightly faster, but is hell to program around, especially when there can be twenty fields being returned. * Convert all fetch_row() calls to fetch_assoc() Secondly, using prepared statements would make the code a lot cleaner and eliminate the need to escape strings being passed in to the database. Unfortunately, this may require PHP 5.1 to pull off, depending on the maturity of the postgres bindings for earlier versions. * Use prepared statements and SQL variables instead of inlined data. |
|
13 | Feature Request | Backend / Core | Rework spooling | Closed | 2006-08-22 |
Task Description
Right now exports and printing work via a dedicated "spool" that is nearly impossible to manage sanely. I'd like to see the spool go away, in favor of allowing exports/printing to work against an album in its entirety. We can create a "special album" (like the Trash folder, for example) to make the UI work a bit simpler, but instead of "spooling" an item, we'll just link it into that special spool album. This also lets us manage the spool directly. |
|
15 | Feature Request | Backend / Core | Offline export support | Closed | 2007-11-26 |
Task Description
It would be nice to be able to generate a static gallery for a given album/folder. It would make archival much easier too. |
|
16 | Feature Request | Backend / Core | Add a 'backed up' flag to the storage volumes | Closed | 2007-11-26 |
Task Description
This way it's easy to see at a glance what still needs to be backed up. (note -- do we want to make this per-image, perhaps?) |
|
17 | Feature Request | Backend / Core | Extend ordering mechanism to automatically ordering pri ... | Closed | 2007-03-27 |
Task Description
eg via shutterfly or one of the many online print services. |
|
19 | Feature Request | Backend / Core | Bulk import from filesystem | Closed | 2006-06-15 |
Task Description
This one is a doozey, due to the security implications in a multiuser/shared environment. We may want to make the 'filesystem bulk import' path per-user or something like that, but it has to be readable by the webserver user. |
|
20 | Bug Report | Backend / Core | Support newer DCRAW releases | Closed | 2006-05-13 |
Task Description
Newer versions of DCRAW use different command-line arguments. |
|
21 | Feature Request | Backend / Core | Import EXIF data from TIFF/RAW images | Closed | 2006-05-13 |
Task Description
Exifer can do it, with some elbow grease. Please backport. |
|
22 | Feature Request | Backend / Core | Support the UFRAW decoder | Closed | 2006-07-13 | |
|
23 | Feature Request | Backend / Core | Support exiftool | Closed | 2006-06-30 | |
|
24 | Bug Report | Backend / Core | Clean up internal checkbox handling | Closed | 2006-07-13 | |
|
26 | Feature Request | Backend / Core | site-wide page title should be customizable | Closed | 2006-05-16 | |
|
28 | Feature Request | Backend / Core | Enhance tooltips a bit | Closed | 2006-06-17 | |
|
29 | Feature Request | Backend / Core | Additional sort orders | Closed | 2006-05-13 | |
|
31 | Feature Request | Backend / Core | Add per-folder/album licensing text | Closed | 2007-11-03 | |
|
32 | Feature Request | Backend / Core | Add 'last modified' or 'last added to' to folder lists, ... | Closed | 2007-03-04 | |
|
33 | Feature Request | Backend / Core | re-parse EXIF tags after importing | Closed | 2007-08-17 | |
|
34 | Feature Request | Backend / Core | OFfline archival capabilities | Closed | 2008-03-02 | |
|
35 | Feature Request | Backend / Core | Reduce database roundtrips. | Closed | 2007-02-15 | |
|
36 | Feature Request | Backend / Core | Add thumbnails to prev/next links. | Closed | 2006-11-24 | |
|
37 | Feature Request | Backend / Core | AJAX! AJAX! AJAX! | Closed | 2007-04-19 | |
|
38 | Feature Request | Backend / Core | better theme/templating support. | Closed | 2007-06-17 | |
|
39 | Feature Request | Backend / Core | Allow XML file to specify defaults for import | Closed | 2013-08-21 | |
|
40 | Feature Request | Backend / Core | EXIF import improvements | Closed | 2006-06-15 | |
|
41 | Feature Request | Backend / Core | Find an alternative for exifer (EXIF library) | Closed | 2006-07-13 | |
|
42 | Feature Request | Backend / Core | Add a bulk upload client. | Closed | 2011-11-23 | |
|
43 | | Backend / Core | Reconcile dev tree changes with PO latest code. | Closed | 2006-06-15 | |
|
44 | Bug Report | Backend / Core | temp files are left lying around after imports | Closed | 2006-05-21 | |
|
45 | Feature Request | Backend / Core | Add support for changing RAW white balance. | Closed | 2013-12-23 | |
|
48 | Bug Report | Backend / Core | Advanced search is broken | Closed | 2006-05-11 | |
|
49 | Bug Report | Backend / Core | Search results 'list view' sends user to folder screen | Closed | 2006-12-28 | |
|
50 | Bug Report | Backend / Core | optimize searching some more | Closed | 2006-06-15 | |
|
51 | Feature Request | Backend / Core | Make Hosting Easier | Closed | 2006-08-17 | |