Activities of "EngincanV"

Hi, for dashboard authorization please refer to our documentation: https://abp.io/docs/latest/framework/infrastructure/background-jobs/hangfire#dashboard-authorization

Hi, can you confirm if I'll update hangfire code, it will be applicable for all background jobs added in application ?

Yes. When you integrate Hangfire, it replaces the default background job manager, and Hangfire’s own job manager will be used instead.

Hi, I referred document, I added permission, but it is not working, I'm getting 401 status code on accessing the dashboard even if permission is added, it is working in local but after deployment as my UI and backend is deployed on different server, I'm not able to access, what is the possible solution with this scenario?

Did you apply the all steps described at https://abp.io/docs/latest/framework/infrastructure/background-jobs/hangfire#dashboard-authorization-in-api-projects?

1-)

2-)

If you applied, can you share the error log?

as per the call can you confirm the mappings

  - 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 

... which of these are viable for a Layered / non-tiered Blazor-interactive?

where the app projects of note are: .Blazor .Client .HttpApi .Http.Client ....etc

Hi,

This ticket was originally about the ABP Studio installation problem, and as far as I understand, your installation issue was resolved during the meeting. (If so, maybe we can close this question)

For your deployment-related questions or issues, could you please create a new ticket? That way, we can assign the appropriate team member to assist you.

Thank you for your understanding. Best regards.

Hi,

Q1/ Sidebar Menu and Toolbar Support: Our project is essentially an admin panel with features and menus that vary based on the user type. We’re currently using a layout that includes a sidebar menu and a toolbar, both of which are essential and must remain intact. If we proceed with the Basic Theme, will it support customizing or overriding these elements (SidebarMenu, Toolbar, etc.)? Or would we need to consider using Lepton Lite instead—so we can keep things open-source while also preserving those layout capabilities?

Here are the layout parts of Basic Theme:

These parts are implemented for all of our supported themes and the only difference is the placement. If the placement is important for you, then you can continue with LeptonX Lite. Also, if you want to go with a side-bar menu, then yes it can be better to go with LeptonX Lite.

Q2 / Reusability and Upgrade Compatibility: Once created, will this custom package remain compatible with future updates to .NET, ABP, or the base theme it’s derived from? Or should we expect to manually modify and update the package each time a new version is released?

When you implement a layout or theme, unfortunately, you are on your own (we are always here for support, but I mean responsibility is on your shoulders). Since the related places are overridden, ABP's version upgrade might not work for you and you may need to manually update ABP's components (if needed). However, our themes are mature, so that means we are not making frequent changes to them, so this should not impact you for most of the time.

Hi, for dashboard authorization please refer to our documentation: https://abp.io/docs/latest/framework/infrastructure/background-jobs/hangfire#dashboard-authorization

Hi, can you confirm if I'll update hangfire code, it will be applicable for all background jobs added in application ?

Yes. When you integrate Hangfire, it replaces the default background job manager, and Hangfire’s own job manager will be used instead.

Hi, first of all, sorry for the late response, and thanks for the detailed explanation.

All 3 options can be the way to go, but our suggestion is to add the Basic Theme Source Code into your solution and then customize it according to your needs. Here is our documentation to briefly explain that: https://abp.io/docs/latest/framework/ui/blazor/theming?UI=Blazor#implementing-a-theme

Since our Basic Theme is built with Bootstrap 5 and Metronic Theme is also Bootstrap-based, pages that come from our modules should be used without having any trouble.

Also, there are some community articles and videos that demonstrate how to use another theme rather than LeptonX Theme ( - not for Metronic Theme but MudBlazor - (but the steps are similar)):

• https://abp.io/community/videos/customize-abp-blazor-application-ui-with-mudblazor-wscmpu3w
• https://abp.io/community/articles/mudblazor-theme-in-abp-blazor-webassembly-ae23zz17

You can always check these contents for reference sources.

You can start with the basic theme and try to implement the Metronic Theme. If you face with an issue, feel free to write here or create a new question.

Regards.

Hi,

I have followed documentation for SignalR module (https://abp.io/docs/latest/framework/real-time/signalr). I added npm dependency for @abp/signalr, and added SignalRBrowserScriptContributor.

You don't need to do that, because the Chat module already uses signalR behind the scene in both the C# and JS side (NuGet & NPM packages).

Here are all the steps for the configuration:

1. Run the abp add-module Volo.Chat command in your solution. (This command will add the all necessary packages for your solution and the related dependson statements. (also adds the related NPM package to your package.json file: "@volo/chat": "~8.2.2",))
2. Then check your .HttpApi.Host project and ensure there is a reference to the Volo.Chat.SignalR package and in the right version.

Then, your configuration should be done, and when you run your application, it should work seamlessly.

If your configuration is similar, and the real-time messaging is working then probably the "unread message count" badge had a problem in the related version and then it's fixed. So, please consider updating your ABP version, in that case.

Regards.

Just to confirm, in order to test it, I'm logging as a user into the portal, picking "My account" from user settings and the "Change the password". I have noticed, this is different application from main portal(Account is from "Auth" project and it's hosted on the different page).

Yes, you should add your dependency replacement in the relevant application. You might be doing the replacement in the wrong application. Can you also try that and let me know?

Because with the suggested ways, it should have hit the breakpoints and you should have seen them in the debug mode.

Hi, you can inject the ILanguageTextRepository and use its InsertAsync method to insert new language texts:

            await LanguageTextRepository.InsertAsync(
                new LanguageText(
                    GuidGenerator.Create(),
                    resourceName,
                    cultureName,
                    name,
                    value,
                    CurrentTenant?.Id
                )
            );

However, we don't suggest that, because the Language texts are designed to get the already defined localizations from the module localization resources and allow you to change the localization value dynamically, not creating additional values. (https://abp.io/docs/latest/modules/language-management)

Regards.

Hi, here are the answers to your questions:

#1: Is this the best way to do this or is there an obvious "ABP way" that I'm missing?

To add a new toolbar item, there is a SetToolbarAsync method in your *.razor.cs file, you can also use it to add a new toolbar. (https://abp.io/docs/latest/framework/ui/blazor/page-header#page-toolbar)

Example:

        protected virtual ValueTask SetToolbarItemsAsync()
        {
            Toolbar.AddButton(L["ExportToExcel"], async () =>{ await DownloadAsExcelAsync(); }, IconName.Download);
            
            Toolbar.AddButton(L["NewLead"], async () =>
            {
                await OpenCreateLeadModalAsync();
            }, IconName.Add, requiredPolicyName: Issue9145Permissions.Leads.Create);

            return ValueTask.CompletedTask;
        }

#2 If it is the best way, how do I disable/hide the default create button (New Lead below)?

You can set the order for page toolbar items in the SetToolbarItemsAsync method. (AddButton method has an optional order parameter)

#3 On create and edit, how do I hide/disable the Dealership selector as we don't want any chance of it being changed before saving.

While establishing a 1-n relationship in ABP Suite, there is no option to hide the UI part for the selector, I guess this is what you are asking. The best option you have, is setting is as not required and manually hide it in the generated code.

Regards.

Hello @EngincanV,

It's kinda similar but that would be a bug them? It seems that ABP Studio is not looking their own Nuget.config from the project but tries to get from global source. Shouldn't ABP Studio add the registered user nuget into the global Nuget.config file them?

What would be the solution if I have more tools installed in my dev machine. Do I need to clear up all my repositories to change ABP Suite version from ABP Studio.

Hi, actually there is no code in the ABP Suite, that checks a path like "Roaming\NuGet\nuget.config", or similar points. As far as I understand, this is a problem of installing dotnet global tools from an external Nuget source and not related to the ABP Studio or ABP Suite itself.

But I'll create an internal issue so we can investigate better.