@StarFleet Carl
So, does that just mean something changed server side, and it'll take a while to migrate through? Or is this an actual error in the coding that Laz or Aroslav needs to fix?
Due to the increase in images being submitted to the site, we needed a better image management system than we had before, so last week I rewrote the image management system to be database-based and migrated image links to this new system. However, just like everything, I introduced some bugs.
If you ever see the image URL to start with: http://reswlpc.com/ instead of https://res.wlpc.com/i/xxxx you should report it. A glitch occurred during migration and few links retained the development server's URL.
Older images were all in the /img directory on the image server. We've moved away from that as it was more labour intensive to put the images on the server (in the author's folder) and populate the html in the files. Now it's easier for us.
The new tag is now < img src="https://res.wlpc.com/i/[image id]" width="image width" height="image height" data-image-file="[original file name]" alt="[could be the file name and could be a description that we enter manually]" >
The images with oldsrc property are the old images migrated to the new system with the old directory-based URL in place just in case something gets screwed up during migration.
The 'osrc' property is a for those who have images hidden by default.