- ABP Framework version: v8.0.0
- UI Type: Angular
- Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
- Tiered (for MVC) or Auth Server Separated (for Angular): yes
- Exception message and full stack trace:
- Steps to reproduce the issue:
error message:
[10:07:35 ERR] defaultValue length must be equal to or lower than 256! (Parameter 'defaultValue')
System.ArgumentException: defaultValue length must be equal to or lower than 256! (Parameter 'defaultValue')
at Volo.Abp.Check.Length(String value, String parameterName, Int32 maxLength, Int32 minLength)
at Volo.Abp.SettingManagement.SettingDefinitionRecord..ctor(Guid id, String name, String displayName, String description, String defaultValue, Boolean isVisibleToClients, String providers, Boolean isInherited, Boolean isEncrypted)
at Volo.Abp.SettingManagement.SettingDefinitionSerializer.SerializeAsync(SettingDefinition setting)
at Volo.Abp.SettingManagement.SettingDefinitionSerializer.SerializeAsync(IEnumerable1 settings) at Volo.Abp.SettingManagement.StaticSettingSaver.SaveAsync() at Volo.Abp.SettingManagement.StaticSettingSaver.SaveAsync() at Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous(IInvocation invocation, IInvocationProceedInfo proceedInfo) at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapter.ProceedAsync() at Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.InterceptAsync(IInvocation invocation, IInvocationProceedInfo proceedInfo, Func`3 proceed)
at Volo.Abp.SettingManagement.AbpSettingManagementDomainModule.<>c__DisplayClass8_0.<
I see that the length of the Default Value field in the newly added table: AbpSettingDefinitions is 256, which should be incorrect. The length of the Default Value field should be the same as the Value field in the AbpSettings table: 2048****
3 Answer(s)
-
0
hi
Thanks. I will confirm this.
-
0
hi
You are right, The
MaxDefaultValueLengthofSettingDefinitionRecordConstsisstaticyou can change it and add new migrations. -
0
Why hasn't this issue been resolved after upgrading to 8.1.1?
