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
94 Answer(s)
-
0
Thanks for your information @sgal. I reproduced your problem and as you say user interface (Angular) could not be generated. I've created an issue about it.
-
0
Dears,
I have a working abp in local environment, when I published to local staging server (without https) it runs but no login links work, all (Login) links in menu and homepage does not do anything!
I have no error in console.
Any idea?
It is 4.2 version (Angular) Commercial
-
0
The issue is solved by changing http to be https (unfortunately there is no error message to tell the the issue, you just need to guess!)
Dears,
I have a working abp in local environment, when I published to local staging server (without https) it runs but no login links work, all (Login) links in menu and homepage does not do anything!
I have no error in console.
Any idea?
It is 4.2 version (Angular) Commercial
-
0
Hello! Two small bugs to report:
With Angular UI, the Administration sidebar menu closes after selecting an element. For example, starting from the Home page, click
Administration
->Identity Management
->Roles
. It navigates to the Roles page but the Administration menu collapses. Not sure if this was introduced in 4.1 or 4.2 as we upgraded from 4.0 to 4.2.The lockout message in English could use a few fixes. Please notice the bold and strike-through below.
Your account has been locked by the admin or due to invalid login attempts. Please try again later. Contact ~~to~~ your system administrator if you think this is a mistake.
As always, thanks for the help!
Edit:
Here are two more:
- With Angular UI, when signed in with an account that does not have any administration permissions, the administration menu button briefly shows when clicking other menu items. This happens frequently but seemingly randomly.
- The cancel button on the login page does not properly return to the unauthenticated app when using Angular UI. It seems to redirect to
http://localhost:4200/?error=access_denied
and throws this error in the console:
core.js:4197 ERROR OAuthErrorEvent {type: "code_error", reason: {…}, params: {…}}
-
1
Hi,
I think it's fixed in the latest version. I couldn't reproduce it on our demo website which is also Angular commercial.abp.io/demo
For the last 2 items, I created an issue.
-
0
-
0
Hi, Suite not create generate files for blazor in module template. Can you fix it in 4.3? We are doing same think for copy past on application template.
-
0
@ilitzy your template pls? blazor, mvc, angular.
@murat.yuceer 4.3 RC deployment is still ongoing so some packages maybe still in publish phase.
-
0
-
1
1.I created a new project ( MVC - EF - 4.2.2)
On build I see error in d:\abptest2\src\Test.Domain.Shared\TestDomainSharedModule.cs(38,23): error CS0246: The type or namespace name "AbpIdentityProDomainSharedModule" could not be found (are you missing a using directive or an assembly reference?)[d:\abptest2\src\Test.Domain.Shared\Test.Domain.Shared.csproj]
-
0
-
0
hi @serdar,
this on my list, I'll check this tomorrow.
-
0
1.I created a new project ( MVC - EF - 4.2.2)
2. Add Lepton Theme module with source code.
- And :
any comment ?
New packages have been added to Lepton, some of them have been renamed. we made it backwards compatible, but since we cannot change the 4.2.2 version of the CLI. You should do it with 4.3.0 RC version. Or you can completely update your project to the latest preview (if that's not a problem for you)
-
0
@Serdar
If you don't want to update your project to v4.3.0, you can run the following Cli commands:
dotnet tool uninstall Volo.Abp.Cli -g
dotnet tool install Volo.Abp.Cli -g --version 4.3.0-rc.2
abp add-module Volo.LeptonTheme --with-source-code --add-to-solution-file
(Run in the folder of the .Sln file of your project)dotnet tool uninstall Volo.Abp.Cli -g
dotnet tool install Volo.Abp.Cli -g
This commands will install ABP CLI with the latest preview version, add LeptonTheme correctly and them switch ABP CLI version back to 4.2.2
-
0
1.I created a new project ( MVC - EF - 4.2.2)
2. Add Lepton Theme module with source code.
- And :
any comment ?
New packages have been added to Lepton, some of them have been renamed. we made it backwards compatible, but since we cannot change the 4.2.2 version of the CLI. You should do it with 4.3.0 RC version. Or you can completely update your project to the latest preview (if that's not a problem for you)
ok, Alper. I'm looking forward to 4.3 Release already.
-
0
@Serdar
If you don't want to update your project to v4.3.0, you can run the following Cli commands:
dotnet tool uninstall Volo.Abp.Cli -g
dotnet tool install Volo.Abp.Cli -g --version 4.3.0-rc.2
abp add-module Volo.LeptonTheme --with-source-code --add-to-solution-file
(Run in the folder of the .Sln file of your project)dotnet tool uninstall Volo.Abp.Cli -g
dotnet tool install Volo.Abp.Cli -g
This commands will install ABP CLI with the latest preview version, add LeptonTheme correctly and them switch ABP CLI version back to 4.2.2
Thanks @yekalkan. I will use this.
-
0
There is an issue with the current UnitOfWork system of the ABP Framework. Please see https://github.com/abpframework/abp/issues/8740 for the details. As of now, I can confirm the issue in 4.2.2 which is my current version. I have not tested additional versions.
The code for the AppService.UpdateAsync method which gets generated by ABP Suite is problematic. The default for the autoSave parameter is false which may fail silently in certain situations.
-
0
@scott7106 I've checked the issue and related Suite template will be updated in v4.31. For a workaround you can update your Suite template. Open Suite, go to Templates tab. Search for
AppService.txt
Find the
UpdateAsync
line and add theautoSave: true
argument.%%entity-name-camelcase%% = await _%%entity-name-camelcase%%Repository.UpdateAsync(%%entity-name-camelcase%%, autoSave: true);
-
0
This question has been automatically marked as stale because it has not had recent activity.