Activities of "scott7106"
Yes, the backend is configured as described and the external logins page was there until we upgraded the application to v8.3.4 and the front-end (angular) to v9.0.4 based on the recommendation in this ticket. Now the external logins configuration page has disappeared.
@liangshiwei - Thank you for providing this. This gives us what we need. If I may make a couple of suggestions.
- Allow for users to pick the version they want from ABP Studio, it switches the Studio version and switches ABP Suite to match the template version of Studio.
- Provide a setting which allows users to skip/disable checking for new versions on startup
This is not an answer to my question. You cannot generate a new solution from newer versions of ABP Suite. How do I install a specific version of ABP Studio?
For business reasons (not technical), we cannot upgrade to .NET 9. We must continue building and developing our solutions on .NET 8. Therefore, we need to continue using the 8.3.4 version for some time.
As of now, we cannot use ABP Studio. I can install the 0.9.8 version of the CLI from the command line and use that to generate new solution templates. However, if I launch ABP Studio, it updates the version of the CLI. Your design choices for version management assume everyone is able and willing to upgrade to .NET 9. We cannot do that which makes the tool useless to us.
Given the documentation about version mappings for new application templates, https://abp.io/docs/latest/studio/version-mapping
How can we install a specific version (v0.9.8) of the ABP Studio application? We want to generate our templates based on the 8.3.4 template as we are not able to upgrade to .NET 9 at the current time.
I have the same problem. In addition, trying to login to ABP Studio gives the following message.
- ABP Framework version: v8.1.3
- UI Type: Angular
- Database System: EF Core (SQL Server)
- Tiered (for MVC) or Auth Server Separated (for Angular): no
- Exception message and full stack trace:
- Steps to reproduce the issue:
This issue is new this morning.
I cannot login this morning from the console.
abp login <username> -p <password> is failing. Adding --organization does not fix the problem.
In addition, I cannot access my account profile. I get an Internal error 500
Thank you!
We are using Angular and have not edited the UI. I sent you an invite to the GitHub repo.
- ABP Framework version: v8.2.1
- UI Type: Angular
- Database System: EF Core (SQL Server)
- Tiered (for MVC) or Auth Server Separated (for Angular): no
- Exception message and full stack trace:
- Steps to reproduce the issue:
We have extended the SaasTenants object. After upgrading to 8.1.4, we noticed that the create/edit screen for tenants does not show the labels. The Index page correctly shows the headers for the additional columns so the localized string is working there. This appears to be a UI bug or something we need to add which wasn't required in earlier versions. We noticed this with 8.1.4, but cannot confirm whether that is where it was introduced.
ObjectExtensionManager.Instance.Modules()
.ConfigureSaas(saas =>
{
saas.ConfigureTenant(tenant =>
{
tenant.AddOrUpdateProperty<string>(
"ClientCode",
property =>
{
property.Attributes.Add(new RequiredAttribute());
property.Attributes.Add(new StringLengthAttribute(MultiTenancyConsts.ClientCodeMaxLength));
property.DisplayName = LocalizableString.Create<ZiplineResource>("::ClientCode");
property.UI.OnTable.IsVisible = false;
});
tenant.AddOrUpdateProperty<string>(
"EnvironmentCode",
property =>
{
property.Attributes.Add(new RequiredAttribute());
property.Attributes.Add(new StringLengthAttribute(MultiTenancyConsts.EnvironmentCodeMaxLength));
property.DisplayName = LocalizableString.Create<ZiplineResource>("::EnvironmentCode");
property.UI.OnTable.IsVisible = false;
});
tenant.AddOrUpdateProperty<string>(
"TenantCode",
property =>
{
property.Attributes.Add(new StringLengthAttribute(MultiTenancyConsts.TenantCodeMaxLength));
property.DisplayName = LocalizableString.Create<ZiplineResource>("::TenantCode");
property.UI.OnCreateForm.IsVisible = false;
property.UI.OnEditForm.IsVisible = false;
});
tenant.AddOrUpdateProperty<EnvironmentType>(
"EnvironmentType",
property =>
{
property.DefaultValue = EnvironmentType.Development;
property.Attributes.Add(new RequiredAttribute());
property.DisplayName = LocalizableString.Create<ZiplineResource>("::EnvironmentType");
});
tenant.AddOrUpdateProperty<StructureType>(
"StructureType",
property =>
{
property.DefaultValue = StructureType.Warehouse;
property.Attributes.Add(new RequiredAttribute());
property.DisplayName = LocalizableString.Create<ZiplineResource>("::StructureType");
});
tenant.AddOrUpdateProperty<string>(
"Description",
property =>
{
property.Attributes.Add(new StringLengthAttribute(MultiTenancyConsts.DescriptionMaxLength));
property.UI.OnTable.IsVisible = false;
property.DisplayName = LocalizableString.Create<ZiplineResource>("::Description");
});
});
});
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="3.2.1" />
Ignoring it may be an option, but it spams the log file with these messages every 5-10 seconds. This issue showed up after upgrading from 8.1.4 to 8.2.1. In the meantime, since it does not appear to be affecting the user experience, I will configure the logs to filter these messages.
