The idea is that you can restrict the content document type nodes to be possible to create or move them into a given subtree. Same use case for routes, menus, ...

after updating the sandbox, i get this error

HTTP 400: '[' not allowed in name 

the reason is probably that we fixed the query builder to itself add the [] around names with : in them and we probably still add them manually in the admin bundle somehwere. however, i did not find where...

the rest (tree, new, edit) all work, just the list is affected.

Resources:

https://github.com/symfony-cmf/TreeBundle

https://github.com/symfony-cmf/phpcrbrowser

See also symfony-cmf/symfony-cmf#88

i created a symfony-update branch in cmf-sandbox with the latest (as of 11.07.2012) symfony. there seems to be something in the form layer that breaks. i get an exception about object expected when i try to load an editing form that uses the tree widget (menu and simple page admins)

@uwej711 would be great if you can have a look at this...

Path is not absolute: cms/content/home/content/stage/col2

Is the documentation ready ?

I can generate the documentation for this bundle if you want. Just let me now.

Try this and make it work

There is an issue with how this bundle detects and changes on the fly some templates. I update the code on the Doctrine ORM, you might want to apply the same change.

sonata-project/SonataDoctrineORMAdminBundle@fb4d139

like used here https://github.com/symfony-cmf/ContentBundle/blob/master/Admin/StaticContentAdmin.php

this should probably be more of a hint and a link to the base sonata admin doc.

follow-up of #23

http://travis-ci.org/#!/sonata-project/SonataDoctrinePhpcrAdminBundle

likely the unit tests broke because some interface/class was changed and so the mock objects are no longer setup correctly.

expose the API for versioning:

• create new version
• see list of versions
• load old version
• restore content to an old version
• optionally completely delete an old version

To control what is currently published, we should maintain a separate tree. Publishing would copy the selected version from the editing tree to the publication tree. (Looking up a specific label on each request is an expensive overhead and error prone, and could mess up with search.). JCR-based CMS like magnolia even support copying the jcr subtree from one system to another, to support different servers for editing and publishing.

We probably need to fix versioned documents children mappings for this to be fully usable.

#93

/cc @lsmith77

Is it possible to filter out translation documents? For documents using the "child" translation strategy the child documents for each language are displayed in the tree, fe. phpcr_locale:en <not editable>.

Or maybe this should be more general, so you could configure for a tree what to display. Related to this is that for a select tree you would like to limit the tree to fe. only pages. for the field to select a parent page.

@saithis found that the type guesser does not know about nodename field (and probably other special fields) and not provide a reasonable type.
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/blob/master/Guesser/TypeGuesser.php

see also
symfony-cmf/cmf-sandbox#107

the query builder is now an odm one, no need to go to the phpcr level anymore

see doctrine/phpcr-odm#204

/cc @dantleech

I have a child annotation in my document, but no child is assigned (yet), but the method getDocumentChildren returns an array containing 'null' which leads to an exception in getChildren.

There should be a check for null in getDocumentChildren.

There is a second issue with that: the nodes are marked "not editable" since this are generated proxy classes not the real classes. The admin exists only for the real classes

travis tells:

PHP Fatal error:  Declaration of Mock_Admin_5b9e740d::setMenuFactory() must be compatible with that of Sonata\AdminBundle\Admin\AdminInterface::setMenuFactory() in /home/vagrant/.phpfarm/inst/php-5.3.8/pear/php/PHPUnit/Framework/MockObject/Generator.php(216) : eval()'d code on line 1

And make filters, forms, etc. work with right datatypes. At the moment evertyhing is a string to simplify things.

admin classes need the configureFormFields method. when i renamed the storage name for 'content' to 'body', but let the getter and setter at set/getContent, i noticed that i need to specify the type and before it was guessed. this should be documented a bit - and maybe there is even a way for me to specify the phpcr name to get the type from instead of the type itself?

protected function configureFormFields(FormMapper $formMapper)
{
    $formMapper
        ->with('General')
            ->add('path', 'text')
            ->add('title')
            ->add('name')
            ->add('content', 'text') // without 'text', the form can not be built if the node does not have a property $content
        ->end();
}

Hello,

I have updated the code to jQuery 1.7, some templates has been updated :

sonata-project/SonataDoctrineORMAdminBundle@4d768b4

The change fixes issues with recursive loop with event and html comment inside a javascript block.

reference to doc for reference collection http://symfony.com/doc/master/cmf/bundles/phpcr-odm.html#phpcr-odm-reference-collection and sonata-type-model (only works for references, not for children)

this widget is used to select a phpcr node by path.

• refactor to use a odm tree instead of the phpcr tree
• support specifying allowed jstree-node-types
• support reference properties, translating from document to a helpful string for the user and on storing back to the document.

this form widget could go into the phpcr-bundle to be available regardless of whether the adminbundle is used or not.

with jackrabbit we do not have the ability to generate a count efficiently for larger data sets. so we should make a simple flag in the base admin class to say that we expect a large dataset. in this case the paging should switch to just offering prev/next buttons.

Hello,

I just add a support for Audit/Versionning, I have started to add interfaces in the AdminBundle and the implementation in DoctrineORMAdminBundle. I am not sure if the interface can match the PHPCR requirements, can you please have a look the the following comments and provides any comments you might have.

Thanks.

• sonata-project/SonataAdminBundle@baa6cd0
• sonata-project/SonataDoctrineORMAdminBundle@f3eec64

In order to work with Symfony 2.2.0 (and new twig version), you should change the following line in /Resources/views/tree.html.twig for the block to work correctly ;

change

