list.php and photodata.php don't allow editing

[thaths]

Hi,

I have uploaded some images. The thumbnails and microthumbnails are getting created OK. The exhibition and the microthumbnails are showing up OK on the main page. But when I click on the thumbnails on the public site or on 'photo editor' or 'photo browser' it complains that there are no images.

I downloaded and ran the fix in ownerfixer.zip. The problem is not solved. Any ideas?

Thanks.

Thaths

[thaths]

I have 1.5 b4 fix 1 and fix 2 installed. Also have run ownerfixer.php

Thaths

[dunhill]

Im not sure exactly what I did to fix that problem, but I know it was a Path issue under:

SETTINGS
path setup

I played around with the path settings ensuring the my URL path was accessible and ensuring my FTP folder was also accessible using IE

Sorry I can't be of more assistance, I am still learning the product myself.

[Pekka]

thaths wrote:
Hi,

I have uploaded some images. The thumbnails and microthumbnails are getting created OK. The exhibition and the microthumbnails are showing up OK on the main page. But when I click on the thumbnails on the public site or on 'photo editor' or 'photo browser' it complains that there are no images.

I downloaded and ran the fix in ownerfixer.zip. The problem is not solved. Any ideas?

Thanks.

Thaths

I do not know of any other integrity issues than the owner bug.

Mail me a dump of your database to pekka AT photography-on-the DOT net if you have not figured this out by thursday. I'm leaving to Austria in half and hour so there is not much I can do now.

Just one note: if you can enter the photo editor for those photos then you have a setup problem, if photo editor gives errors or does not open then you may have a database integrity problem.

Unless you _can't_ wait for thursday evening:
For _experienced_ users, to manually fix database integrity problems: open database in PhpMyAdmin, view ee_photo table and each photo one by one. Check that each row with an ID number (ee_workflow_id, ee_accessory_id, ee_camera_id...) has that same id in corresponding table, e.g. if photo's ee_owner_id is 74 then check that owner table (also corresponding language tables if there are any) has also a row with ee_owner_id id 7. If they do not match, change PHOTO's owner id to any id that IS in owner table (do not change anything else than ee_photo table..
Make a backup of you database before you do above checks, and mail that original database for me in any case.

[thaths]

pekka wrote:
I do not know of any other integrity issues than the owner bug.


Thanks. Turned out there was an integrity issue. But don't know whether the culprit is me or the software. More info below.

pekka wrote:
For _experienced_ users, to manually fix database integrity problems: open database in PhpMyAdmin, view ee_photo table and each photo one by one. Check that each row with an ID number (ee_workflow_id, ee_accessory_id, ee_camera_id...) has that same id in corresponding table, e.g. if photo's ee_owner_id is 74 then check that owner table (also corresponding language tables if there are any) has also a row with ee_owner_id id 7. If they do not match, change PHOTO's owner id to any id that IS in owner table (do not change anything else than ee_photo table..
Make a backup of you database before you do above checks, and mail that original database for me in any case.


This is the path I took. It turns out that the ee_lens_id of the photos I uploaded into a particular exhibition were referring (in the ee_photo table) to a lens (ID num 6) that I had deleted. The problem could have arisen because I deleted the lens in 'Settings - Lenses' but 'Set - default photo data' was continuing to refer to this deleted lens. When I was uploading photos into this new exhibition, data was being entered into ee_photo that had references to the deleted lens. Maybe when deleting lenses the code should remove a reference to it in default photo data.

Thanks a lot for the help, Pekka. Hope you have fun in Vienna.

Thaths

[Pekka]

thaths wrote:
pekka wrote:
I do not know of any other integrity issues than the owner bug.


Thanks. Turned out there was an integrity issue. But don't know whether the culprit is me or the software. More info below.

pekka wrote:
For _experienced_ users, to manually fix database integrity problems: open database in PhpMyAdmin, view ee_photo table and each photo one by one. Check that each row with an ID number (ee_workflow_id, ee_accessory_id, ee_camera_id...) has that same id in corresponding table, e.g. if photo's ee_owner_id is 74 then check that owner table (also corresponding language tables if there are any) has also a row with ee_owner_id id 7. If they do not match, change PHOTO's owner id to any id that IS in owner table (do not change anything else than ee_photo table..
Make a backup of you database before you do above checks, and mail that original database for me in any case.


This is the path I took. It turns out that the ee_lens_id of the photos I uploaded into a particular exhibition were referring (in the ee_photo table) to a lens (ID num 6) that I had deleted. The problem could have arisen because I deleted the lens in 'Settings - Lenses' but 'Set - default photo data' was continuing to refer to this deleted lens. When I was uploading photos into this new exhibition, data was being entered into ee_photo that had references to the deleted lens. Maybe when deleting lenses the code should remove a reference to it in default photo data.

Thanks a lot for the help, Pekka. Hope you have fun in Vienna.

Thaths


Excellent bug report.
Thanks Thaths!! :)