Hello and thank you for contacting the Toolset support.
To better assist you with this issue, I think, I'll need to check how the view is built and see on the frontend these issues. That way, I can debug it a bit and hopefully find out what's going on. If you would agree, your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **
Thank you for the credentials.
I disabled all plugins and switched to the 2020 theme and the issue persists. Randomly, we can get the image, then we can't any longer.
I thought that the issue came probably from the solution of wrapping the container block inside HTML blocks to have the link, or from reusable blocks, so I tested with a new page and a new view, and the issue was reproduced there again.
To further investigate this issue, I would like to take a copy of your website and debug it locally, would you agree if I install the Duplicator plugin and take a copy?
Hi Jamal,
Yes sure, please proceed.
Thank you. I just want to let you know, that I am still working on this issue. I was not able to find the origin of this issue, so, I am approaching our 2nd Tier for assistance. I'll get back to you as soon as we find something.
Our 2nd Tier was not able to reproduce this issue on his environment, so he can't really debug, why this is happening.
He thinks that the issue might be because of the character encoding on your server. And he suggested images that do not have special characters on the name such as (é and â).
Please try to change the images on the current posts(especially those returned by the view) to use images without special characters on the name and let us know if it will fix the issue for you.
The 2nd Tier has escalated this to our developers and they will work on it to find out the real origin of the issue.
Please, let us know what you will get.
Hi Jamal,
I did replace the image name special characters but the issue persists, I am afraid.
I'll wait for developers reply.
Thank you for your feedback. I am escalating this to our 2nd Tier and I'll get back to you as soon as possible.
Hello and our apologies for the late reply. The developers have closed the internal ticket about this issue because they were not able to reproduce it with the provided copy of the website.
I assume that it was not reproducible because the issue was somehow fixed in the updates that followed. So, I would like to get back to you and check if you have been able to update Toolset plugins. And if you still encounter this issue with these versions.
Hi Jamal,
I custom coded the container 4 month ago, not very convenient but it did the job.
I saw the update with this new functionality, that's good news.
I didn't change anything yet, as I have a working page already but next time for sure.
I also had to crash the staging site I provided you with as I had to move on with new tests on a new one, maybe that's why they couldn't reproduce it 🙂