Ends in:
7 DAYS
21 HRS
29 MIN
42 SEC
Ends in:
7 D
21 H
29 M
42 S

Activities of "Bryan-EDV"

Hi,

I am aware of the local event bus. However would prefer to use the conventional EventHandler<TEventArgs> delegate to set up events as some other parts of our application has used those and we would like to ensure code consistency.

Are you able to provide any insights as to why the dependency injection was failing?

Thanks

Specifically, we want TenantId property to be available on OpenIdApplication table. We want to be able to map openIdapplication based on tenantId. We also need it to be visible on the Create / Update and View UI screens

thanks,

fyi managed to solve new question issue by removing serverBuilder.SetIssuer(new Uri(configuration["AuthServer:Authority"]!));

Also, do you happen to know the change you made in this ticket: https://abp.io/qa/questions/7297/3a130461-8b69-1a8a-743f-133fccbac906

We are having the exact same issue whereby the issuer still defaults to the main domain of the backend (api.mydomain.com) instead of the subdomain (tenant.api.mydomain.com).

Hi managed to get it resolved. We realised that as part of our CI/CD pipeline, we were running dotnet publish "MyApp.sln"

During the creation of artifacts, the last project to be published is NOT the HttpApi.Host project. Hence, appsettings.json for HttpApi.Host was overwritten by another project appsettings.json.

The resolution was to only publish the needed artifact i.e. dotnet publish "MyApp.HttpApi.Host/MyApp.HttpApi.Host.csproj"

Note: the commands are not exactly as used in our project but conveys the idea (we also added flags such as -c Release etc)

Will post the results here soon

Manage to solve with this -> https://abp.io/docs/latest/framework/fundamentals/object-extensions?_redirected=B8ABF606AA1BDF5C629883DF1061649A

Thank you, will close the ticket

@Bryan-EDV if you want to update only texts you can use the localization text files. @maliming provided you the localization keys. if you add these keys in your localization file (en.json) it'll be changed. also you can change the colors and other styles with simple CSS overrides. but if you want to radically change this bar, you need to replace this component as stated here.

Hi, Thanks for the reply, I explored doing css overrides but this component is not in the classes that i can overwrite, so i think i'm left with replacing the whole component.

Is this the correct replaceable component? I am on abp v8.3, eGdprConfigComponents.CookieConsent does not work

`import { eGdprComponents } from '@volo/abp.ng.gdpr';

key : eGdprComponents.PersonalData `

I'm also under the impression that all source code will be included in the Enterprise version (which my company has purchased), however i didn't find any for this cookie consent bar. can you kindly point me to it? thank you.

hi

Can you inspect this element with dev tool to see if it is a angular or MVC component?

it looks like this:

hi

The component is rendered by AbpCookieConsentViewComponent(Volo.Abp.Gdpr.Web.Pages.Gdpr.Components.CookieConsent;)

You can override it.

Hi, thanks for the reply,

Can i customize this in my angular proj? instead of MVC?

Showing 1 to 10 of 29 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06