User Activities - jfistelmann

Lepton X public site mobile view issues #4736

one year ago Answer

Thanks. Can you share the LeptonxDemoApp project? liming.ma@volosoft.com

Uhm. As described this is your demo project without a single change.

You can get it by executing abp get-source Volo.Abp.LeptonXTheme.Pro --version 2.1.0 But if it helps you, I'll send it to you

Lepton X public site mobile view issues #4736

one year ago Answer

I just started the demo app from the leptonx project. Same issue applies.

please share the steps I will try to reproduce it. Thanks

Sure,

First get source of LeptonXTheme.Pro

abp get-source Volo.Abp.LeptonXTheme.Pro --version 2.1.0

Replace $(abpVersion) with 7.1.0 in all csproj files. Have no process for that, so I just open vs code and do some good old find and replace magic.

Next step is to start docker.

After that, run tye with .\demo\run-app.ps1 -setup

Little note here: You have

try {
        dotnet tool install -g Microsoft.Tye --prerelease
    }
    catch {
        { 1:dotnet tool update -g Microsoft.Tye --prerelease }
    }

You only need dotnet tool update - it will automatically install a package if it is not there.

Alternatively, you may start things directly from within visual studio (I had to, because tye has thrown some weird issues which I have to look into)

Now wait until stuff has started.

Now go to https://localhost:44360/

Change to mobile view thing and tadaaa

Lepton X public site mobile view issues #4736

one year ago Answer

I just started the demo app from the leptonx project. Same issue applies.

See Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX.Themes.LeptonX.Components.SideMenu.MobileNavbar.MobileNavbarViewComponent

Lepton X public site mobile view issues #4736

one year ago Answer

when you navigate to the URL, what happens?

well, as expected a 404. Because the link is not built to end and displaying it is wrong in the first place.

This opens when I click on the image:

The real question is: Why does it think that I am authorized when I'm not? Because that is leading to this behavior.

Lepton X public site mobile view issues #4736

one year ago Answer

Updated to 7.1.0 and LeptonX 2.1.0 today. Issues still apply

MVC public site: How to keep selected menu item #4634

one year ago Answer

hi

Can you share your public site project? liming.ma@volosoft.com?

sure, I'll prepare everything for that.

MVC public site: How to keep selected menu item #4634

one year ago Answer

hi

What is the theme you are using?

Did you add the below code to your index page?

@{ 
    // replace the bloew localization keys with yours 
    PageLayout.Content.Title = L["Applications"].Value; 
    PageLayout.Content.BreadCrumb.Add(L["Menu:OpenIddict"].Value); 
    PageLayout.Content.MenuItemName = OpenIddictProMenus.Applications; 
}

Hey maliming :)

I am using lepton theme. App is still running with IdentityServer. Putting the code into index.cshtml leads to this: Does not know of PageLayout (I think it is supposed to be a property or something?)

LeptonX Blazor Server issues #4621

one year ago Answer

Hi,Issue 2 and Issue 3 are known issues and will be solved in the next version.

I'm creating internal issues for Issue 1 and Issue 4.

Can you please provide which LeptonX version are you using?

Hey enisn,

thank you very much :)

We are on Version 2.0.2

Frequent HTTP 500 when restoring packages during CI Builds #4308

2 years ago Answer

Can't even update cli. Wanted to create a new solution but blocked. dotnet tool update -g Volo.Abp.Suite --add-source https://nuget.abp.io/MYPRIVATEKEY/v3/index.json runs for around 5 mins and then throws errors at me

ABP-LIC-0013 and ABP-LIC-0023 #4126

2 years ago Answer

❯ abp new AbpDebugTest -t app-pro -u blazor -d ef -o AbpDebugTest -dbms SQLite
[21:56:54 INF] ABP CLI (https://abp.io)
[21:56:54 INF] Version 6.0.1 (Stable)
[21:56:55 INF] Creating your project...
[21:56:55 INF] Project name: AbpDebugTest
[21:56:55 INF] Template: app-pro
[21:56:55 INF] Database provider: EntityFrameworkCore
[21:56:55 INF] DBMS: SQLite
[21:56:55 INF] UI Framework: Blazor
[21:56:55 INF] Output folder: C:\Repos\test\AbpDebugTest
[21:56:56 INF] Using cached template: app-pro, version: 6.0.1
[21:56:56 INF] Theme: LeptonX
[21:56:56 INF] Theme Style: System
[21:56:57 INF] Check out the documents at https://docs.abp.io/en/commercial/latest
[21:56:57 INF] 'AbpDebugTest' has been successfully created to 'C:\Repos\test\AbpDebugTest'
[21:56:57 INF] Creating initial migrations...
[21:57:09 INF] Initial migrations are created.
[21:57:09 INF] Installing client-side packages...
[21:57:10 INF] Found 1 projects.
[21:57:10 INF] C:\Repos\test\AbpDebugTest\src\AbpDebugTest.HttpApi.Host
[21:57:10 INF] Running Yarn on C:\Repos\test\AbpDebugTest\src\AbpDebugTest.HttpApi.Host
yarn install v1.22.19
info No lockfile found.
[1/4] Resolving packages...
warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > glob-watcher > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > gulp-cli > matchdep > micromatch > snapdragon > source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > gulp-cli > matchdep > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > gulp-cli > matchdep > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning @volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/aspnetcore.mvc.ui > gulp > gulp-cli > matchdep > micromatch > snapdragon > source-map-resolve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "@volo/abp.aspnetcore.mvc.ui.theme.leptonx > @volo/abp.aspnetcore.mvc.ui.theme.commercial > @abp/aspnetcore.mvc.ui.theme.shared > @abp/bootstrap > bootstrap@5.2.3" has unmet peer dependency "@popperjs/core@^2.11.6".
[4/4] Building fresh packages...
success Saved lockfile.
Done in 32.57s.
[21:57:43 INF] Generating bundles for Blazor Wasm...
Building....:  (1/1)C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Blazor\AbpDebugTest.Blazor.csproj
Executing...: dotnet build C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Blazor\AbpDebugTest.Blazor.csproj
MSBuild version 17.4.0+18d5aef85 for .NET
  Determining projects to restore...
  Restored C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Application.Contracts\AbpDebugTest.Application.Contracts.csproj (in 1.38 sec).
  Restored C:\Repos\test\AbpDebugTest\src\AbpDebugTest.HttpApi.Client\AbpDebugTest.HttpApi.Client.csproj (in 2.24 sec).
  Restored C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Blazor\AbpDebugTest.Blazor.csproj (in 10.74 sec).
  1 of 4 projects are up-to-date for restore.
  AbpDebugTest.Domain.Shared -> C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Domain.Shared\bin\Debug\netstandard2.0\AbpDebugTest.Domain.Shared.dll
  AbpDebugTest.Application.Contracts -> C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Application.Contracts\bin\Debug\netstandard2.0\AbpDebugTest.Application.Contracts.dll
  AbpDebugTest.HttpApi.Client -> C:\Repos\test\AbpDebugTest\src\AbpDebugTest.HttpApi.Client\bin\Debug\netstandard2.0\AbpDebugTest.HttpApi.Client.dll
  AbpDebugTest.Blazor -> C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Blazor\bin\Debug\net6.0\AbpDebugTest.Blazor.dll
  AbpDebugTest.Blazor (Blazor output) -> C:\Repos\test\AbpDebugTest\src\AbpDebugTest.Blazor\bin\Debug\net6.0\wwwroot

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:16.54
[21:58:04 INF] Generating style bundle...
[21:58:04 INF] Style bundle has been generated successfully.
[21:58:04 INF] Generating script bundle...
[21:58:05 INF] Script bundle has been generated successfully.
[21:58:05 INF] Script and style references in the index.html file have been updated.

After that I opened the solution and started the dbmigrator.

[21:59:17 INF] Started database migrations...
[21:59:17 INF] Migrating schema for host database...
[21:59:19 INF] Executing host database seed...
[21:59:22 INF] Successfully completed host database migrations.
[21:59:22 INF] Successfully completed all database migrations.
[21:59:22 INF] You can safely end this process...

C:\Repos\test\AbpDebugTest\src\AbpDebugTest.DbMigrator\bin\Debug\net6.0\AbpDebugTest.DbMigrator.exe (process 64260) exited with code 0.
To automatically close the console when debugging stops, enable Tools->Options->Debugging->Automatically close the console when debugging stops.
Press any key to close this window . . .

The license issue does not appear anymore.

Tested abp suite again. It also does not show the error anymore. Everything seems to be fine now (I did not change anything).

Thank you for whatever you did there :D

Activities of "jfistelmann"