You mean every deployment, the Redis Cache should be cleared? How to enforce it in CI/CD pipeline? (Micro Services to Kubernetes)
Our pipeline would automatically execute DbMigrator project against QA database
We do have DataProtection Enabled. For each deployment Redis container would be cleared or not? From ABP Audit log, the code try to access /connect/authorize URL and the exception is: [ { "code": null, "message": "The data you have submitted has already been changed by another user. Discard your changes and try again.", "details": null, "data": null, "validationErrors": null }, { "code": null, "message": "The data you have submitted has already been changed by another user. Discard your changes and try again.", "details": null, "data": null, "validationErrors": null } ]
We disabled File Log when deployed to site. I noticed this happens after the site has a new deployment. Is it possible related to new feature of session management?
Yes, the app is using LeptonX theme. With help of AI, add the following styles to make scroll bar visible on main Lepton Content:
//Section ABP 9 Lepton 4.1.1 scroll bar fix // WebKit (Chrome, Safari, newer Edge) ::-webkit-scrollbar { width: 8px; height: 8px; display: block; }
::-webkit-scrollbar-track { background: #f1f1f1; border-radius: 4px; }
::-webkit-scrollbar-thumb { background: #aaa; border-radius: 4px; }
::-webkit-scrollbar-thumb:hover { background: #888; }
// Firefox
// Ensure the main scrollable containers have overflow properties set .lpx-content { overflow-y: auto !important; overflow-x: hidden !important; /* Fix for Lepton 4.4.1 scrollbar issues */ display: flex; flex-direction: column; height: 100%; max-height: 100vh; position: relative;
/* Force scrollbar visibility */ &::-webkit-scrollbar { width: 8px; height: 8px; display: block !important; opacity: 1 !important; visibility: visible !important; }
&::-webkit-scrollbar-track { background: #f1f1f1; border-radius: 4px; display: block !important; opacity: 1 !important; visibility: visible !important; }
&::-webkit-scrollbar-thumb { background: #aaa; border-radius: 4px; display: block !important; opacity: 1 !important; visibility: visible !important; } }
/* Additional fix for Lepton 4.4.1 - ensure main content area scrolls properly */ .lpx-wrapper { height: 100vh; display: flex; flex-direction: column; overflow: hidden; }
Add connection string to Identity Db in Administration Service works. Though after click save button, Angular app somehow automatically navigate to the home page. I comment this line since from that component code, when updating personal info (roles are not updated). There is no need to call refreshAppState().
I did figure out the solution from another project. It's a custom provider export const OVERRIDE_LEPTON_X_USER_MENU_PROVIDERS = [ { provide: APP_INITIALIZER, useFactory: configureUserMenu, deps: [Injector, Router], multi: true, }, ];
export function configureUserMenu(injector: Injector, router: Router) { const userMenu = injector.get(UserMenuService);
return () => {
userMenu.removeItem(eUserMenuItems.LinkedAccounts);
userMenu.removeItem(eUserMenuItems.SecurityLogs);
I am delighted to hear that your problem has been solved.
Can you help me on this thread? https://abp.io/support/questions/9210/ABP-Upgrade-to-911--Click-profile-icon---point-to-auth-server-pages
Our app copied ABP 7.2.3 account and identity source code to Angular project, after revert to the original source code (module style), and fix several compile error. Now the admin menu works as before.
I figured out the reason, I replace the existing code:
export const APP_ROUTE_PROVIDER = [ { provide: APP_INITIALIZER, useFactory: configureRoutes, deps: [RoutesService, AppConfigService], multi: true, }, ];
With: export const APP_ROUTE_PROVIDER = [ provideAppInitializer(() => { configureRoutes(); }), ];
After revert back, there is only one Administration menu, however, when I click Roles or Users menu item, it complains: src_app_identity_identity-routes_ts.js:1 ERROR RuntimeError: NG04014: Invalid configuration of route 'identity/'. The component must be standalone. Notes: The app is converted to standalone mode, and we write our own identity components to replace ABP's identity component.
