We've fixed the problem, it should be working as expected. If your problem still persists, please don't hesitate to write me back. Or if fixed feel free to close the question.
Best Regards.
Hi, currently we are facing some problems with our NuGet server. We are working on it. I'll inform you when it's fixed.
@EngincanV will there be a v6 release for this fix ?
Hi, you can update your LeptonX package versions to 2.0.0
, it was released yesterday and includes the fix for your problem.
thanks, you can ask @maliming for the example project ( its an almost empty project, generated by abp suite 6.0 ) - have sent it to his email
We've reproduced the problem and will fix it within the new release. Thanks again for reporting.
Hi, thanks for reporting. I will test and create an internal issue for this.
It seems to happen to Blazor but it works great with MVC (a note if you decide to switch to another UI)
Yes, it works for other UI types.
Hi, ABP does not provide any UI or monitoring service for RabbitMQ Logs. There are great third-party tools for these purposes. You can check the Elastic Agent for instance: https://docs.elastic.co/en/integrations/rabbitmq . It collects and parses logs from RabbitMQ servers with Elastic Agent (APM). .
Hi, we have an open internal issue in the backlog for this feature (#5335). However, we haven't prioritized it yet. In meantime, if the modal UI type is the only possible option for you, you can either implement it yourself or use another UI (if it's possible).
I am not sure if this disabling
AutoValidate
is really safe when releasing to production? but for now it works. It seems like there is a problem with the X-CSRF token?
Hi, as you mentioned it's not good to disable the auto anti-forgery token system. Did you change the header name from the AntiforgeryOptions
?
Please read the Angular UI section of XSRF documentation to learn more.
An error has occurred! Http failure response for https://my-azure-site.azurewebsites.net/api/identity/settings: 0 Unknown Error
All the
GET
requests are working fine. Any idea why it fails when doingPOST
/PUT
requests?
Hi, there are two possible reasons for this problem. First, ensure in your IIS Server POST and PUT requests are not restricted and second, you might want to consider removing "WebDAV publishing".
See https://stackoverflow.com/a/13259689/10477283 for possible solutions to your problem.