Hello,
You need to add FileManagementInitializer to your component's routing.
Example
// home.module.ts
import { NgModule } from '@angular/core';
import { HomeRoutingModule } from './home-routing.module';
import { HomeComponent } from './home.component';
import { FileManagementModule } from '@volo/abp.ng.file-management';
@NgModule({
declarations: [HomeComponent],
imports: [/*other modules*/HomeRoutingModule, FileManagementModule.forChild()],
})
export class HomeModule {}
// home-routing.module.ts
import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';
import { HomeComponent } from './home.component';
import { FileManagementInitializer } from '@volo/abp.ng.file-management';
const routes: Routes = [
{ path: '', component: HomeComponent, canActivate: [FileManagementInitializer] },
];
@NgModule({
imports: [RouterModule.forChild(routes)],
exports: [RouterModule],
})
export class HomeRoutingModule {}
Now datatable columns are initialized successfully.
Hello,
I opened a pull request for ABP implementation.
After these changes, you can navigate to the login page by clicking the log-in button page one time. You don't need to check explorer, desktop version, and login status in the component (Your layout component only includes layout methods and layout components).
I tried to reproduce your error but I can't reproduce it (I added a custom network throttling configuration upload 1kb download 1kb).
Can you share the backend log with the related token endpoint whose HTTP status is 400?
Can you inform us about what is the client's AbsoluteRefreshTokenLifetime, SlidingRefreshTokenLifetime?
Hello,
Can you inform us about your Operating System? Can you try generating again after removing angular/.suite folder?
Hello,
Top menu layout available with version ABP version 6. According to our plans, we will release version 6 one month later
Hello
I can't share because the issue is in the private repo. We realized also ABP Cli generates modules successfully.
You can use the command below to generate a module (Please run this command in the project root folder which includes angular and aspnet-core folders)
abp new Your.Module -t module --add-to-solution-file
I will inform you when the fix is available.
Hello,
The top menu layout is not available for now. It will be available in the next stable version
Hello,
Sorry for the late reply
I realized there are problems after generating custom module in the app pro template. Suite creates an angular project inside the projects folder and this app has angular project files (angular.json etc.). But projects folder should include only angular packages and angular applications. The config added to angular.json which is in the angular folder does not point to the created library.
We will work on this problem. For now, you can follow the steps below to avoid this error
Note: After applying these steps StartConfigModule's routeProviders successfully added routes to the menu. You don't need to add manually in the app routeProviders
For your example, these files should look like following
// tsconfig.json
"@top-tis.project-name/start": [ "projects/start/src/public-api.ts" ],
"@top-tis.project-name/start/config": [ "projects/start/config/src/public-api.ts" ]
// angular.json
{
// other configs
"projects": {
// other projects
"start": {
"projectType": "library",
"root": "projects/start",
"sourceRoot": "projects/start/src",
"prefix": "lib",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:ng-packagr",
"options": {
"project": "projects/start/ng-package.json"
},
"configurations": {
"production": {
"tsConfig": "projects/start/tsconfig.lib.prod.json"
},
"development": {
"tsConfig": "projects/start/tsconfig.lib.json"
}
},
"defaultConfiguration": "production"
},
"test": {
"builder": "@angular-devkit/build-angular:karma",
"options": {
"main": "projects/start/src/test.ts",
"tsConfig": "projects/start/tsconfig.spec.json",
"karmaConfig": "projects/start/karma.conf.js"
}
},
"lint": {
"builder": "@angular-eslint/builder:lint",
"options": {
"lintFilePatterns": ["projects/start/**/*.ts", "projects/start/**/*.html"]
}
}
}
}
}
}
Your credit refunded
Hello,
I created a new application with the application pro template in version 5.3.0. Modals displayed the same as the screenshot correct you shared.
Is there any error in your browser console? Are you have CSS rules which override modal styles?
Hello,
Can you send us an example project which includes this error?
Note: Please write the issue number(for this issue 3273) in the mail. Support mail address is support@abp.io
Hello,
What is your angular version?
Did you use the inject function outside of the class creation context (eg: in lifecycle methods). If you did this angular doesn't allow it. For more information, you can check official angular documentation