Activities of "alper"

I would like to change the database table prefix for IdentityServer.

To update your version to v4.3.x for both ABP CLI and ABP Suite run the following command

dotnet tool update -g Volo.Abp.Cli --version 4.3.0-rc.1
abp suite update --preview

or

Run this PowerShell script to update both the CLI and Suite to the latest including the preview versions.

v4.3 Preview ABP Framework Version Notes https://blog.abp.io/abp/ABP-Framework-4.3-RC-Has-Been-Published

v4.3 Preview ABP Commercial Version Notes https://blog.abp.io/abp/ABP-Commercial-4.3-RC-Has-Been-Published

From 4.x to 4.3 Migration Guide https://docs.abp.io/en/commercial/4.3/migration-guides/v4_3

What's the default credentials of the ABP Framework login page?

@huseyin.cakirli reports an issue about working Redis with password keyword.

ABP works with Redis with server-ip:port string. but when we use the following formats it doesn't connect redis_server_ip:redis_port,password=REDIS_PASSWORD_HERE or redis_password@redis_server_ip:redis_port

reported here https://support.abp.io/QA/Questions/287#answer-0eb2a565-8f43-115b-3e34-39fa7f9c1875

I have a requirement to use Suite from command line for my CI/CD pipeline

If you face with one of the following problems:

• I have upgraded to a higher license and it still shows my previous license information.
• License check failed for 'XYZ'. You need to log in using the command abp login <username>.

To update your version to the latest (v4.2) for both ABP CLI and ABP Suite run the following command

dotnet tool update -g Volo.Abp.Cli && abp suite update

v4.2 Preview Version Notes https://blog.abp.io/abp/ABP-IO-Platform-v4-2-RC-Has-Been-Released

v4.2 Final Version Notes https://blog.abp.io/abp/ABP.IO-Platform-4-2-Final-Has-Been-Released

I'm getting the following errror.

You are not granted permission to use the module 'XYZ'

Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: XXXX

System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'WebPlatformDbContext'.

@jackmcelhinney asks here