mark007 Posted October 21, 2017 Posted October 21, 2017 I changed to HTTPS and used this feature in ACP: Serve images from local server? When using https and members post remote links to insecure images then this can cause the page to report as insecure in your browser. This setting, when enabled, will cause the image to be retrieved and then served from the local web server over https instead. But there is a big problem. Many smilies are not displayed after that and images, too. I don't know where the problem is. In source code you can find the difference: AFTER <img alt=":78_robot:" data-emoticon="" height="20" src="https://www.polar-chat.de/hunde/applications/core/interface/imageproxy/imageproxy.php?img=%3CfileStore.core_Emoticons%3E/emoticons/78_robot.png&key=(...)" srcset="https://www.polar-chat.de/hunde/applications/core/interface/imageproxy/imageproxy.php?img=%3CfileStore.core_Emoticons%3E/emoticons/78_robot@2x.png&key=(...) 2x" title=":78_robot:" width="20"> BEFORE <img alt=":78_robot:" data-emoticon="" height="20" src="https://www.polar-chat.de/hunde/uploads/emoticons/78_robot.png" srcset="" title=":78_robot:" width="20" /> PS.: (...) that's me, to shorten the key here
opentype Posted October 21, 2017 Posted October 21, 2017 The URLs are apparently not generated correctly. That “fileStore” part should point to an actual location and not output directly. You probably need to open a support ticket with IPS to have that checked out properly. Feel free to tell us the result. I planning to use that feature on my biggest site soon as well.
Optic14 Posted October 22, 2017 Posted October 22, 2017 I'm getting this exact issue too... I enabled the feature and ran the rebuild for it to update all the posts and status updates overnight. I've now disabled the feature and am running the rebuild and can confirm my inline attachments are working again. Strangely this behaviour has affected attachment images. The images are still attached to their posts thankfully but inline images have been replaced with a hyperlink (as per @mark007above)
Stuart Silvester Posted October 22, 2017 Posted October 22, 2017 21 hours ago, mark007 said: I changed to HTTPS and used this feature in ACP: Serve images from local server? When using https and members post remote links to insecure images then this can cause the page to report as insecure in your browser. This setting, when enabled, will cause the image to be retrieved and then served from the local web server over https instead. But there is a big problem. Many smilies are not displayed after that and images, too. I don't know where the problem is. In source code you can find the difference: AFTER <img alt=":78_robot:" data-emoticon="" height="20" src="https://www.polar-chat.de/hunde/applications/core/interface/imageproxy/imageproxy.php?img=%3CfileStore.core_Emoticons%3E/emoticons/78_robot.png&key=(...)" srcset="https://www.polar-chat.de/hunde/applications/core/interface/imageproxy/imageproxy.php?img=%3CfileStore.core_Emoticons%3E/emoticons/78_robot@2x.png&key=(...) 2x" title=":78_robot:" width="20"> BEFORE <img alt=":78_robot:" data-emoticon="" height="20" src="https://www.polar-chat.de/hunde/uploads/emoticons/78_robot.png" srcset="" title=":78_robot:" width="20" /> PS.: (...) that's me, to shorten the key here 1 minute ago, Optic14 said: I'm getting this exact issue too... I enabled the feature and ran the rebuild for it to update all the posts and status updates overnight. I've now disabled the feature and am running the rebuild and can confirm my inline attachments are working again. Strangely this behaviour has affected attachment images. The images are still attached to their posts thankfully but inline images have been replaced with a hyperlink (as per @mark007above) Please open a support ticket in the client area, I would like to take a look at this and see what's going on.
Optic14 Posted October 22, 2017 Posted October 22, 2017 Thanks @Stuart Silvester I have created ticket #992349
mark007 Posted October 22, 2017 Author Posted October 22, 2017 32 minutes ago, Stuart Silvester said: Please open a support ticket in the client area, I would like to take a look at this and see what's going on. I already opened a ticket yesterday: #992318
mark007 Posted October 24, 2017 Author Posted October 24, 2017 Tier II = really good support has fixed it
mark007 Posted October 24, 2017 Author Posted October 24, 2017 45 minutes ago, opentype said: So, what was the problem? I don't know, but @Stuart Silvester knows.
Stuart Silvester Posted October 24, 2017 Posted October 24, 2017 1 hour ago, opentype said: So, what was the problem? 1 hour ago, mark007 said: I don't know, but @Stuart Silvester knows. It was a minor bug that has been fixed
iNoxvil Posted October 27, 2017 Posted October 27, 2017 On 10/24/2017 at 10:32 PM, Stuart Silvester said: It was a minor bug that has been fixed Hi Stuart, i have the same issue and i just open a ticket #992723 Can you please take a look at it? Thx!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.