Open alexander-nitsche opened 1 year ago
Are you sure the existence of the Neos.Neos:Page Prototyp is the problem? As long as you don’t use it it should not be run and cause any issues.
im more confused by your Neos.Neos:ContentComponent in your custom view without nodes … you won’t need it and it might actually be a problem if you don’t have the context node defined.
Also do I see this correctly that you want to open Inside of the NeosUi iFrame your custom flow route? Isn’t this odd?
and does the view works if it’s not loaded in the iFrame but in a normal tab? - could you provide a screenshare?
btw I just realised that you will upset the ui if you’re navigating inside the iFrame to a page which is not a node document, but this is okay - as the backend is only meant for nodes… does this explain everything?
Is there an existing issue for this?
Current Behavior
In Neos 7.3 a custom controller with Fusion view and including the Neos core Fusion libraries via
breaks the Neos UI in that it is endlessly loading the orange line at the top.
Expected Behavior
It should be possible to implement a controller with Fusion view and using the core Fusion libraries comfortably with the above mentioned aggregation includes.
Steps To Reproduce
DistributionPackages/MyWebsite.Site/Configuration/Settings.yaml
DistributionPackages/MyWebsite.Site/Configuration/Policy.yaml
DistributionPackages/MyWebsite.Site/Configuration/Routes.yaml
DistributionPackages/MyWebsite.Site/Classes/Controller/Service/ArticlesController.php
DistributionPackages/MyWebsite.Site/Resources/Private/Fusion/Controller/ArticlesController.fusion
Environment
Anything else?
In-depth analysis revealed that
in Packages/Application/Neos.Neos/Resources/Private/Fusion/Prototypes/Page.fusion is responsible here and commenting it in fixes the endless loading.
A temporary fix is to replace the generic
with the specifically required Fusion files of the Neos.Neos package, e.g.
which hopefully do not include the Page.fusion :)