Activities of "jfistelmann"

Hey,

sorry for the delay,

Here's a suggestion on how you can approach this:

First of all, how does style selection work?

If I take a look at a running site - we have a cookie named lpx_loaded-css:

If I then take this string and search for it in the leptonx source code I can see that there is a LeptonXStyleProvider.

And if I perform a search on where this is used, I can see this:

Let's take a look at the SideMenuLayout for example:

We can see that the LeptonXStyleProvider is used to determine the name of the css files to load. We can also see, that the LeptonXStyleProvider does not inherit from an interface which we could override to perform our own logic.

What you need to do is:

1. Create your own LeptonXStyleProvider with your desired logic
2. Override the Layout-Pages and replace the LeptonXStyleProvider with your own implementation

Please let me know if that helps you.

Kind regards Jack

In addition to malimings answer, these resources here may be helpful:

ABP Framework Entity Framework Core

PostgreSQL ILIKE

Hey,

the pull request has been merged. The changes will be included in the next version.

kind regards Jack

Hey,

Most of the issues have already been addressed. The translations for the settings module can be found here:

https://github.com/abpframework/abp/blob/dev/modules/setting-management/src/Volo.Abp.SettingManagement.Domain.Shared/Volo/Abp/SettingManagement/Localization/Resources/AbpSettingManagement/tr.json

I created a PR for şifre -> Şifre. https://github.com/abpframework/abp/pull/17035

Related Issue in Github: https://github.com/abpframework/abp/issues/16956

QA 5278 also has this issue

@jfistelmann  Thanks for feedback.

What about the other issue ?

I recommend that we track the AbpWindowService issue here: https://support.abp.io/QA/Questions/5298/Compile-error-in-version-73-Preview as it only concentrates on this specific error.

I'll add a comment there to reference this issue back.

Hey,

this seems to be more of a DevExpress issue than an ABP issue.

I've done some research based on what you described and hopefully this here helps you: https://docs.devexpress.com/Blazor/403737/components/grid/bind-to-data#large-data-server-mode-sources

https://supportcenter.devexpress.com/ticket/details/t1104088/dxgrid-custom-data-binding-events-in-blazor

kind regards Jack

Also you don't have any option to create free angular template because it use the template name with commercial version, and the only option you have to logout your account useing abp logout to create the free one

abp new MyProject -u angular -dbms SQLite --separate-identity-server --preview 
 
It should be (for example ) angular-pro for commercial version  
abp new MyProject -u angular-pro -dbms SQLite --separate-identity-server --preview 

Hey,

though maybe a bit irritating, you can specify that with the template parameter:

Community: (-t | --template -> app)

abp new MyProject -t app -u angular -dbms SQLite

Sample output:

ABP CLI 7.2.2
Creating your project...
Project name: MyProject
Template: app
DBMS: SQLite
UI Framework: Angular
Output folder: C:\Repos\abp\support\QA5278
Using cached template: app, version: 7.2.2
Theme: LeptonXLite
Check out the documents at https://docs.abp.io/en/abp/latest/Startup-Templates/Application

Commercial: (-t | --template -> app-pro) *default if logged in as commercial user

abp new MyProject -t app-pro -u angular -dbms SQLite

Sample output:

ABP CLI 7.2.2
Creating your project...
Project name: MyProject
Template: app-pro
DBMS: SQLite
UI Framework: Angular
Output folder: C:\Repos\abp\support\qa5278-pro
Using cached template: app-pro, version: 7.2.2
Theme: LeptonX
Theme Style: System
Check out the documents at https://docs.abp.io/en/commercial/latest

Something's off here:

First log is from API Host and it's searching the openid configuration on https://localhost:44378/.well-known/openid-configuration - so port 44378

The second log comes from Auth Server and it has lines like this: 2023-06-12 17:08:39.433 +03:00 [INF] Request starting HTTP/1.1 GET https://localhost:44335/.well-known/openid-configuration - -

And Auth Server returns responses like this:

2023-06-12 17:08:42.869 +03:00 [INF] The response was successfully returned as a JSON document: {
  "issuer": "https://localhost:44335/",
  "authorization_endpoint": "https://localhost:44335/connect/authorize",
  "token_endpoint": "https://localhost:44335/connect/token",
  "introspection_endpoint": "https://localhost:44335/connect/introspect",
  "end_session_endpoint": "https://localhost:44335/connect/logout",
  "revocation_endpoint": "https://localhost:44335/connect/revocat",
  "userinfo_endpoint": "https://localhost:44335/connect/userinfo",
  "device_authorization_endpoint": "https://localhost:44335/device",
  "jwks_uri": "https://localhost:44335/.well-known/jwks",
  "grant_types_supported": [
    "authorization_code",
    "implicit",
    "password",
    "client_credentials",
    "refresh_token",
    "urn:ietf:params:oauth:grant-type:device_code",
    "LinkLogin",
    "Impersonation"
  ],
  "response_types_supported": [
    "code",
    "code id_token",
    "code id_token token",
    "code token",
    "id_token",
    "id_token token",
    "token",
    "none"
  ],
  "response_modes_supported": [
    "form_post",
    "fragment",
    "query"
  ],
  "scopes_supported": [
    "openid",
    "offline_access",
    "email",
    "profile",
    "phone",
    "roles",
    "address",
    "Pbys"
  ],
  "claims_supported": [
    "aud",
    "exp",
    "iat",
    "iss",
    "sub"
  ],
  "id_token_signing_alg_values_supported": [
    "RS256"
  ],
  "code_challenge_methods_supported": [
    "S256"
  ],
  "subject_types_supported": [
    "public"
  ],
  "token_endpoint_auth_methods_supported": [
    "client_secret_basic",
    "client_secret_post"
  ],
  "introspection_endpoint_auth_methods_supported": [
    "client_secret_basic",
    "client_secret_post"
  ],
  "revocation_endpoint_auth_methods_supported": [
    "client_secret_basic",
    "client_secret_post"
  ],
  "claims_parameter_supported": false,
  "request_parameter_supported": false,
  "request_uri_parameter_supported": false,
  "authorization_response_iss_parameter_supported": true
}.

May it be that your auth server runs under port 44335 and that your api host has something like this in it's appsettings.json:

"AuthServer": {
    "Authority": "https://localhost:44378",
    ...
  },

If yes, change it to

"AuthServer": {
    "Authority": "https://localhost:44335",
    ...
  },

It's also strange that the auth server also has those errors with redis.

If above does not help, can you share the code?

Kind regards Jack