Not sure bug or what ?
maity-kgz opened this issue · 10 comments
If you create from admin panel new publishable static page and create publishable menu-node and link to newly created static page (by changing link type to content) its never shown in menu.
Tested on 1.3 locally and on official sandbox.
you also need to create a route. but at least in the online demo at http://sandbox.cmf.symfony.com/en/admin/app/demoseocontent/cms/content/company/edit the route part seems to be broken. it does not even show routes for content that already exists and that has a route. i get no js error, so something else must be amiss.
if i create the route in the separate route admin and select that it points to a new content, that new content indeed shows up in the menu on the page. so it must be a problem with https://github.com/symfony-cmf/routing-bundle/blob/master/Admin/Extension/RouteReferrersExtension.php (or some edge case with sonata itself)
Thanx for your replay dbu. I figured out later that i must create route. But in first place the fact that existing static pages shows in menu "without routes" confused me.
We've had similar issues before: #316 These were related to Sonata. I'll try to look at this this evening.
@wouterj was sonata-project/SonataDoctrinePhpcrAdminBundle#397 related to this? do we need to update sonata admin in the sandbox?
in the online sandbox it still does not work, but when i try to add a route i now get "Fatal error: Call to undefined method Symfony\Component\Validator\Context\ExecutionContext::addViolationAt() in /app/vendor/doctrine/phpcr-bundle/Validator/Constraints/ValidPhpcrOdmValidator.php on line 64".
the fatal error is fixed in phpcr-bundle 1.3.4 but when trying to update the sandbox, i run into other problems, will try to fix those tonight.
hm, got myself confused bout that phpcr-bundle 1.3.4 upgrade, was able to upgrade now, see #334
As far as I can test things, it works perfectly after updating the dependencies ( #335 ). However, updating the dependencies brought in some new issues that we have to fix...
#335 is merged, but this bug still exists. I'll investigate this once again tomorrow.
Tried it again with the new sandbox and things work as expected now.