Do not use IIS, directly in the folder of the publisher.
Execute dotnet MyCompanyName.AbpZeroTemplate.Web.Mvc.dll
or MyCompanyName.AbpZeroTemplate.Web.Host.dll
See how the results are.
Are you talking about Extending Localization Sources? https://aspnetboilerplate.com/Pages/Documents/Localization#extending-localization-sources
I think the application's runtime environment error caused the wrong connection string to be read. The wrong environment settings were used. appsettings.json appsettings.Production.json
https://github.com/maliming/abplocalization/blob/master/src/QA.Web.Mvc/Controllers/HomeController.cs#L17
https://github.com/maliming/abplocalization/blob/master/src/QA.Core/Localization/SourceFiles/Abp/Abp.xml#L4
https://github.com/maliming/abplocalization/blob/master/src/QA.Core/Localization/QALocalizationConfigurer.cs#L23
Access this url: http://localhost:62114/home/test
{
"result": null,
"targetUrl": null,
"success": false,
"error": {
"code": 0,
"message": "Hello You Need Login!",
"details": null,
"validationErrors": null
},
"unAuthorizedRequest": true,
"__abp": true
}
@alexanderpilhar If I use a template project(https://github.com/aspnetboilerplate/module-zero-core-template) to show you the extension's built-in localization, what do you think?
I believe this is a problem with firefox.
https://stackoverflow.com/questions/699941/handle-ajax-error-when-a-user-clicks-refresh/18170879 https://bugzilla.mozilla.org/show_bug.cgi?id=486511 https://forum.jquery.com/topic/what-s-the-proper-way-to-deal-with-ajax-error-because-of-page-reload
If your users use Firefox more You may be able to make some special judgments on the Firefox browser here, not showing this error. https://github.com/aspnetboilerplate/aspnetboilerplate/blob/dev/src/Abp.Web.Resources/Abp/Framework/scripts/libs/abp.jquery.js#L100
@kalidarscope Please share the full code and values such as result.creatioN_TIME and result.expirY_DATE.
Track https://github.com/aspnetzero/aspnet-zero-core/issues/2306
Please confirm your application environment for production. Is the local test successful?
Execute the dotnet yourwel.dll test in the release folder to see