Actually, I was nudged into upgrading to 10.4, and that magically fixed things. At least, the Angular generation issue. So the .suite folder located under the angular directory has been changed by now, and I didn't keep the zip file, sorry. It might be interesting to get some "cleaning" instructions, on how to start over with the Schematics components. Where can I find it?
Thank you for your response. You can check the ABP Suite version through the ABP Studio tool by following this document: Automatic Version Matching
To clear any potential Angular-side cache issues, you can delete the temporary .suite, node_modules, and yarn.lock files/folders. After that, reinstall the dependencies and run code generation again using the Suite tool. This process will automatically recreate a fresh .suite folder in the same location.
I do have another issue however, that I thought to be related, but it turns out it doesn't .
The app translations are not working anymore since the upgrade to 10.3. You can see the effect on https://dev.tvrs.thconsulting.be/, even when not logged in.
After reviewing your deployed website, I noticed that the following request does not return the expected localization key-value pairs:
api/abp/application-localization?CultureName=en&OnlyDynamics=false
This indicates that localization may not be functioning correctly in the deployed environment. You can review the following resources for more detailed information:
When I call https://backend.dev.tvrs.thconsulting.be/api/abp/application-localization?CultureName=en&OnlyDynamics=false I see a lot of return, but nothing specific to my own solution tvrs, only standard ABP messages
From this perspective, your custom translations should appear under the following scope:
"TVRS": {
"texts": {},
"baseResources": ["AbpValidation","AbpUi"]
},
You can let us know if you need any further assistance. Thank you for your cooperation.
Hello,
Thank you for sharing the related files and folders. I reviewed them and generated the code on my end; however, I was unable to reproduce the issue you described. Because of this, I suspect there may be a version mismatch between your application and the installed Suite version.
You can check your Suite version through ABP Studio as explained here: ABP Studio – Automatic Version Matching
Please ensure that the ABP Suite version is set to 10.3.0 if your project is also using version 10.3.0.
If the issue persists after verifying the versions, could you also share the .suite folder located under the angular directory?
Thank you for your cooperation.
Since the latest maintained stable version is 10.3, the fix will be implemented at this level.
Hello,
Thank you for reporting this issue. We plan to resolve it in the next patch release. You can follow upcoming releases here: https://github.com/abpframework/abp/releases
We will also process a refund for this ticket.
Please let us know if you need any further assistance. Thank you for your cooperation.
Hello,
Thank you for taking the time to try this out and for informing us about your situation. We will update the migration documentation accordingly.
You can find the latest guidance for logo replacement in the following documentation: Logo Component Replacement Documentation
Please let us know if you need any further assistance. Thank you again for your cooperation.
Thank you for the detailed explanation. However, this behavior is intentional and based on a design decision for that specific module. Therefore, the files are not actually missing. While we continue to support older versions, newer versions may still be updated according to our roadmap.
If your goal is to use older templates with the latest ABP versions and features, you may encounter compatibility issues. In such cases, the documentation can help guide you through any necessary adjustments: https://abp.io/docs/9.2/get-started
Alternatively, if you are planning to start a new project, you may want to review the latest documentation to find the most suitable template: https://abp.io/docs/latest/get-started#which-startup-template-is-suitable-for-me
Correct me if I am mistaken, but this DDD module cannot function as a host application on its own. Instead, it is intended to be consumed by a host application.
I also suspect that the application builder migration might lead to a similar issue, so through a different mechanism. Could you confirm whether your problem resembles the one described here?
https://abp.io/community/articles/angular-library-linking-made-easy-paths-workspaces-and-5z2ate6e#how-path-references-worked-before-the-new-angular-application-builder
If your issue appears to be different, please feel free to share a minimal reproducible example via email (sumeyye.kurtulus@volosoft.com) or through any method you prefer.
Thank you for your cooperation.
Hello,
Thank you for the detailed explanation and the steps you shared. After reproducing the issue on my side, it appears to be related to change detection.
The application layout is rendered by <abp-dynamic-layout />, which determines the appropriate layout by listening to router events and updating its internal state on navigation. These updates depend on Angular’s default Zone.js–based change detection to trigger a re-render. By adding provideZoneChangeDetection() in app.module.ts, we explicitly enable this mechanism, allowing the layout selected for each route (for example, eLayoutType.application from route.provider.ts) to render correctly. This resolved the issue in my testing. Without it, the layout selection logic still executes, but Angular does not receive a signal to refresh the view, so the layout is not displayed.
We continue to support the module-based structure in Angular, so there’s no need to migrate to standalone components at this stage. Please try adding this provider on your end and let us know the result. Based on your feedback, we can update the migration guide if needed.
Thank you for your cooperation and patience.
Hello,
Thank you for the detailed description of the issue. The errors you are encountering are likely due to the modular template being added as a DDD module without being properly integrated into a host application, which is required for it to function correctly.
For more information, I recommend reviewing the following resources:
If you need any further assistance, please do not hesitate to reach out. Thank you for your cooperation.
Hello,
After reviewing the issue with replacing the user menu items, it appears that the AI response may have led you in the wrong direction starting from this point:
https://abp.io/qa/questions/10591/3a20a9c1-487c-9567-8f42-16c1e04f90a9
Could you try the following approach instead:
// user-menu.provider.ts
import { ConfigStateService } from '@abp/ng.core';
import { UserMenuService } from '@abp/ng.theme.shared';
import { inject, provideAppInitializer } from '@angular/core';
import { Router } from '@angular/router';
import { eUserMenuItems } from '@volosoft/abp.ng.theme.lepton-x';
export const USER_MENU_PROVIDER = [
provideAppInitializer(async () => {
configureUserMenu();
}),
];
export function configureUserMenu() {
const userMenu = inject(UserMenuService);
const router = inject(Router);
const configState = inject(ConfigStateService);
configState.getOne$('currentUser').subscribe(currentUser => {
if (!currentUser?.isAuthenticated) return;
userMenu.removeItem(eUserMenuItems.LinkedAccounts);
userMenu.removeItem(eUserMenuItems.SecurityLogs);
userMenu.removeItem(eUserMenuItems.AuthorityDelegation);
userMenu.removeItem(eUserMenuItems.ExternalLogins);
userMenu.removeItem(eUserMenuItems.Sessions);
userMenu.patchItem(eUserMenuItems.MyAccount, {
action: () => router.navigate(['/account/manage']),
});
});
}
// app.config.ts
import { USER_MENU_PROVIDER } from './user-menu-provider';
export const appConfig: ApplicationConfig = {
providers: [
//...
USER_MENU_PROVIDER,
],
};
You can let us know if you need further assistance. Thank you for your cooperation.
