Hi there,
You can also use the ThemeManager to set the required Theme:
@inject IThemeManager ThemeManager
@{
Layout = ThemeManager.CurrentTheme.GetApplicationLayout();
//Or account layout
//Layout = ThemeManager.CurrentTheme.GetAccountLayout();
}
But as you found out setting the string to the Theme fully qualified inside your pages works too.
Kind regards
how did you disable it?
you need to disable the nullable feature for your application.contracts project or make the string props nullable.
Sure.
Here is the whole documentation for the static js proxies: https://docs.abp.io/en/abp/latest/UI/AspNetCore/Static-JavaScript-Proxies
so updating would be something like
abp generate-proxy -t js -u <yoururl>
this will generate the js file for the proxies. there should be already another file in your target project. that needs to be overriden by the new file.
if you use dynamic proxies please let me now. then most properly the app service is not added as auto controller in your target project and so that would explain why the app service is missing in js.
Did you update the client proxy js in the target project? Seems to me that the application you copied to does not have the js client for that particular app service.
Hi,
i assume you use Asp.Net Core MVC as frontend right? It could be that the namespace is not ready to the exact moment when you try to access it in the js file.
Would you mind sharing the index.js file so i can have a look?
Kind Regards Nico
As is see it from the logs there is a really strang behavior when the deletion endpoints get called:
Can you reproduce this behavior in debug mode? If so you can send me the project so i can deep dive into the project and look whats causing this.
E-Mail: kontakt@chrobyte.de
Could you provide logs once again now that the 405 is gone?
Also it would be good if you share the code of the page. I created a fresh project using with a test entity using abp suite and there is an error modal displayed and no redirections are made to the error page.
Another thing: did you override the default Error page?
It seems that the anti forergy validation failed due to the missing RequestVerificationToken header. Could you send a screenshot of the request headers the browser is sending to the api?
Also check if there is a cookie set named "XSRF-TOKEN".
Create (Post) and update (Put) and Get Work Fine
I just saw that you are hosting behind an IIS in the response headers. Please ensure that the IIS is configured correctly to allow the DELETE Http-Verb.
Do you use a reserve proxy like nginx or something else that might block delete requests currently?