Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

storage has not been created when Azure Media Storage or Azure Media ImageSharp Image Cache was enabled #17597

Open
canadacubachina opened this issue Mar 10, 2025 · 3 comments

Comments

@canadacubachina
Copy link
Contributor

Describe the bug

Azure Media ImageSharp Image Cache or Azure Media Storage was enabled. my storage on configuration has not been created

Orchard Core version

2.1.4

To Reproduce

  1. set up Env. Var. of azure app service as: OrchardCore__OrchardCore_Media_Azure__CreateContainer true , OrchardCore__OrchardCore_Media_Azure_ImageSharp_Cache__CreateContainer true
  2. Go to 'admin portal.'
  3. Click on 'Enable of Azure Media ImageSharp Image Cache'
  4. the storage has not been created

Expected behavior

If the CreateContainer option is set to true an activating event will check on Startup for a valid connection string, and test that the container exists, creating if it does not. Set CreateContainer to false to disable this check if your container already exists.

Logs and screenshots

@canadacubachina
Copy link
Contributor Author

it seems because of {{ ShellSettings.Name }}_imagecache for OrchardCore__OrchardCore_Media_Azure_ImageSharp_Cache__ContainerName.
if I only use imagecache , it worked

@SzymonSel
Copy link
Member

Have you provided the connection string? I had an issue, when I activated the Azure Media Storage module without setting the connection string in the first place - which bricked the whole system. To fix it, I needed to manually disable the module in the database.

@infofromca
Copy link
Contributor

infofromca commented Mar 11, 2025

Have you provided the connection string? I had an issue, when I activated the Azure Media Storage module without setting the connection string in the first place - which bricked the whole system. To fix it, I needed to manually disable the module in the database.

Yes, because I got successfully with imagecache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants