Atividades de "paul.harriman"

Responder

Just making sure case doesn't get closed for inactivity

Responder

Mahmut,

Any update on this?

hi,

I just want to make sure I understand what you said above. Are you saying that if our solution was an MVC/Blazor solution, this wouldn't be a problem? The slide would exist?

IE, because we are using an angular and .netcore solution, we do not get the slide.

maliming,

Part of the reason we adjusted the lifetimes above was to make it easier to test. I have some of the code changes locally as I'm developing. I have the scope removed, but not the lifetime adjustments.

It appears that when we just remove the offline_access, we will get logged out after ~1 hour. Meaning even if you're in the middle of something, you get brought back to the screen where you need to enter your credentials. So the time does not "slide". Is there a way to "slide" (meaning while the user is active, they stay logged in, but when they go idle for 1 hour, they get logged out)?

Responder

Mahmut, Maybe this will help Here's a brand new 7.1 abp site with angular (this is the latest, our current app is a version behind, but the problem still exists), no mobile and added stubbed file for alerts. Unfortunately, I did not do a git init before adding alerts. The changes are:

  • adding the folder and contents mobile-navbar
  • adding replaceableComponent in app.component
  • adding modulefor mobile-navbar in app.module The solution was cleaned and node_modules, .angular files were removed https://github.com/Dovernh/ABP71.MobileNavbar
Responder

Mahmut,

Thanks for the quick reply. Here's more info on my issue. This is my customized template that I have (below). I have already commented out the code you described. I want what is there before login Home, Settings, Red button, EMPTY, Alerts and then after login I want Admin to be on the toolbar. Home, Settings, Red button, Admin, Alerts

The problem that is after login, my custom code is not executed (there are breakpoints in the ngOnInit, before login the breakpoints are hit). The original mobile nav bar code is. If I click the big red button, you can see the breakpoints being hit and then the mobile navbar displays as I want

<div class="lpx-mobile-navbar-container">
  <div class="lpx-mobile-navbar">
    <ul class="lpx-mobile-nav-tabs">
      <!-- <li class="lpx-mobile-nav-tab"
        *ngFor="let tab of navTabs"
        [routerLink]="tab.link"
        [routerLinkActive]="tab.link ? 'selected' : ''"
        [routerLinkActiveOptions]="{ exact: tab.link === '/' }"
        [class.selected]="tab.expanded">
        <a class="lpx-mobile-nav-item">
          <lpx-icon class="menu-item-icon"
            *ngIf="tab.icon"
            [iconClass]="tab.icon"></lpx-icon>
          <span class="mobile-item-text">
            {{ tab.mobileMenuText || tab.text | toObservable | async }}
          </span>
        </a>
      </li> -->

      <li class="lpx-mobile-nav-tab"
        (click)="toggleMenu('settings', settingsMenuItems)"
        [class.selected]="activeMenu === 'settings'">
        <a class="lpx-mobile-nav-item">
          <lpx-icon class="menu-item-icon"
            iconClass="fas fa-home"></lpx-icon>
          <span class="mobile-item-text">
            {{ "Home" | lpxTranslate | async }}
          </span>
        </a>
      </li>

      <li class="lpx-mobile-nav-tab"
        (click)="toggleMenu('settings', settingsMenuItems)"
        [class.selected]="activeMenu === 'settings'">
        <a class="lpx-mobile-nav-item">
          <lpx-icon class="menu-item-icon"
            iconClass="gearConnected"></lpx-icon>
          <!-- TODO: PROVIDE API -->
          <span class="mobile-item-text">{{
            settingsTitle | lpxTranslate | async
            }}</span>
        </a>
      </li>

      <li class="lpx-mobile-nav-tab menu-toggle">
        <a class="lpx-mobile-hamburger"
          [ngClass]="toggleClass"
          (click)="toggleNavbarMenu()">
          <span class="hamburger-icon"
            aria-hidden="true"
            [class.lpx-mobile-menu-opn]="activeMenu === 'navbar'">
            <span class="icon-part"></span>
            <span class="icon-part"></span>
            <span class="icon-part"></span>
            <span class="icon-part"></span>
            <span class="icon-part"></span>
            <span class="icon-part"></span>
          </span>
        </a>
      </li>

      <li class="lpx-mobile-nav-tab"
        (click)="profileMenuItems && toggleMenu('profile', profileMenuItems)"
        [class.selected]="activeMenu === 'profile'">
        <a class="lpx-mobile-nav-item">
          <lpx-avatar [avatar]="userProfile.avatar"></lpx-avatar>
          <span class="mobile-item-text">{{ userProfile.userName }}</span>
        </a>
      </li>

      <li class="lpx-mobile-nav-tab"
        (click)="profileMenuItems">
        <a class="lpx-mobile-nav-item otised-alerts">
          <otised-notification-icon />
          <div class="mobile-item-text">{{
            'Alerts' | lpxTranslate | async
            }}</div>
        </a>
      </li>
    </ul>
  </div>

  <div class="lpx-mobile-menu"
    [hidden]="!menuVisible">
    <div class="lpx-logo-container"><lpx-brand-logo></lpx-brand-logo></div>
    <lpx-navbar-routes [navbarItems]="selectedMenuItems"
      (routeClick)="closeMenu()">
    </lpx-navbar-routes>
  </div>
