Activities of "liangshiwei"

See: https://docs.abp.io/en/abp/latest/Modules/Cms-Kit/Index#how-to-install

By default, Cms-Kit is disabled by GlobalFeature. Because of that the initial migration will be empty. So you can skip the migration by adding --skip-db-migrations to command when installing if you are using Entity Framework Core. After enabling Cms-Kit global feture, please add new migration.

Before adding migrations, you need to enable the cms feature.

npm WARN config global --global, --local are deprecated. Use --location=global instead

This line of warning is causing the problem. you can see: https://github.com/npm/cli/issues/4980

Sorry that, I mean your application logs

Hi,

You can configure the redirect allowed URLs See: https://github.com/abpframework/abp/blob/dev/templates/app/aspnet-core/src/MyCompanyName.MyProjectName.HttpApi.HostWithIds/appsettings.json#L6

And: https://github.com/abpframework/abp/blob/dev/templates/app/aspnet-core/src/MyCompanyName.MyProjectName.HttpApi.HostWithIds/MyProjectNameHttpApiHostModule.cs#L88

Hi,

We had the problem before https://support.abp.io/QA/Questions/3092/Error-when-trying-to-use-abp-generateproxy--t-ng--m-identity But we fixed it

Maybe ABP CLI can not work on macOS as well, we will check it.

Hi,

maybe the empy migration error will be fixed in a future version

Can you share the full steps to reproduce? if there has a problem we should fix it.

Hi,

Try: abp generate-proxy -t ng -m app -u <Your back-end url.>

Hi,

I'm sorry that we don't have such example.

You can use the IFeatureDefinitionManager to get all feature definitions and use IFeatureManager to set feature.

Hi,

Please

• Steps to reproduce the issue:"

Neither of these two commands solved the problem, though the yarn command did download some packages. The abp install-libs command resulted in a warning that I did not have NPM Installed though I have confirmed that I do have it installed by running npm -v right after the warning. Unfortunately I did not think about This at first and so I uninstalled and reinstalled Node and played with my path for a couple of hours thinking that this was part of the problem.

What is the result when you run npm -v

Upon encountering the certificate error, I tried multiple things offered on stack overflow including the the following: Running etc\dev-cert\create-certificate.ps1 Running dotnet dev-certs https --clean Running dotnet dev-certs https --trust

The dev-certs is only working on domain localhost, can you share the full logs?

Hi,

You can try subscribing a EntityCreatedEto<FileDescriptorEto> event

public class My...Handler:  IDistributedEventHandler<EntityCreatedEto<FileDescriptorEto>>, ITransientDependency
{
   //.....
}