Activities of "EngincanV"

It still happens to me even in my other projects not named "Demo". I have to fill the first page then add whatever column and save to avoid any loosing data.

I'm sorry I still could not reproduce it. Can you make a clean uninstallation by following the steps https://support.abp.io/QA/Questions/414/ABP-Suite-install-problem-How-can-I-reinstall-clean-install#answer-9c56ff0e-0a46-ffd1-dd08-39f78e032607 in this question? And then try in a private window? (I think it might be related to an extension that you are using, because we haven't got any other questions related to that, and currently I don't have any idea why it's happening)

Hi, I see. Is there a way to change this behavior so that it is replaced with a different component?

I'll create an internal issue for that, and try to implement it with 8.1.0-rc.2 or 8.1.0-rc.3.

Changing the Field="WorldRegion?" to Field="WorldRegion", should be a quick workaround in your case. You don't need to set it as non-nullable in the ABP Suite UI and re-generate the entity again. We will fix this bug in the upcoming version, thanks for reporting.

Also since this is a bug can you please credit me back this support ticket?

I have refunded your ticket. Best regards.

Hi, thank you very much for explanation, it is much more understandable for me now. I can see all of the field templates except the one used for TextArea. Templates in our solution are untouched.

I also tried to manually go through most of the templates, but I have not noticed the one, which would be responsible for generation of MemoEdit component.

Hi, the Frontend.Blazor.Page.Partials.Modal.Field.Text.txt component is used for text areas. We replace the TextEdit component with MemoEdit on the code side. when it's marked as "textarea".

I think it's a cli bug:

PS D:\github\modules\abp> abp get-source Volo.Abp.LeptonXTheme.Pro --output-folder "leptonX-theme-pro" --preview 
ABP CLI 8.1.0-rc.1 
Downloading source code of Volo.Abp.LeptonXTheme.Pro (Latest) 
Output folder: D:\github\modules\abp\leptonX-theme-pro 
The latest template version (3.1.0-rc.1) is different than the CLI version (8.1.0-rc.1). This may cause compatibility issues. 
Please upgrade/downgrade the CLI version to the template version. 
> dotnet tool uninstall -g volo.abp.cli 
> dotnet tool install -g volo.abp.cli --version 3.1.0-rc.1 
There is no version found with given version: 8.1.0-rc.1 
System.Exception: There is no version found with given version: 8.1.0-rc.1 
   at Volo.Abp.Cli.ProjectBuilding.AbpIoSourceCodeStore.GetAsync(String name, String type, String version, String templateSource, Boolean includePreReleases, Boolean skipCache, Boolean trustUserVersion) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\AbpIoSourceCodeStore.cs:line 156 
   at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 48 
   at Volo.Abp.Cli.Commands.Services.SourceCodeDownloadService.DownloadModuleAsync(String moduleName, String outputFolder, String version, String gitHubAbpLocalRepositoryPath, String gitHubVoloLocalRepositoryPath, AbpCommandLineOptions options) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\Services\SourceCodeDownloadService.cs:line 39 
   at Volo.Abp.Cli.Commands.GetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\GetSourceCommand.cs:line 59 
   at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 173 
   at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 80 