</div>

it also will not solve the issue for those who use the angular client

I tried to update lepton-x to 2.0. looks like it wants ABP7, but it builds. i run into an error saying it can't find font.bundle.css

localhost/:1

   Refused to apply style from 'http://localhost:4200/font-bundle.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

I am experiencing the same issue. I want to create a new angular, ef core solution for version 5.3.3. I uninstalled abp suite and abp cli to make sure I started out clean, then re-installed. I get the same issue.

My real goal is to try and install LeptonX Lite. I tried doing it to an existing solution and I get error messages it requires angular 14.2. I do not believe 5.3.3 supports angular 14. I do not want to update my current solution to abp 6, at this time

abp suite remove Open %USERPROFILE%.dotnet\tools directory, delete abp.exe. Then open .store folder and delete volo.abp.cli folder.

dotnet tool install Volo.Abp.Cli -g --version 5.3.3 abp suite install --version 5.3.3

[08:17:52 ERR] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null }

[08:17:52 ERR] Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.Cli.ProjectBuilding.Templates.RemoveUnnecessaryPortsStep.RemoveUnnecessaryDbMigratorClients(ProjectBuildContext context) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\Templates\RemoveUnnecessaryPortsStep.cs:line 56 at Volo.Abp.Cli.ProjectBuilding.Templates.RemoveUnnecessaryPortsStep.Execute(ProjectBuildContext context) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\Templates\RemoveUnnecessaryPortsStep.cs:line 15 at Volo.Abp.Cli.ProjectBuilding.Building.ProjectBuildPipeline.Execute() in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\Building\ProjectBuildPipeline.cs:line 19 at Volo.Abp.Cli.ProjectBuilding.TemplateProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\TemplateProjectBuilder.cs:line 120 at Volo.Abp.Cli.Commands.NewCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\NewCommand.cs:line 73 at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SolutionService.CreateSolutionAsync(CreateSolutionModel input) at lambda_method1705(Closure , Object ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.

trying with just the cli, shows almost the same, except it mentions trying to use cached template for 6.0.0. This solution is for 5.3.3 abp new AbpLeptonX -t app -u angular --mobile none --database-provider ef -csf

[08:57:40 INF] ABP CLI (https://abp.io) [08:57:40 INF] Version 5.3.3 (Stable) [08:57:41 WRN] ABP CLI has a newer stable version 6.0.0, please update to get the latest features and fixes. [08:57:41 WRN] [08:57:41 WRN] Update Command: [08:57:41 WRN] dotnet tool update -g Volo.Abp.Cli [08:57:41 WRN] [08:57:41 INF] Creating your project... [08:57:41 INF] Project name: AbpLeptonX [08:57:41 INF] Template: app [08:57:41 INF] Database provider: EntityFrameworkCore [08:57:41 INF] UI Framework: Angular [08:57:41 INF] Output folder: C:\Dev\AbpLeptonX [08:57:43 INF] Using cached template: app, version: 6.0.0 [08:57:44 ERR] Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.Cli.ProjectBuilding.Templates.RemoveUnnecessaryPortsStep.RemoveUnnecessaryDbMigratorClients(ProjectBuildContext context) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\Templates\RemoveUnnecessaryPortsStep.cs:line 56 at Volo.Abp.Cli.ProjectBuilding.Templates.RemoveUnnecessaryPortsStep.Execute(ProjectBuildContext context) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\Templates\RemoveUnnecessaryPortsStep.cs:line 15 at Volo.Abp.Cli.ProjectBuilding.Building.ProjectBuildPipeline.Execute() in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\Building\ProjectBuildPipeline.cs:line 19 at Volo.Abp.Cli.ProjectBuilding.TemplateProjectBuilder.BuildAsync(ProjectBuildArgs args) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectBuilding\TemplateProjectBuilder.cs:line 120 at Volo.Abp.Cli.Commands.NewCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\NewCommand.cs:line 73 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 161 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 69

Responder

that worked w/ both Tenant and User. :)

Responder

sent u an email

Mostrando 11 até 20 de 46 registros
Made with ❤️ on ABP v8.2.0-preview Updated on março 25, 2024, 15:11