We've fixed the issue. It will be available with the next RC or final version.
With 4.3.0-rc.2, the CMS-Kit public page controller not registered, cannot visit a page by slug from public site.
The error logs as below:
2021-04-10 15:30:18.186 +08:00 [INF] Executing endpoint 'Volo.CmsKit.Public.Pages.PagesPublicController.FindBySlugAsync (Volo.CmsKit.Public.HttpApi)' 2021-04-10 15:30:18.201 +08:00 [INF] Route matched with {area = "cms-kit", action = "FindBySlug", controller = "PagesPublic", page = ""}. Executing controller action with signature System.Threading.Tasks.Task1[Volo.CmsKit.Public.Pages.PageDto] FindBySlugAsync(System.String) on controller Volo.CmsKit.Public.Pages.PagesPublicController (Volo.CmsKit.Public.HttpApi). 2021-04-10 15:30:18.264 +08:00 [ERR] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null }2021-04-10 15:30:18.265 +08:00 [ERR] The requested service 'Volo.CmsKit.Public.Pages.PagesPublicController' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency. Autofac.Core.Registration.ComponentNotRegisteredException: The requested service 'Volo.CmsKit.Public.Pages.PagesPublicController' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.`
We're not able to reproduce the issue. Can you give us some details regarding how you created the solution? CLI or Suite? Screenshot of the command or suite creation screen. Thanks
Hello @chofoza,
The error you're getting on step 2 isn't looking related to the ABP. You might want to try yarn and gulp commands before adding the CMS-Kit module. It looks like they're related to your development environment.
Regarding the setup process, please follow the steps on the CMS-Kit Module page.
After enabling both CMS Kit and CMS Kit Pro features, you need to create a migration and then run the DbMigrator. Can you please follow these steps and let us know if issues still exist?
