Internal Dev issue, accidental log-off method triggered mid processing which cleared AbpUserTokens access token
Here is the code but I'm not sure how helpful it will be, its generally the same concept you have
html:
<div [busyIf]="!ContentLoaded">
<span>
<app-mycomponent></app-mycomponent>
</span>
</div>
ts:
ContentLoaded = false;
constructor(
injector: Injector,
) {
super(injector);
}
ngOnInit(): void {
}
myLoadingMethod($event) {
this.ContentLoaded = $event;
}
}
that component was a visual div in tab on a modal
<tab heading="{{'Content' | localize}}">
<div class="tab-class" *ngIf="active">
<content-loaded-area></content-loaded-area>
</div>
</tab>
The code you have should spin the div. From what you are describing its treating the whole area as the div. I would try cutting the entire area in 4 and add loading to just 1 to see how it reacts and maybe it will show you why its not reacting correctly Maybe even try adding a solid border around your div and seeing if its going past the area you expect it to be in
<div [busyIf]="loading">
<div class="row align-items-center" *ngIf="excelData">
<dx-tree-list id="excelData" class="excelData" [dataSource]="excelData.Children"
itemsExpr="Children" dataStructure="tree" [showRowLines]="true" [showBorders]="true"
[allowColumnResizing]="true" [columnMinWidth]="100" [columnAutoWidth]="true"
(onRowPrepared)="onRowUpdated($event)" (onCellPrepared)="onCellPrepared($event)"
(onRowExpanding)="onRowExpanding($event)" (onRowCollapsing)="onRowCollapsing($event)"
[customizeColumns]="customizeColumns">
<dxo-sorting mode="none">
</dxo-sorting>
<dxi-column dataField="Name" caption="reportName" [width]="400">
</dxi-column>
<dxi-column dataField="GLCode" caption="GLCode">
</dxi-column>
</dx-tree-list>
</div>
</div>
<div class="div-green">box 2</div>
<div class="div-red">box 3</div>
<div class="div-blue">box 4</div>
........
div-green {
background-color: lightgrey;
width: 300px;
border: 15px solid green;
padding: 50px;
margin: 20px;
}
div-red {
background-color: lightgrey;
width: 300px;
border: 15px solid red;
padding: 50px;
margin: 20px;
}
div-blue {
background-color: lightgrey;
width: 300px;
border: 15px solid blue;
padding: 50px;
margin: 20px;
}
Can you try to reverse that order?
Like this:
<div class="row align-items-center" *ngIf="excelData">
<div [busyIf]="loading">
<dx-tree-list id="excelData" class="excelData" [dataSource]="excelData.Children"
...
Also, I think the busy-if.directive.ts takes care of the spinnerService show/hide, I didnt need to add it to any of my custom components to get the loading spinner - I only used [busyIf]
[busyIf]
works exactly how you are describing it, add it to a div and add a state bool to trigger on/off/finished-loading-data
In the ASPNETZero source code I believe all the tables and dashboard widgets have code you can try to replicate
I would recommend trying to put a very clearly defined div inside of a div container and checking your process again to see if it triggers the whole page again - or trying to copy the code from a widget and seeing if that helps identify the issue
https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Deployment-Angular-Publish-IIS
When you click the button, what does the network show and what does the local log show? Log location should be: \src\myCompany.Web.Host\App_Data\Logs{here}
https://docs.aspnetzero.com/en/common/latest/Version-Updating https://github.com/aspnetzero/aspnet-zero-core
your app looks never hits the API from what the network is showing, can you check contents of: assets/appconfig.production.json make sure remoteServiceBaseUrl and appBaseUrl are pointing to the right URLs
Also, your app looks like it returns Content-Type: text/html for a JSON file instead of content-type: application/json
On IIS, did you convert the API as an Application?
When you say "The ASP.NET Core website works fine." can you elaborate? Are you able to connect to the remote swagger page from outside of the deployment server?
Also, what version of the application are you using?
And finally, can you check \App_Data\Logs\{log file} can see what it says in there when you get this error?
Here was the original issue: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at (Reason: CORS request did not succeed).
We revisited this and found that Cisco locks ports outside of generic ports - if anyone needs help with this please review:
https://www.cisco.com/c/en/us/support/docs/security/web-security-appliance/117933-qa-csc-00.html
use this site to help you test open ports: http://portquiz.net