i update my Project Abp version form 9.3.2 to 10.1.0 after updating i have issue with Faq Widget it cant render and show this error
and every this fine its work before updating version
[Widget Type="Faq" groupName="Client" sectionName="Faq" ]
i add widget like this and my groupName is Client and section Name is Faq
2 Answer(s)
-
0
In ABP 10.x the FAQ widget parameters are
groupNameandsectionName. Your dynamic widget usage is passingsectionName, but the docs example shows a mismatch (name = "Development"). This typically results in the widget endpoint failing and the UI showing “This part of content couldn’t be loaded.” after the upgrade.Fix your widget invocation by using
sectionName(notsectionName="Faq"with an old/incorrect parameter name mapping likename), and ensure the values match an existing FAQ Group + Section in CMS Kit:If you use the Dynamic Widget tag helper:
[Widget Type="Faq" groupName="Client" sectionName="Faq"]If you render it directly (recommended to verify quickly):
@await Component.InvokeAsync( typeof(FaqViewComponent), new { groupName = "Client", sectionName = "Faq" } )After changing it, restart the app and hard refresh the page. The widget content is loaded via an internal widget endpoint; if that endpoint throws due to parameter mismatch, you’ll only see the generic “couldn’t be loaded” message on the UI.
If it still fails after this change, the issue is no longer the parameters; it will be a server-side exception inside the widget endpoint. In that case, check the server logs for the request that serves the widget content (it will show the real exception).
- https://abp.io/docs/latest/modules/cms-kit-pro/faq
- https://abp.io/docs/latest/framework/ui/mvc-razor-pages/widgets
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
[AI-Bot] said:
In ABP 10.x the FAQ widget parameters are
groupNameandsectionName. Your dynamic widget usage is passingsectionName, but the docs example shows a mismatch (name = "Development"). This typically results in the widget endpoint failing and the UI showing “This part of content couldn’t be loaded.” after the upgrade.Fix your widget invocation by using
sectionName(notsectionName="Faq"with an old/incorrect parameter name mapping likename), and ensure the values match an existing FAQ Group + Section in CMS Kit:If you use the Dynamic Widget tag helper:
[Widget Type="Faq" groupName="Client" sectionName="Faq"]If you render it directly (recommended to verify quickly):
@await Component.InvokeAsync( typeof(FaqViewComponent), new { groupName = "Client", sectionName = "Faq" } )After changing it, restart the app and hard refresh the page. The widget content is loaded via an internal widget endpoint; if that endpoint throws due to parameter mismatch, you’ll only see the generic “couldn’t be loaded” message on the UI.
If it still fails after this change, the issue is no longer the parameters; it will be a server-side exception inside the widget endpoint. In that case, check the server logs for the request that serves the widget content (it will show the real exception).
- https://abp.io/docs/latest/modules/cms-kit-pro/faq
- https://abp.io/docs/latest/framework/ui/mvc-razor-pages/widgets
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
@await Component.InvokeAsync( typeof(FaqViewComponent), new { groupName = "Client", sectionName = "Faq" } ) when i use like this i throw this exception DependencyResolutionException: None of the constructors found on type 'Volo.CmsKit.Pro.Web.Pages.Public.Shared.Components.Faqs.FaqViewComponent' can be invoked with the available services and parameters: Cannot resolve parameter 'Volo.CmsKit.Public.Faqs.IFaqGroupPublicAppService faqGroupPublicAppService' of constructor 'Void .ctor(Volo.CmsKit.Public.Faqs.IFaqSectionPublicAppService, Volo.CmsKit.Public.Faqs.IFaqGroupPublicAppService)'