-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in cms listing page in the administration #16
Comments
I attempted to reproduce the error but was unable to do so using Shopware 6.6.9.0, plugin version 4.2.0, and the Chrome browser. Are you perhaps using Shopware 6.5 with an older version of the plugin? |
@7underlines you need to use the table view, not the grid view for the translation to be called, I'm getting the same issue on 6.6.9.0 and plugin version 4.2.0 the cms-aware flag seems to not catch because entities are apparently supposed to start with ce_ or custom_entity_, I don't think I've ever seen a plugin do that.. but that's stopping the page type from being registered here |
I am using Shopware 6.6.9.0 with Plugin Version 4.2.0 and the table view like @phit mentioned. |
Thanks for providing the additional information. I can now reproduce the error. It seems there must be at least one blog entry for it to be triggered. |
After opening the shopping experiences listing page (
/#/sw/cms/index
) in the administration I get the following error:After that my shopware administration stops working until I reload the browser window.
Possible fix:
The error is caused by the new
blog_detail
page type introduced by this plugin. The listing page tries to translate the name of the cms pages and fails forblog_detail
because the name and type ist not known to shopware.My temporary fix is registering the new page type when the administration loads.
Further informations:
cms-aware
flag in Shopware 6.5.x which should auto add custom cms-pages to the cmsPageTypeService in the administration.blog_detail
to a type known by shopware)The text was updated successfully, but these errors were encountered: