Hello,
I apologize for the delay in my response. I have thoroughly investigated the issue you reported but was unable to replicate it on my end. Given this, I recommend upgrading your application to version 8.0, which is more stable and well-supported.
Thank you for your understanding.
Hello, thank you for reporting this issue. It will be fixed by the next patch release where you can follow the details here. Your ticket will be refunded, either.
Hello, I could not duplicate your issue on my side. Normally, the warning pop up should behave in the right way.
For this reason, I suspect some other configuration that may result in this and that would be the best if you can share a sample project through this e-mail: sumeyye.kurtulus@volosoft.com
Hello, this problem can be related to this issue https://github.com/abpframework/abp/issues/19656 that was solved in a 8.1 patch.
Yes, you are right. However, the Navbar service is not the only place we handle the navigations and highlights. Because of this restriction, we are fixing the navbar items according to the route changes that is connected to the navbar routes component.
I can suggest you to modify the related part as follows:
this.navbarService.navbarItems$.subscribe((items) => {
items.forEach((item) => {
if (item.text === "Home") {
item.expanded = false;
item.selected = false;
}
if (item.text === "Administration") {
item.expanded = true;
item.selected = true;
}
});
this.menuItems = items;
});
By doing this you can reach such result:
Hello, I have investigated your case carefully. However, we cannot provide such functionality for the time being. Hence, I could not quite get how you implemented this block either
this.navbarService.navbarItems$.subscribe(items => {
items.forEach(item => {
if (item.text === 'Approve It') {
item.expanded = true;
} else {
item.expanded = false;
}
this.changeDetectorRef.markForCheck();
});
});
Hello, thank you for reporting this problem. It will be fixed as soon as possible for the next patch release. So, you can follow this issue and the next releases.
Your ticket will be refunded, either.
Hello, thank you for reporting this problem. It will be fixed as soon as possible for the next patch release. So, you can follow this issue and the next releases.
Your ticket will be refunded, either.
I also acknowledge your point, but it has to do nothing with the lepton-x configurations. It must be working right for the main project since then all configs are based on that project apart from the extra application that you have added.
I have duplicated the same case by cordially checking the locales file inside the sources. However, as you can presume that the files are not loaded because the project is some sort of an extension and we cannot serve such customization on our side.
For the sake of helping you, I can suggest you to utilize this way by replacing the path @angular/common/locales with the files that you can copy inside another folder, that depends on your business logic, so that the so-called unreachable files would become reachable.
// register-locale.ts
import { differentLocales } from '@abp/ng.core';
export function registerLocale(locale: string) {
return import(
/* webpackChunkName: "_locale-[request]"*/
/* webpackInclude: /[/\\](en|fr).js/ */
/* webpackExclude: /[/\\]global|extra/ */
`@angular/common/locales/${differentLocales[locale] || locale}.js`
)
}
// app.module.ts
import { registerLocale } from './register-locale';
@NgModule({
imports: [
// ...
CoreModule.forRoot({
// ...other options,
registerLocaleFn: registerLocale
}),
//...
]
Hello, thank you for giving more details that lead me to investigate further. However, I have not detected anything to fix on our side. As the error you receive implies, you will need to configure the localization setting according to this documentation.
Moreover, once I add this block for the angular-extra project, it works for the en-GB localization.
