-
Notifications
You must be signed in to change notification settings - Fork 32
Symfony CMF StaticContent show all child blocks in PHPCTRee? #97
Comments
You have to look at your SonataDoctrinePhpcrAdmin configuration: sonata_doctrine_phpcr_admin:
document_tree:
Doctrine\ODM\PHPCR\Document\Generic:
valid_children:
- all
Symfony\Cmf\Bundle\ContentBundle\Doctrine\Phpcr\StaticContent:
valid_children:
- all
# ... This sets the |
I have tried it both ways -- no luck. It wont display those child blocks. It only displays blocks inside the additionalInfoBlock container block. First I tried....
Then I tried this too....
I don't think this affects the display of the children in the actual visual tree itself. You can see this is the situation even in the hosted demo @ http://cmf.liip.ch/en/admin/dashboard It is the tree that wont show them -- those blocks are actually there when you query for them. |
And with the config, you configure the tree that shows them. But I know too less about the Sonata Admin integration to help you further, sorry. |
closing in favor of symfony-cmf/tree-browser-bundle#57 |
Does anybody know how I can make all child blocks show up on the CMF Tree in the Sonata Admin for the StaticContent class? The way our system uses the Symfony\Cmf\Bundle\ContentBundle\Doctrine\Phpcr\StaticContent class is to just use it as a content document that we can attach other blocks to. I thought that was the purpose of the ContentBundle. Instead only blocks inside of this additionalInfoBlock container block appear in the tree. Unless I am doing something wrong.
I have looked at
Symfony/Cmf/Bundle/ContentBundle/Resources/config/doctrine-model/StaticContent.phpcr.xml:
There has to be way to get all the child blocks show. I just dont want to start hacking the PHPCRTree class to do this. Do I extend StaticContent and hopefully it will show all children? How do I go about this if that is the answer. Or is there another setting.
See this image below of what I can see in jackrabbitexplorer vs what is in the CMF Tree in the Sonata admin
The text was updated successfully, but these errors were encountered: