Activities of "Mehmet"

Hi @Repunjay

I have found a solution on Stackoverflow.

Can you also check your node version? You can run the following command to learn the version:

node --version

It should be v12.x.x

Hi @gvnuysal

Open styles.scss file and add the below style to hide the footer:

abp-application-layout footer.lp-footer {
  display: none;
}

You can get the current user informatin as shown below:

import { ConfigStateService, ApplicationConfiguration } from '@abp/ng.core';

@Component(/* component metadata*/)
export class YourComponent {
  constructor(private config: ConfigStateService) {
    const currentUser = this.config.getOne('currentUser') as ApplicationConfiguration.CurrentUser;
   }
}

If you like to get access token, call the getAccessToken() method of OAuthService:

import { OAuthService } from 'angular-oauth2-oidc';

@Component(/* component metadata */)
export class YourComponent {
  constructor(private oAuthService: OAuthService) {
    const accessToken = this.oAuthService.getAccessToken()
  }
}

I hope your questions are answered. Thanks.

Hi @humood1990

The problem will be resolved in v3.0.5. Here is the raised PR: https://github.com/abpframework/abp/pull/4868

Thanks for reporting, your one question credit will be refunded.

Hi @drpdev2

1- Can you share code example with us? I can't reproduce it.

I found a bug in ThemeLeptonModule. We'll fix it. You can override the validation messages in v3.0.5. I created an issue about this. See the issue and please read the description.

The v2.9 to v3.0 Angular UI Migration Guide may help you for upgrading the v3.x The @ngx-validate/core package code example also may help you to learn how it is working.

Thanks for reporting. We refunded your one question credit.

We have created an issue about this. We'll probably add new permissions for user management in v3.1.

The permissions you have disabled don't affect another page. E.g if you disable all organization units permissions, the organization units tab in the users page don't be hidden.

1- You can modify all buttons under an actions button. See the Entity Action Extensions for Angular UI document to learn how can you be done it.

2- As of v3.0.5, you can hide the "Organization Units" tab with some style codes.

Open the styles.scss file in the src folder and add the following:

#user-nav-tabs #user-organization-units {
  display: none;
}

Second way is temporary. Please use new permissions to hide/show the "Organization Units" tab and remove the style above in v3.1. HTML IDs can be changed or removed, not reliable for development.

We also fixed the authorization error above. We'll release the v3.0.5 soon.

Thanks for reporting ☺️

Hi @jackmcelhinney

It seems a bug. We'll fix the problem. You won't need to override the Angular UI.

Hi @gexiaoxu

application.logoUrl property is not working with ABP Commercial app. You should replace the logos in the assets/images/logo with your logos without changing the file names to change the logo. See the description about lepton theme logos

Please replace the package.json with below, remove yarn.lock file and run the yarn command. The problem will be resolved.

{
  "name": "MyApplication",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve --open",
    "build": "ng build",
    "build:prod": "ng build --configuration production",
    "test": "jest",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "jest": {
    "preset": "jest-preset-angular",
    "setupFilesAfterEnv": [
      "<rootDir>/setupJest.ts"
    ],
    "testPathIgnorePatterns": [
      "<rootDir>/node_modules/",
      "<rootDir>/dist/",
      "<rootDir>/src/test.ts"
    ]
  },
  "dependencies": {
    "@abp/ng.setting-management": "~2.7.0",
    "@angular/animations": "~9.1.0",
    "@angular/cdk": "^9.2.4",
    "@angular/common": "~9.1.0",
    "@angular/compiler": "~9.1.0",
    "@angular/core": "~9.1.0",
    "@angular/forms": "~9.1.0",
    "@angular/material": "^9.2.4",
    "@angular/platform-browser": "~9.1.0",
    "@angular/platform-browser-dynamic": "~9.1.0",
    "@angular/router": "~9.1.0",
    "@types/jest": "^26.0.0",
    "@volo/abp.ng.account": "~2.7.0",
    "@volo/abp.ng.audit-logging": "~2.7.0",
    "@volo/abp.ng.identity": "~2.7.0",
    "@volo/abp.ng.identity-server": "~2.7.0",
    "@volo/abp.ng.language-management": "~2.7.0",
    "@volo/abp.ng.saas": "~2.7.0",
    "@volo/abp.ng.text-template-management": "~2.7.0",
    "@volo/abp.ng.theme.lepton": "~2.7.0",
    "jest": "^26.0.1",
    "jest-preset-angular": "^8.2.1",
    "rxjs": "~6.5.4",
    "tslib": "^1.10.0",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.901.0",
    "@angular-devkit/build-ng-packagr": "~0.901.0",
    "@angular/cli": "~9.1.0",
    "@angular/compiler-cli": "~9.1.0",
    "@angular/language-service": "~9.1.0",
    "@ngxs/logger-plugin": "^3.6.2",
    "@types/node": "^12.11.1",
    "codelyzer": "^5.1.2",
    "ng-packagr": "^9.0.0",
    "ngxs-schematic": "^1.1.9",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~3.8.3"
  },
  "resolutions": {
    "@abp/ng.core": "~2.7.0",
    "@abp/ng.feature-management": "~2.7.0",
    "@abp/ng.theme.shared": "~2.7.0",
    "@abp/ng.permission-management": "~2.7.0",
    "@abp/ng.setting-management.config": "~2.7.0",
    "@abp/utils": "~2.7.0",
    "@volo/abp.commercial.ng.ui": "~2.7.0",
    "@volo/abp.ng.account.config": "~2.7.0",
    "@volo/abp.ng.audit-logging.config": "~2.7.0",
    "@volo/abp.ng.language-management.config": "~2.7.0",
    "@volo/abp.ng.identity-server.config": "~2.7.0",
    "@volo/abp.ng.identity.config": "~2.7.0",
    "@volo/abp.ng.saas.config": "~2.7.0",
    "@volo/abp.ng.text-template-management.config": "~2.7.0"
  }
}

If you upgrade the ABP version to the latest, you don't need to add resolutions to package.json.

See the new versions after configuration above:

Hi

We created RoutesService and deprecated the dispatchAddRoute method. See the RoutesService document and v2.9 to v3.0 Angular UI Migration Guide

Can you share your dependencies in package.json with us? It seems the versions of @volo/* packages is ~2.6.0. As you specified above, your ABP Framework version is v2.7.0. You should upgrade all @volo/* packages to v2.7.0