Intermittent problem rendering template feed "&mvt:record:image;" value

[PCINET - Andreas]

That would be the cleanest way and no need to test. You could just assign the legacy images in a batch job to the main image and be done. Of course adjust the feed afterwards :)

[William Davis]

yeah, you can't do this for all but would need to add a conditional and test if a part is missing and add only in this case.

Would it be best to address products with Legacy Images by replacing them with Image Machine images then manually add missing portion of URL path to feed? If so, how would I go about doing that?

[PCINET - Andreas]

yeah, you can't do this for all but would need to add a conditional and test if a part is missing and add only in this case.

[William Davis]

correct, just add the missing part manually as a prefix before the token.

Andreas, if I do as you suggest wouldn't fixing one issue brake the other?

[PCINET - Andreas]

correct, just add the missing part manually as a prefix before the token.

[William Davis]

Intermittent problem rendering template feed "&mvt:record:image;" value in "image_link" field, most render complete URL path correctly. However, over 3k URLs path are partially rendered.

Example: "https://www.store.com/mm5/" , consistently missing the remaining "graphics/00000001/[Main-ImageName]_{n}_{width}x{height}.jpg" portion.

Note: Both set of "&mvt:record:image;" values (complete and partial URL path) have been confirmed to be properly assigned to "Main" image type. However, I have noticed in admin that those with partial URL path issues, the image name contains the Image Machine dynamic suffix "..._{n}_{width}x{height}." and those with complete URL path ("Legacy Images" from MM4.24c) do not have said suffix.

Thinking out loud, it appears the template feed "&mvt:record:image;" token only renders complete URL path for "Legacy Images" and not Image Machine images. Am I on the right track or am I missing something and what would be the solution?