@hrod761
you could consider using this to hide/show elements on your page depending on the Tenant:
*ngIf="appSession.tenancyName.toLowerCase() == 'xxx'
@murat.yuceer - theres a setting in the Admin for a fixed foooter.
Go to:
Administration>Visual Settings and the Footer tab
Hi @ismcagdas, also experiencing this. Do you have a fix?
Hi Team,
The OPENID users will have the token/user ID in the username which usually a long string. We have to change all the places from username to full name. There will be some users have the same full names in the sytem. Is that any chance that OPENID users store the token or userID somewhere else so that they can have an unique and proper username?
RE: ASP.NET Core + Angular
Are there any plans for the future to unify all the stylesheets under a single build system?
Currently the LESS files (and some .css files) are compiled using the Angular CLI.......while the metronic stylesheets use Gulp.
Why was it necessary create two separate systems? Could the metronic files not also use the Angular CLI?
Its not particularly intuitive because the Angular CLI works on save whereas gulp requires the command gulp buildDev
would also like to hear the answer to this. I had HMR working reasonably on earlier version of aspnetzero, but haven't been able to get it working on the latest version.
Are there any demo links of V8 up for us to view?
Hi @ismcagdas, thanks. what was the reason to go with NgxBootstrap instead of NgBootstrap (if the latter is already included in Metronic) ?
We are using ASP.NET CORE Angular..
A question relating to Metronic -
Are we supposed to be able to use any of the compnents on the Metronic demos/docs pages, and it will automatically work within ASP.NET ZERO?
From what I can see this is not the case. The styles seem to be more or less working OK, but not the functionality (the JS)
Seems that some of the Metronic componets use jQuery... but jQuery is not included in the Angular version of ASP.NET ZERO, correct?
Can you please confirm exactly what we can or can't use.
Hi,
I've got a workaround, but thought I would highlight an issue I've found.
I've got a client written that is logging into the .NET API and is trying to use the refresh tokens. But I've found a bug where the refresh token can be used to get a new access token, but the access token won't work.
I've found the problem in the template code and it only happens when the user belongs to a tenant.
The refresh token code is using the current session's tenant. So for example the access token has a user identity of (tenant ID: null, user ID: 82) instead of (tenant ID: 7, user ID: 82).
The work around ws to send the tenant ID in the headers on the request to refresh the token. But this is still a bug since the API should handle that. And if by design the tenant ID should be sent, the refresh token endpoint should error rather than return an access token that doesn't work.
This isn't stopping us anymore. But thought it should be raised to ease of use of future users.