Photos Cannot Be Displayed or Saved
On this page
7.6 Photos Cannot Be Displayed or Saved
Determine database/folder/interface source and separate main-photo, card-image, and temporary-edit states.
7.6.1 Source and Ownership
Locate by unique number and compare row/photo/card, not name alone. Card-only blanks suggest element binding/crop/display rules; a missing photo panel may mean no identifiable main portrait. Do not assume the first binary image is the face in a design with signatures and other images. Compare all-versus-few people and other stations to isolate source availability. For a wrong person, stop that record's output/export/encoding and correct ownership with retained evidence, not merely a screen replacement.
7.6.2 Database Photos
Administrators should verify nonempty binary data, matching relation, and actual SQL output. A photo table's presence is insufficient. Preserve damaged originals and test a readable image on a copy before formally replacing one record, not overwriting the full table. Inspect write permission, target, type, and constraints. Reread/reopen the same person to exclude memory-only success.
7.6.3 Folder and Interface Photos
Check root, naming field, extension, subdirectories, and running identity. 00123 does not inherently match 123.jpg; blank keys, duplicate names/extensions can misassociate. Readable shares do not prove write/overwrite permissions; inspect readonly/locks. Interface sources depend on service/authentication/network and often do not expose local editing controls. Their absence alone is not a defect. Do not send tokens in tickets.
Figure 7.6-1. Use fictitious 00123 to compare database/folder checks and correct naming; identify external-service responsibility. Hide paths/authentication and use no real portraits.
7.6.4 Capture, Crop, and Transparency
For no camera image, verify connection, desktop-app privacy, selected device, and exclusive access; test Windows/vendor preview first. Do not assume every camera matches delivery components. Check original dimensions, crop ratio, and output pixels for clipped/small faces. Zoom cannot restore a blurred original; obtain a clear source. PNG supports alpha; JPEG does not. Inspect edges against actual card backgrounds and separately confirm whether official photo storage was updated.
7.6.5 Saving and Batch Acceptance
Preview adjustments may be temporary; use the proper maintenance save and reread. Folder batch output does not automatically update personnel. Check success/failure/naming/location and approved import/replacement, sampling first/middle/last and same-name people. Accept only correct identity, durable reread, known original/output, and correct card proportions. Keep affected automatic tasks paused for unresolved wrong/missing images.
Figure 7.6-2. Show a single dummy number through temporary crop, formal save, and reread, plus redacted batch-output location. State that batch results still require approved integration.