schungx
(Stephen Chung)
January 31, 2020, 6:12am
1
Upgraded to 2.4.0.beta10 [8a82ceb3bc].
After cooking, all images in posts had the wrong src
URL.
For example, before cooking:
https://xxx.blob.core.windows.net/support/original/2X/1/13452effd9ce842874ae17e3145f4e28911d4b41.jpeg
After cooking:
https://support.xxx.com/t/topic/3498
Obviously, the cooked URL for the image src
is wrong. It should be the optimized image under xxx.blob.co.windows.net
; instead it is the topic’s link itself.
I am using Azure-Blob-Storage plugin. Not sure it it has something to do with it.
1 Like
sam
(Sam Saffron)
January 31, 2020, 6:24am
2
Very extremely likely, the plugin is not supported and not maintained and marked as #plugin:broken-plugin at the moment.
discourse-azure-blob-storage
I have created the Azure Blob Storage plugin as part of my Outreachy internship with Discourse. It allows storing uploads into the Azure Blob storage .
Azure account
If you don’t have an Azure account yet, create one for free
In your Microsoft Azure portal, go to Storage account and add a new account - make sure to select Blob storage under Account kind
Go over to your newly created storage account and find Containers in the settings. Add a contain…
4 Likes
schungx
(Stephen Chung)
January 31, 2020, 8:17am
3
Understand that this is free software and all…
But still, under discourse
org maybe it should have some basic maintenance such that it doesn’t break with each change to the storage layer?
Not really complaining… Free and all…
sam
(Sam Saffron)
January 31, 2020, 8:19am
4
Unfortunately we have zero paying enterprise customers using this plugin, if this changes we will certainly make it official and maintain it
2 Likes
schungx
(Stephen Chung)
February 2, 2020, 3:41am
5
Just to report back that this issue has been resolved (not sure if 100%).
EDIT: OK, I added secure: false to store_optimized_image and everything seems to work fine now.
Can be closed.
2 Likes