Wrong images link after cooking - since recent upgrade

AI-generated summary

A user reported that after upgrading to 2.4.0.beta10, images in posts were linked incorrectly post-cooking, pointing to the topic URL instead of the Azure Blob Storage URL. schungx identified the issue as likely related to the Azure-Blob-Storage plugin, which is currently unsupported and marked as broken. sam clarified that the plugin lacks maintenance due to no paying enterprise users, but this could change. schungx later confirmed the issue was resolved, referencing a fix in the plugin’s discussion thread, and the topic was closed.

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.

Very extremely likely, the plugin is not supported and not maintained and marked as #plugin:broken-plugin at the moment.

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…

Unfortunately we have zero paying enterprise customers using this plugin, if this changes we will certainly make it official and maintain it

Just to report back that this issue has been resolved (not sure if 100%).

Can be closed.