{% render 'sonata.admin.doctrine_phpcr.tree_controller:treeAction' with { 'root': id, 'selected': selected } %}

with

{% render( controller('sonata.admin.doctrine_phpcr.tree_controller:treeAction',{ 'root': id, 'selected': selected })) %}

Figure out if parameter binding works in PHPCR/Jackalope first

we have fixed the double slashes in the page urls, but it seems we still have the double slashes in the form action urls.

At the moment the admin class and controllers are tied to a specific kind of document.

In order to have a tree containing different types of documents we need a new controller for the tree view.

That controller should:

• Have RESTful routes for create, edit, delete, update nodes...
• Provide the right urls for CRUD
• Has routing that match what FOSJsRoutingBundle sends to the server

There is a tiny doc explaining how to activate the bundle, but we need docs explaining how to set up a working environment to try this out with the symfony-cmf sandbox, explain that this won't work with doctrine2 versions prior to this fix doctrine/orm#154

As the ORM does. Currently, when a empty text field is saved, the field gets populated with an empty string in the database.

I don't know what component is responsible of this behaviour.

doctrine/phpcr-odm@7a27bad adds createQueryBuilder to the phpcr-odm DocumentManager - this could be used by this bundle for better abstraction and less code:
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/blob/master/Builder/DatagridBuilder.php#L130

There should be a way of handling child documents in Node Form..

assuming you have a structure like this:

Articles
 - Article 1
 - Article 2
 -- Images
 --- Image 1
 --- Image 2
 - Article 3

It should be possible to identify those child-documents and render them as a list (or tree view?).
I don't hink that there should be something like a form for it.. it should just show the User that there are Subnode which can be edited too.

A lillte more visual: http://cl.ly/1M1s0p1R1n0r331a1M0d :)

on the menu items, we use two trees, one for the parent, the other for the linked content. since the last update, the parent tree is showing the content as well. the sonata admin class looks correct to me, but the rendered html configures the tree to look in /cms/content

the problem is visible for example on
http://cmf.lo/app_dev.php/de/admin/bundle/menu/menunode/cms/menu/main/edit

on the demo sandbox http://cmf.liip.ch/en/admin/bundle/menu/multilangmenuitem/cms/menu/main/edit it is still correct

@uwej711 not sure if your PR broke it - but whatever, do you think you can fix it?

ReferenceOne/ReferenceMany are field types. select target documents. Similar to #23 this needs an injected application specific strategy to determine what targets are valid.

Note that there is also the Referrers, which are the backlinks from referenced documents. We might display that for completeness, but editing is probably a bit weird (the info is only stored on the source document of the reference, never at the target. so to remove a referrer, you would actually edit the other document. might be useful from a user perspective though)

The ListBuilder now takes a list of template as arguments, the same thing will be done for the show actions.

sonata-project/SonataAdminBundle@a722dba
sonata-project/SonataDoctrineORMAdminBundle@8b4a687

An extra magic as been added in order to support localized data : date and numeric field

sonata-project/SonataIntlBundle@fd79e47

The bundle need to be altered in order to work with the last master of SonataAdminBundle.

Thanks

as of doctrine/phpcr-odm#218 we have inheritance in search queries, which results in mixed collections being shown.

ie. the MenuNode list now shows MultilangMenuNode nodes since the later extends from the former.

for the add button SonataAdminBundle already supports subcollections:
https://github.com/sonata-project/sandbox/blob/2.1/src/Sonata/Bundle/DemoBundle/Resources/config/admin.xml#L14

however SonataAdminBundle does not yet support dynamically choosing which edit form to load.

i think it would be kind of cool to be able to take this to the extreme by simply having a single list for any document. in a way this would be a competing or complementary interface to what we offer with the https://github.com/symfony-cmf/phpcrbrowser (which @danleech is working to replace with a Symfony2 implementation). at this point we would no longer really be talking about inheritance, but mixed collections. for such mixed collections we would likely need to offer a "search in any property" or something like that .. but that is another story.

/cc @rande @dbu

This also needs a way to inject application logic to decide what parents are to be proposed.

the tree currently displayes fully - we should have some way to show it minimized and expand it when activated.

additionally some sort of "livesearch" to quickly find the right child would be useful. see also doctrine/DoctrinePHPCRBundle#112 for autocomplete in the phpcr_odm_path type

Using a language switcher, you can edit all languages of a document: http://symfony.com/doc/master/cmf/tutorials/handling-multilang-documents.html

A cool feature would be to have language tabs to edit all languages without changing the request locale (which also changes the language of the user interface)

we should show the children documents of a document, also allowing to reorder children.

relates to #17 (editing children inline) which would be an extended case of this feature.

make sure the multivalue editing works out of the box (including the javascript to add/remove items). once implemented, also check that doctrine/DoctrinePHPCRBundle#111 works as expected.

see #87

There are situations where selecting a referenced document as described in #24 is not convenient for the user. Think of the content page that is referenced by a menu document and a route document. It would be good to enter all 3 documents in one interface.

#89
#91

and also explain how to edit things in an ajax overlay

/cc @elHornair

Hello,

You might want to apply the same patch to the DatagridBuilder class .

sonata-project/SonataDoctrineORMAdminBundle@c40d55a

Thomas

Ideally, we reach 100% conscious decision: that is, all code is either tested or has the phpunit comments that it does not make sense to test it.

When creating a new route or editing certain existing routes it is impossible to select the correct route path.

link

See this in action here:

http://cmf.liip.ch/admin/bundle/routingextra/route/cms/routes/en/projects/cmf/edit