View Single Post
Old November 23rd, 2005, 01:00 PM   #7 (permalink)
Bill Thebert
Member
 
Join Date: Nov 2001
Posts: 66
This is important to me as well.

I am experimenting with PhotoPost 5.21 for use on a site containing action photos of the local professional hockey team. If I can solve this problem, I will be purchasing my THIRD PhotoPost license.

Top-level "categories" are:

Photos by PLAYER
and
Photos by GAME

There are sub-categories for each player on the roster, and for each game on the schedule.

Each uploaded photo is "filed" under AT LEAST two categories (a player name and a specific game), or more if the image contains multiple players.

It looks pretty silly to see each thumbnail two or three times under "Recent Uploads", or when one clicks on a specific day in the "calendar PAL", etc.

In fact, I can't imagine ANY scenario where I would want PhotoPost to behave the way it does now in this respect. The beauty of databases is at least in part to be able to slice & dice my *views* of the data in different ways -- WITHOUT actually duplicating data. Right?

PhotoPost seems to be creating DUPLICATE image records, and treating them like separate entities, rather than just different views of ONE image.

Comments appended to a photo should (IMHO) appear regardless of which "category" one used to arrive at the photo. As it is now, there are actually two "copies" of a photo stored, and comments appear on only one or the other. Same issue for edits to the description, keywords, etc. -- all must be performed TWO OR MORE TIMES, in order to update all "copies" of an image. This feels like bad design to me.

The advice above is not adequate for me (a PHP novice) to correct this problem and get PhotoPost to behave in a way that make more sense to me.

Can I get more specific edits, please?

Last edited by Bill Thebert; November 23rd, 2005 at 01:07 PM.
Bill Thebert is offline   Reply With Quote