or User Organization Unit and its dependent Organization Unit in the hierarchy,
Hi, you can use the IdentityUserAppService's GetOrganizationUnitsAsync(Guid id) to get a user's all organization units. The result will be List<OrganizationUnitDto> and you can see the parentId's of the related organization units. If it's null, then it means it's a root organization unit.
Regards.
Hi @EngincanV,
Sure. Here are two documentation that you can refer:
I think these docs are not related as the issue is not related to cascade/restrict delete. I want to delete the dependent entity, instead of the principal entity.
Did you test my working ASP.NET Core Web API example app? https://cdn.fuzed.app/share/abp/EFCorePlayground.zip
The following ABP framework example app, with the same EF Core configuration, doesn't work: https://cdn.fuzed.app/share/abp/AbpEFCorePlayground.zip
Best regards, Steff Beckers
Hi, sorry for the misunderstanding (I thought you were expecting a cascade delete/update behavior). I will check your project and write you back asap.
Hello,
I created folders for AbpAccount and AbpIdentiy under Localizations within the Domain.Shared project.
Domain.Shared/Localizations/AbpAccount/en.json
{ "Culture": "en", "Texts": { "DisplayName:Name": "First name", "DisplayName:Surname": "Last name" } }Domain.Shared/Localizations/AbpIdentity/en.json
{ "Culture": "en", "Texts": { "DisplayName:Name": "First name", "DisplayName:Surname": "Last name", "Name": "First name", "Surname": "Last name" } }I modified the DomainSharedModule's ConfigureServices as follows:
Configure<AbpLocalizationOptions>(options => { ... options.Resources .Get<IdentityResource>() .AddVirtualJson("/Localization/AbpIdentity"); ... });I modified the ApplicationContractModule's ConfigurationServices as follows:
Configure<AbpLocalizationOptions>(options => { options.Resources .Get<AccountResource>() .AddVirtualJson("/Localization/AbpAccount"); });
It seems that you did everything right. By any chance, can you share your project via email, so I can better assist you? (support@abp.io with the ticket number)
Hi, you should download the source-code, make the customizations and then recompile to CSS for overriding/or using another font:
To download the source-code, you can use the following command:
abp get-source Volo.Abp.LeptonXTheme
Then, please follow the documentation: https://abp.io/docs/latest/ui-themes/lepton-x/source-files
You can also check this thread if you want.
Hi, we will check this problem and write you back asap. Thanks for your understanding.
Hi, can it be related to https://abp.io/support/questions/4596/Email-Parameter-pasword-set-to-NULL#answer-3a09b39b-df3d-fdcb-f5ee-8e1adf660f20 can you please check? You may have different DefaultPassPhrase for two projects.
And also please check that can you see the password in the database.
Hi, we are using Bootstrap for our tag helpers, and abp-tab is no exception. You should be able to hide tabs with both display:none; and visibility: hidden;. Please share more information if the following info doesn't help you.
You can hide the first tab as follows for an example on the js side:
$("ul#PermissionsTabs > li:first").hide();
//or for completely hiding all the tabs
$("ul#PermissionsTabs").hide();
If you want to do this on the CSS side, then you can do the following:
ul #PermissionsTabs
{
visibility: hidden !important; //or alternatively -> display: none !important;
}
Hi, yes you are right, there is a missing "steps" keyword before the invalid line. Here is the correct one:
# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
# More GitHub Actions for Azure: https://github.com/Azure/actions
name: Build and deploy ASP.Net Core with BlazorServer to Azure Web App
on:
push:
branches:
- main
workflow_dispatch:
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up .NET Core
uses: actions/setup-dotnet@v4
with:
dotnet-version: '8.x'
include-prerelease: true
- name: Install ABP CLI
run: |
dotnet tool install -g Volo.Abp.Cli
abp install-libs
shell: bash
- name: Build with dotnet
run: dotnet build --configuration Release
- name: Run migrations
run: dotnet run -- "${{ secrets.CONNECTION_STRING }}" # Set your connection string as a secret in your repository settings
working-directory: ./src/blazorservertierdemo.DbMigrator # Replace with your project name
- name: dotnet publish apihost
run: dotnet publish -c Release -o ${{env.DOTNET_ROOT}}/apihost
working-directory: ./src/blazorservertierdemo.HttpApi.Host # Replace with your project name
- name: Generate authserver.pfx
run: dotnet dev-certs https -v -ep ${{env.DOTNET_ROOT}}/apihost/authserver.pfx -p 2D7AA457-5D33-48D6-936F-C48E5EF468ED # Replace with your password
- name: dotnet publish webapp
run: dotnet publish -c Release -o ${{env.DOTNET_ROOT}}/webapp
working-directory: ./src/blazorservertierdemo.Blazor # Replace with your project name
- name: Upload artifact for apihost
uses: actions/upload-artifact@v4
with:
name: .net-apihost
path: ${{env.DOTNET_ROOT}}/apihost
- name: Upload artifact for webapp
uses: actions/upload-artifact@v4
with:
name: .net-webapp
path: ${{env.DOTNET_ROOT}}/webapp
deploy:
runs-on: ubuntu-latest
needs: build
environment:
name: 'Production'
url: ${{ steps.deploy-to-webapp-3.outputs.webapp-url }}
steps:
- name: Download artifact from apihost
uses: actions/download-artifact@v4
with:
name: .net-apihost
path: ./apihost
- name: Deploy apihost
id: deploy-to-webapp-2
uses: azure/webapps-deploy@v3
with:
app-name: 'apihost-blazorserver' # Replace with your app name
slot-name: 'Production'
publish-profile: ${{ secrets.apihostblazorserverPublishSettings }} # Set your Azure Web App to publish your profile as a secret in your repository settings
package: ./apihost
- name: Download artifact from webapp
uses: actions/download-artifact@v4
with:
name: .net-webapp
path: ./webapp
- name: Deploy webapp
id: deploy-to-webapp-3
uses: azure/webapps-deploy@v3
with:
app-name: 'webapp-blazorserver' # Replace with your app name
slot-name: 'Production'
publish-profile: ${{ secrets.webappblazorserverPublishSettings }} # Set your Azure Web App to publish your profile as a secret in your repository settings
package: ./webapp
Anyway, I just thought I'd let someone know. Also, may want to update the dot-net version since version 9 is out now.
I have created an issue for that: https://github.com/abpframework/abp/issues/22061
I noticed that when I click on the Download Publish Profile, mine does not download and says "Basic Authentication is Disabled". Is this supposed to be like that?
Yes, it's disabled by default, if you want to enable it, please refer to the answer below:
https://learn.microsoft.com/en-us/answers/questions/1497453/how-to-download-publish-profile
Hi, to add more than 10 custom-code placeholders, you should edit templates and add the relevant placeholder for the related templates. Here are the documents that you can check to see how to do that:
We are using Pomelo.EntityFrameworkCore.MySql NuGet package in our MySQL provider package, which is Volo.Abp.EntityFrameworkCore.MySQL. This package hasn't released a stable version for .NET 9 yet.
Therefore, the provider is unable to transform/process some SQL queries, we are closely following the stable 9.0.0 release of the Pomelo.EntityFrameworkCore.MySql package and we will update our provider when they release the stable version. (You can also follow the upgrade status from https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/issues/1841, if you want)
When using EF Core 9 with MySQL in ABP-based projects, you may encounter SQL translation issues. One of the key problems is that certain queries involving parameterized collections fail to translate correctly.
To fix this problem, you can open your module class of the *.EntityFrameworkCore project and configure the AbpDbContextOptions as follows:
//...
public class MyProjectEntityFrameworkCoreModule : AbpModule
{
public override void ConfigureServices(ServiceConfigurationContext context)
{
//...
Configure<AbpDbContextOptions>(options =>
{
options.UseMySQL(builder =>
{
//add the following line 👇
builder.TranslateParameterizedCollectionsToConstants();
});
});
}
}
Using the TranslateParameterizedCollectionsToConstants() option ensures that parameterized collections are translated into constants, preventing SQL translation errors.