Unhandled exception. System.Exception: There is no version found with given version: 8.1.0-rc.1 
   at Volo.Abp.Cli.ProjectBuilding.AbpIoSourceCodeStore.GetAsync(String name, String type, String version, String templateSource, Boolean includePreReleases, Boolean skipCache, Boolean trustUserVersion) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\AbpIoSourceCodeStore.cs:line 156 
   at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 48 
   at Volo.Abp.Cli.Commands.Services.SourceCodeDownloadService.DownloadModuleAsync(String moduleName, String outputFolder, String version, String gitHubAbpLocalRepositoryPath, String gitHubVoloLocalRepositoryPath, AbpCommandLineOptions options) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\Services\SourceCodeDownloadService.cs:line 39 
   at Volo.Abp.Cli.Commands.GetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\GetSourceCommand.cs:line 59 
   at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 173 
   at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 80 
   at Volo.Abp.Cli.Program.Main(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli\Volo\Abp\Cli\Program.cs:line 43 
   at Volo.Abp.Cli.Program.<Main>(String[] args) 

also with fixed version:

PS D:\github\modules\abp> abp get-source Volo.Abp.LeptonXTheme.Pro --output-folder "leptonX-theme-pro" --version 3.1.0-rc.1 
ABP CLI 8.1.0-rc.1 
Downloading source code of Volo.Abp.LeptonXTheme.Pro (v3.1.0-rc.1) 
Output folder: D:\github\modules\abp\leptonX-theme-pro 
The specified template version (3.1.0-rc.1) is different than the CLI version (8.1.0-rc.1). This may cause compatibility issues. 
Please upgrade/downgrade the CLI version to the template version. 
> dotnet tool uninstall -g volo.abp.cli 
> dotnet tool install -g volo.abp.cli --version 3.1.0-rc.1 
We have changed the template version as the cli version. 
New version: 8.1.0-rc.1 
There is no version found with given version: 8.1.0-rc.1 
System.Exception: There is no version found with given version: 8.1.0-rc.1 
   at Volo.Abp.Cli.ProjectBuilding.AbpIoSourceCodeStore.GetAsync(String name, String type, String version, String templateSource, Boolean includePreReleases, Boolean skipCache, Boolean trustUserVersion) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\AbpIoSourceCodeStore.cs:line 156 
   at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 48 
   at Volo.Abp.Cli.Commands.Services.SourceCodeDownloadService.DownloadModuleAsync(String moduleName, String outputFolder, String version, String gitHubAbpLocalRepositoryPath, String gitHubVoloLocalRepositoryPath, AbpCommandLineOptions options) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\Services\SourceCodeDownloadService.cs:line 39 
   at Volo.Abp.Cli.Commands.GetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\GetSourceCommand.cs:line 59 
   at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 173 
   at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 80 
Unhandled exception. System.Exception: There is no version found with given version: 8.1.0-rc.1 
   at Volo.Abp.Cli.ProjectBuilding.AbpIoSourceCodeStore.GetAsync(String name, String type, String version, String templateSource, Boolean includePreReleases, Boolean skipCache, Boolean trustUserVersion) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\AbpIoSourceCodeStore.cs:line 156 
   at Volo.Abp.Cli.ProjectBuilding.ModuleProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\ModuleProjectBuilder.cs:line 48 
   at Volo.Abp.Cli.Commands.Services.SourceCodeDownloadService.DownloadModuleAsync(String moduleName, String outputFolder, String version, String gitHubAbpLocalRepositoryPath, String gitHubVoloLocalRepositoryPath, AbpCommandLineOptions options) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\Services\SourceCodeDownloadService.cs:line 39 
   at Volo.Abp.Cli.Commands.GetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\GetSourceCommand.cs:line 59 
   at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 173 
   at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 80 
   at Volo.Abp.Cli.Program.Main(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli\Volo\Abp\Cli\Program.cs:line 43 
   at Volo.Abp.Cli.Program.<Main>(String[] args) 

wow, what is this?

Please upgrade/downgrade the CLI version to the template version. We have changed the template version as the cli version.

when I want to download a fixed version why does CLI decide to change the version? Is this a joke from the development team? so remove the --version flag because it's useless anymore. wow. This is very unexpected from your team

Thanks for reporting this problem, but we already fixed it: https://github.com/abpframework/abp/pull/19095 It will be included with v8.1.0-rc.2+.

Sure, I created a Loom with the footage of the issue.

https://www.loom.com/share/0281cc2d84f24cc6950b803db9755ccf?sid=1661c041-1e0d-48b9-8cb4-9146716bc9c2

Dear EngincanV, I have also another issue with migrations. Sometimes the demo2 (with version 8.1.0.rc-1) doesn't apply any migrations at all, it's a weird bug because it happens (sometimes!!) when the project is created or when I create or update an already existing entity (It happens randomly). I will try to create a loom at the exact moment when It happens.

Hi, thanks for sharing the problem with a gif. Weirdly, I could not reproduce the entity deletion problem, and also could not reproduce the" entity names can not be the same with the namespace" problem.

I think it might be related to that you had a project name "Demo2" in the appsettings.json file of the ABP Suite and when you create a new project with the same name and by having the same entity "Book", it might get confused and gives the errors. So, can you check that you have a project with the name "Demo2" twice in the appsettings.json file?

What I acknowledge is that I'm able to edit the template to the point it would generate what I want, thanks to the present if branching a looping logic, but it feels like a really impractical solution to me. What I'm confused about the most are these variables:

    %%main-edit-tab-opener%% 
    %%razor-modal-fields-edit%% 
    %%main-tab-closer%% 
    %%razor-modal-navigation-connection-fields-editing%% 

• %%main-edit-tab-opener%% -> this only creates an opening tab for the TabPanel component (<TabPanel Name="..">) on the code side.
• %%razor-modal-fields-edit%% -> this corresponds to the related field components and you can edit the related txt files such as Field.Text.txt, Field.DateTime.txt, Frontend.Blazor.Page.Partials.Modal.Field.Numeric.txt, Frontend.Blazor.Page.Partials.Modal.Field.Bool.txt and Frontend.Blazor.Page.Partials.Modal.Field.Enum.txt
• %%main-tab-closer%% -> This is just for the closing tag of the TabPanel component (</TabPanel>)
• %%razor-modal-navigation-connection-fields-editing%% -> This is for navigation connections and use the field components again. (So, you can edit the related txt files like in the %%razor-modal-fields-edit%% placeholder)

I will update the Editing Templates documentation.

Best Regards.

Hi, how can I reproduce it? I have created a project named "Demo2" like yours and filled in the entity metadata as in the screenshot that you shared, but could not reproduce it:

Hi, I created an article to show how to hide ABP related endpoints on Swagger UI by simply checking from the settings page. Your requirement is almost the same, so you can follow this article and update it according to your needs.

Also, please notice if you want to hide ABP-related endpoints on Swagger UI on development time, you can use the built-in option:
https://docs.abp.io/en/abp/latest/API/Swagger-Integration#hide-abp-endpoints-on-swagger-ui

Thanks, I used this method to hide endpoints before. But, we want t o manage this option dynamically. For example, if admin user select some module from UI, then we want to show it on swagger. Otherwise, users should not see this module's endpoints Is it possible?

Yes, it's possible. You need to create a custom document filter, check if the related permission is granted, or check if the role is admin for example, and then provide the related endpoints that you want to show by filtering endpoints.

But, as you would guess, this is a custom need and we are not providing a built-in option for that. So, you should create the document filter by yourself according to your needs.

Hi, I created an article to show how to hide ABP related endpoints on Swagger UI by simply checking from the settings page. Your requirement is almost the same, so you can follow this article and update it according to your needs.

Also, please notice if you want to hide ABP-related endpoints on Swagger UI on development time, you can use the built-in option: https://docs.abp.io/en/abp/latest/API/Swagger-Integration#hide-abp-endpoints-on-swagger-ui