You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, the reason to change this is UX. Other, similar external providers give you a warning on their settings page about missing configuration instead.
To Reproduce
Steps to reproduce the behavior:
Run OC on the latest main commit (8852c98 in my case).
Set up the site with any recipe.
Enable the Amazon Media Storage feature.
Go to Configuration -> Media -> Amazon S3 Options
Expected behavior
I should see the configuration screen without errors, but with a notification that warns me about missing configuration.
Actual behavior
Instead, this error is thrown:
ArgumentNullException: Value cannot be null. (Parameter 'buffer')
Parlot.Scanner..ctor(string buffer)
Fluid.Parser.FluidParseContext..ctor(string text)
Fluid.FluidParserExtensions.Parse(FluidParser parser, string template)
OrchardCore.Media.AmazonS3.AwsStorageOptionsConfiguration.ParseBucketName(AwsStorageOptions options, TemplateContext templateContext) in AwsStorageOptionsConfiguration.cs
-
private void ParseBucketName(AwsStorageOptions options, TemplateContext templateContext)
{
// Use Fluid directly as this is transient and cannot invoke _liquidTemplateManager.
try
{
var template = _fluidParser.Parse(options.BucketName);
options.BucketName = template
.Render(templateContext, NullEncoder.Default)
.Replace("\r", string.Empty)
.Replace("\n", string.Empty)
.Trim();
The text was updated successfully, but these errors were encountered:
Describe the bug
As the title says, the reason to change this is UX. Other, similar external providers give you a warning on their settings page about missing configuration instead.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should see the configuration screen without errors, but with a notification that warns me about missing configuration.
Actual behavior
Instead, this error is thrown:
The text was updated successfully, but these errors were encountered: