@jess2, this is almost always a dynamic item page where the image isn’t bound to the dataset field. Every item shows the same picture because the element has a fixed image instead of a connection.
Open the dynamic item page in the editor, click the image (or media element), then Connect to CMS and pick the image field from your collection, not a static upload. Make sure the page’s dataset is the same collection your sections come from and set to the current item.
If it’s a repeater or grid on a listing page, each repeater item needs its image connected the same way, inside the repeater, and the dataset filter has to be set per item, otherwise it reuses the first item’s media.
Also check the collection: if two items point at the same media field value, they’ll show the same image even when connected correctly.
@Ecom_swift_LLC thank you for the quick response. I was unable to do your suggestions because now in my ‘work’ pages, there is no media showing up at all, despite it being included within each ‘Item content’ page for each field
@jess2 if nothing shows at all now, the most common cause is a field type mismatch: an Image element only binds to an Image field, and a Gallery element only binds to a Media Gallery field. If your CMS field is a Media Gallery but got connected to a plain Image element (or the other way around), it renders blank instead of erroring.
On the work page, click the media element again, choose Connect to CMS, and check the field actually listed in that dropdown matches your collection’s field type. If the right field doesn’t show up in the list at all, that confirms the mismatch and you’d need to swap the element type (Image vs Gallery) to match.
Also worth checking: did the page’s dataset stay pointed at the same collection while you were troubleshooting? Changing the dataset can silently drop the old element connection even though the panel still looks normal.
Last thing, rule out caching: preview in a fresh incognito tab, since a stale published version can look identical to a broken connection.
@jess2 sorry it’s still not sorting itself out. At this point it’s faster to see the actual setup than keep guessing over text. Could you post a screenshot of the Connect to CMS panel for one of the work page media elements, plus the field type your collection uses for that image (Image field vs Media Gallery field)? That will show exactly where the connection is breaking.
If you would rather skip the back and forth, happy to just fix it directly for you, it is a quick job. You can DM me here or reach out at support@ecomswiftllc.com.
@jess2 found it. Look at your first screenshot: under Connections, “Image source connects to” shows janewadesorel, that is the slug of one specific Work item (row 6, JANE WADE + SOREL), not a field name like Media Gallery or Main Project Image.
That means the dataset on this element is filtered to that one fixed item instead of resolving to whatever item the current dynamic page is for. So every generated page pulls the same JANE WADE + SOREL image, which is exactly “media repeats on each page.”
Fix: open Dataset Settings on that element, remove the manual item filter, and set it back to read from the dynamic page’s current item (the default for a CMS/Item page dataset). Then reconnect the image field to Media Gallery or Main Project Image as needed. Do this for every media element on the template, a filter like this is usually set per element, not shared automatically.
@jess2 Found it. Look at the link icon next to “janewadesorel” in your Connect Image panel, that’s your Work (Item) field, the slug field (same icon as the Work (Item) column in your CMS table). Your image element is bound to that field instead of Media Gallery or Main Project Image, which are the actual media fields on that collection. That’s why it looked blank or repeated, it was never pointed at media at all.
Fix: open the image element, Connect to CMS again, and under “Image source connects to” switch it from Work (Item) to Media Gallery (or Main Project Image, whichever one holds the photo you want shown there). Repeat on each media element across your work pages if more than one is affected.
Still happy to just fix this directly if you’d rather skip more back and forth, support@ecomswiftllc.com.