When auto-generating hierarchical import files from an external stock control system, often the photography and production of JPG files lags well behind the products themselves. The automatically-produced import CSV files nevertheless contain an automatically-generated JPG filename, but such product records are rejected on import because the JPG file cannot be found.
It would be useful for the import program(s) on Actinic to use a DEFAULT.JPG picture in such cases (the DEFAULT.JPG would be user-generated just once, perhaps saying "Image under construction") which would allow the basic website to be fully populated and tested before all the relevant JPGs were available.
In this way the same import file could be re-imported from time to time without any alteration, as more JPGs come on-line; or
(better still) the database retains the actual JPG filename requested but uses DEFAULT.JPG at run-time if the actual file cannot be found at that time.
It would be useful for the import program(s) on Actinic to use a DEFAULT.JPG picture in such cases (the DEFAULT.JPG would be user-generated just once, perhaps saying "Image under construction") which would allow the basic website to be fully populated and tested before all the relevant JPGs were available.
In this way the same import file could be re-imported from time to time without any alteration, as more JPGs come on-line; or
(better still) the database retains the actual JPG filename requested but uses DEFAULT.JPG at run-time if the actual file cannot be found at that time.
Comment