I am installing Symfony 2.3.x and sonata admin bundle, but when it is installed, the admin panel is shown in a wrong way (see the screen capture).
This problem has appeared when I run composer update command. Before that, my sonata admin panel looks nice.
Any idea? Could be a problem with any template of sonata? (Icons from sonata not appear).
Thank you!
It appears that there is a dependency between the dev-master versions of SonataCoreBundle and SonataAdminBundle that breaks if any older version is used between either. Here is a GitHub issue regarding the problem
The solution is to use the ~2.3 Composer version tag of SonataAdminBundle instead of dev-master, or run composer require sonata-project/core-bundle dev-master so that it exceeds the minimum requirement of ~2.2 for SonataCoreBundle in the composer.json file of SonataAdminBundle. Then run composer update to fix all of the dependencies.
Related
I'm looking to integrate the FOSElasticaBundle into my symfony 3 project. Currently this bundle doesn't support symfony 3. I was ondering what I could do to still implement it?
Seems is not yet tagged a valid release for using it via packagist. See this issue on github.
The release dev-master / 3.2.x-dev seems already compliant with symfony3.
I successfully installed this bundle on a symfony3 installation with the command :
composer require friendsofsymfony/elastica-bundle dev-master
Hope this help
I want to start a new project on symfony 2.4.3 and I need the functionality of the fosuserbundle. My Problem: On their github (https://github.com/FriendsOfSymfony/FOSUserBundle) in the documentation they recommand 2.1.x.
Here , a user says you should install fosuserbundle manually but this question is for symfony 2.3.
Can I use the bundle on my version of symfony? If yes, can I install it with composer? If no, are there any similar bundles that I can use instead?
Thanks in advance
This version of the bundle requires Symfony 2.1+. If you are using Symfony 2.0.x, please use the 1.2.x releases of the bundle.
From their docs. 2.1+ means, 2.1, 2.2, 2.3, 2.4, ... 2.n So 2.3 is perfectly valid.
Moreover, Composer handles the dependencies for you, so just require it and run composer update, if the Symfony version is not supported the command fails and you know it doesn't support your current version, if it succeeds everything is working perfectly.
I've installed Sentry on Laravel 4 through composer following these instructions but the vendor/cartalyst/sentry/src folder is empty. Why is that? Does anyone know? I didn't get any errors during composer update.
Thanks a lot!
Sentry didn't install properly because I also used the fzaninotto/faker package in my app. I guess they just don't work well together. After removing fzaninotto/faker package from my composer.json file and re-running composer update it worked perfectly.
I'm updating my app from Symfony2.0 to Symfony2.1.
When I run composer install I receive a fatal exception about JMS/SerializerBundle not being found when it reaches the generating autoload files step. I think cache:clear is causing this.
I've added it to composer.json:
"jms/serializer-bundle": "dev-master",
And in my appKernel:
new JMS\SerializerBundle\JMSSerializerBundle($this),
I basically followed the steps.
I also can not find the file in the vendor directory. The composer stated 'Nothing to install or update' though. It does not matter if I put in a version number. Think this is the same for the stof doctrine extension.
How do I resolve this?
Setting symfony to 2.1.0 allowed me to install the extra repositories.
I am try to install Sonata Admin Bundle on WAMP . To begin, add the dependent bundles to the vendor/bundles directory. Add the following lines to the file deps.
[SonatajQueryBundle]
git=http://github.com/sonata-project/SonatajQueryBundle.git
target=/bundles/Sonata/jQueryBundle
[SonataUserBundle]
git=http://github.com/sonata-project/SonataUserBundle.git
target=/bundles/Sonata/UserBundle
[SonataAdminBundle]
git=http://github.com/sonata-project/SonataAdminBundle.git
target=/bundles/Sonata/AdminBundle
[KnpMenuBundle]
git=https://github.com/KnpLabs/KnpMenuBundle.git
target=/bundles/Knp/Bundle/MenuBundle
[KnpMenu]
git=https://github.com/KnpLabs/KnpMenu.git
target=/knp/menu
[SonataDoctrineORMAdminBundle]
git=http://github.com/sonata-project/SonataDoctrineORMAdminBundle.git
target=/bundles/Sonata/DoctrineORMAdminBundle
Now problem in install these bundle in vendor. I run this commend php bin/vendors install but it's show Try to run ./bin/vendors install --reinstall
Is there something wrong with my Bundle. I am really not sure what to do about this. Please help.
I appreciate all the help.
Thanks!
You might be using incompatible versions of Symfony and SonataAdminBundle.
Also, you might be missing SonataBlockBundle and SonataCacheBundle which are required with the latest versions of SonataAdminBundle (have a look at the SonataAdmin installation reference). Symfony, SonataAdminBundle and Doctrine2 only work together in specific combinations.
Suggestion: Try the relevant instructions in this tutorial, or better yet, clone this repository and configure it according to the instructions.
You'll have a working install, to which you can then add your existing bundle.