The code in your website differs from the source code I have in my project.
If you took the time to debug the javascript error, you would see that there is a syntax error in your minified js.
window.paypal.request.addHeaderBuilder(()=>{"X-XSRF-TOKEN":abp.security.antiForgery.getToken()});
That is not valid arrow syntax.
It should be:
window.paypal.request.addHeaderBuilder(()=>{return {"X-XSRF-TOKEN":abp.security.antiForgery.getToken()}});
Javascript files are not minified in development, which might explain why you don't have the issue locally.
I can't find the _PayPal.min.js file in the solution, so I'm not sure how it's being generated.
Most of those updates are for .Net Core 2.0 I suspect, and should not be updated.
The better approach, while painful, would be to download the new 4.5 version that includes the .net core 2.0 upgrade, and apply your customizations to that.
We are currently going through that process our self.
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/380">https://github.com/aspnetzero/aspnet-ze ... issues/380</a>
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/380">https://github.com/aspnetzero/aspnet-ze ... issues/380</a>
There is an open issue in github tracking it. They said they will begin investigation soon, and it will be included with 4.6 or 4.7, most likely.
You can find the issue here:
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/432">https://github.com/aspnetzero/aspnet-ze ... issues/432</a>
<cite>Mdonogma: </cite>
<cite>ismcagdas: </cite> Hi @Mdonogma,
I assume you want to create a similar page the one you have shared a link. If so, we didn't include profile.css into AspNet Zero solution. Adding it to your page might solve your problem. If it does not, you can compare included css files and add missing ones to your page.
Thanks.
Why do t you just include all the Medtronic .css files. That way developers won't have to log requests like this. My assumption is since your documentation says Medtronic them added is that all the relevance metronic .css and other artefacts are built in.
What else is missing?
Because Metronic is an incredibly bloated front end framework, and if they included everything despite not needing it, everyone would end up with an application that loaded more slowly and took up more memory than was necessary.
Part of their goal in provided Asp.Net Zero as a template is to provide a starting point for a multi-tenant SaaS application that follows best practices from the ground up.
Including unnecessary bloat is not best practice.
They do, however, provide you with the entire source of the Metronic UI, so you are free to incorporate any part of it that they have not included. You can find the link here:
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/releases">https://github.com/aspnetzero/aspnet-zero/releases</a>
The latest version of Metronic that is incorporated in Asp.Net Zero is 4.7.5, and can be found in the download section of Asp.Net Zero Release 4.1.
It's frustrating, for sure, but SignalR was pretty clear about it.
The good news is that it looks like SignalR Core progress is moving along smoothly, so we should have Asp.Net Core 2.1 (and SignalR core) along with it by early next year.
Are you using the MVC core version with full framework?
If so, you cannot use web sockets. SignalR 2.0 is not fully compatible with Asp.Net Core. This has to do with the web sockets middleware. There are some various hacks that MIGHT get it to work for you, but they are messy.
You can find more about the issue here:
[https://github.com/aspnet/SignalR/issues/435])
Scott Brady wrote up a pretty good overview of how IdentityServer4 can be set up for a more advanced configuration here:
[https://www.scottbrady91.com/Identity-Server/Getting-Started-with-IdentityServer-4])
Do you envision this being a 4.6 release, or being included with 4.5?
