My process flow is I will add a picture to Resources, usually by creating a subfolder, sometimes nests of subfolders, I drag the picture from my desktop into that folder within Element’ Resource view. I often rename the image. Then I will drag that re-named image into the Image component.
The image previews fine inside the Elements app. It previews fine locally - sometimes (inconsistent).
On my live server-based site the image does not appear. When I inspect the image it has been renamed with an appendage, something along the lines of “@760”. This is obviously not how the file resides on the server itself.
A live example is the first block on this work-in-progress site. Images that I moved pre-1.6.0 seem to still work. New image, the one missing, does not (quickly seen at the first card). https://paladien.com
Thoughts? I had this problem with icons farther down the page, I converted those to .svg to avoid the Image component and that worked. But most pictures I can’t avoid .png or similar.
I will add that these pictures were put into cards from the Essential Templates pack. When I drag the exact same Resources pic into an Image component dragged into the project (not from Essentials), it works.
When I move a new Image component into the Essentials default setup, copy the settings that were in the Essentials pack, the picture now publishes and works fine. When I move that other Essentials pack Image component simply out of the collection of components that made up the template (“Blurry Overlay”), it works.
Am I the only one experiencing this strange “rebuild it and it works” anomaly?
No help with your problem but looked at your website it looks good, from a purely personal point of view only I di laugh at your 4 ordering images as they look like monkeys to me and as its for a fertility site I didnt think this looked a good image. that is my personal observation only and not meant as a criticism.
do you have an example URL where an image is not displayed?
The @760 suffix is added when Elements generates resized versions of an image. In your case, because you’re using the Essentials templates, the Image components in those templates are already configured with specific sizes to suit each layout. That’s why you’re seeing filenames with @760 appended.
Those resized image files are automatically generated by Elements during publishing and uploaded to your server.
Perhaps you’ve already solved the issue, but all of the images seem to be loading just fine here!
This sounds very strange, we’ve not had any other reports of this. I’ve tried to replicate the issue here, but everything is working as expected.
Do you think you could share a project, via Elements Cloud, that has this issue with us?
Hi Ben, yes, I got this to work by dragging new Image components into the project to replace the default Image components pulled in by the Essentials pack. I then copied most Essentials pack settings to preserve all the work that went into the Essentials pack with some tweaks. That worked. I’ll let you know if I encounter any “default pack” errors again.