Activities of "Mehmet"

Hi @DanielAndreasen

This problem has been resolved with v3.2-rc.2.

Hi @ali.turkmen

The problem has been fixed. I am closing the ticket. You can try when v3.2-rc.3 released. If you try and see a problem, please let me know.

Thanks.

Hi @ali.turkmen

I have opened an issue: https://github.com/abpframework/abp/issues/5582

Thanks for reporting, we will be fixed the problem.

Hi @murat.kebabci

Unfortunately, the authorization code flow does not work with a backend that running on HTTP. You should run your backend on HTTPS URL or change the oAuthConfig for resource owner password flow.

oAuthConfig for resource owner password flow:

  oAuthConfig: {
    issuer: 'http://localhost:5002',
    clientId: 'XXX_App',
    dummyClientSecret: '1q2w3e*',
    scope: 'XXX',
    oidc: false,
    requireHttps: false,
  },

See that question related to this: https://support.abp.io/QA/Questions/411/how-to-config-oAuthConfig-in-angular

v3.1.1 has been released. We fixed some problems in the module template with this version. I suggest you download the v3.1.1 module template and look at the changes.

Hi @buaziz

Please remove yarn.lock and package-lock.json files and run the yarn install command again. The ngcc error will probably be resolved. If you still encounter this error, add the below script to the scripts of package.json.

"compile:ivy": "...",
"ngcc": "ngcc" // add this

How to publish a package to the NPM

Build your package with the below command:

yarn ng build <place here your package name in angular.json> --prod

After the building, you will see the output folder in the dist folder.

Open dist/your-package-name folder via terminal.

Run the npm login command and enter the username and password.

Then run the npm publish command.

Hi @gexiaoxu

You can add requireHttps: false property to the oAuthConfig object but if your backend running on HTTP, you can not use the authorization code flow. Please try adding the requireHttps property, let me know if the code flow is working.

If it doesn't work, update the oAuthConfig as shown below:

  oAuthConfig: {
    issuer: 'http://www.hd-auth.cn:44318',
    clientId: 'AuthServer_App',
    dummyClientSecret: 'place client secret here',
    scope: 'AuthServer',
    requireHttps: false,
  },

Hi @jackmcelhinney

Actually, you do not need the provide ScrollBarHelper and other services. Did you add the NgxDatatableModule to imports array of your module?

I can't reproduce the problem.

If you still have problems, can you explain the replication steps in detail with us?

Hi @edelivery

You can patch the "Administration" route as shown below:

import { RoutesService } from '@abp/ng.core';
import { Component } from '@angular/core';
import { eThemeSharedRouteNames } from '@abp/ng.theme.shared';

@Component(/* component metadata */)
export class AppComponent {
  constructor(private routes: RoutesService) {
    this.routes.patch(eThemeSharedRouteNames.Administration, { invisible: true });
  }
}

See the Modifying the Menu document for more information.

I have fixed some problems. You can see the PR. The problem will probably be fixed in v3.1.

Thanks for reporting 🙂