Hi @sreenu539, What worked for us were two things:We missed adding core.wcm.components.image.v3 to the embed property of clientlib.baseWe had to rebuild the clientlibs after deploying. Once that was done, the images rendered correctly.Also, make sure your width and height properties are present.
I deferred upgrading this to work on other things but am now returning and the same issue is occurring. Hopefully this will bump the question back up in the list.
Thanks, @lukasz-m for the quick reply.
So, it’s a little more involved than just adding an include, then. It’s more of a case of adding code in a similar way to the core CF component?
Thanks again for the insight.
Thanks, @lukasz-m. I knew this was deprecated, but I was hoping in V3 there was an alternative similar to what @GabrielWalt wrote here, and I just missed it, but I guess that didn't make the cut. Thanks again. Jon
Thanks for your reply, @Vijayalakshmi_S. Reading your answer on the other thread, are you saying extending this wouldn't be advised because it would be like rewriting the whole implementation?
Thanks for the explanation, it is helpful. I did notice that the default max size of 3840 can be increased in the Web Console, so I increased it to 7000 just to test. I'm not sure almost doubling this value is the best way to go about this, but it did resolve the issue.
I don't know why this was marked as accepted. @ChitraMadan's answer below should be the accepted solution. ${item.subtitle} does not work. ${item.properties.subtitle} does work.