Dear all, we noticed a problem when trying to load images in a few old posts:
Sometimes, despite the image URLs being valid, they aren't loaded in posts appearing with the "corrupted" image Icon like here.
As you know, the PixInsight forum is on a secure server, and the pages are accessed via the HTTPS protocol. Still, in these old posts, the images are on a different server and accessed via a standard HTTP connection.
This is why the browser considers them unsafe and blocks them.
If you want to check if your browser has this issue try this link and check if you can see the images in the first post.
The solution to this problem is very simple and consists in allowing unsecure contents ONLY FOR PixInsight Forum
This is the Chrome workflow to solve the problem, but it is very similar with other browsers
Click on the padlock icon near the site URL and select Site Settings
In the setting list look for unsecure content, and change from the Block (default) to Allow.
This setting will be valid only for pixinsight.com website, so you will not compromise your browser security settings.
The images will be correctly loaded after this change, but you browser, in these pages, will correctly show the Not Secure Icon.
Clear Skyes
Edoardo
Sometimes, despite the image URLs being valid, they aren't loaded in posts appearing with the "corrupted" image Icon like here.
As you know, the PixInsight forum is on a secure server, and the pages are accessed via the HTTPS protocol. Still, in these old posts, the images are on a different server and accessed via a standard HTTP connection.
This is why the browser considers them unsafe and blocks them.
If you want to check if your browser has this issue try this link and check if you can see the images in the first post.
New versions of StarAlignment and ImageIntegration
Hi all, Yesterday I released updates for the ImageRegistration and ImageIntegration modules (new versions 1.0.4.527 and 1.12.0.351, respectively). These updates provide important performance improvements for the StarAlignment and ImageIntegration tools by way of high-level parallelization...
pixinsight.com
The solution to this problem is very simple and consists in allowing unsecure contents ONLY FOR PixInsight Forum
This is the Chrome workflow to solve the problem, but it is very similar with other browsers
Click on the padlock icon near the site URL and select Site Settings
In the setting list look for unsecure content, and change from the Block (default) to Allow.
This setting will be valid only for pixinsight.com website, so you will not compromise your browser security settings.
The images will be correctly loaded after this change, but you browser, in these pages, will correctly show the Not Secure Icon.
Clear Skyes
Edoardo