Our custom CMS utilizes TreeBundle from Symfony2 CMF. When deploying to a production server, bin/vendors install failed because apparently the whole bundle does no longer exist - at least in GitHub. The Symfony2 CMF homepage still mentions the bundle, the link just leads to a 404 page.
Is the bundle gone for good? What happened to it? Is there a Symfony 2.0 compatible replacement for it or should we just include the bundle in our own repository?
This bundle was refactored into the TreeBrowserBundle and the old bundle removed after a while. See here for the discussion about that: https://groups.google.com/forum/?fromgroups=#!searchin/symfony-cmf-devs/treebundle/symfony-cmf-devs/k7nm-XtXW8Q/kgZpaOJN1x8J
If you can update your project, then just do that and drop the reference to TreeBundle. Otherwise the easiest would indeed be to include it in your own repository.
We assumed that the early adopters of the CMF frequently update, and thus we removed this repository after a few months. Sorry about that. We will be more careful with backwards compatibility the more stable we get.
Related
I have started with symfony 3.2 project, then changed version in composer to 2.8 (which is long term support).
Problem is that folders structure still remains 3.2 project. Is there any way to change (not manually) folders structure to 2.8?
Of course you can downgrade. You might choose the old Symfony2 directory structure (deprecated) or keeping the current Symfony3 structure.
In either ways, please take a look at How to Override Symfony's Directory Structure.
Using the Symfony3 directory structure
If you choose to use the Symfony3 structure, it's easy as following up this article about upgrading from Symfony2 to Symfony3's directory structure.
Using the Symfony2 directory structure
First you'll have to rename and move some files (like var/cache/, var/logs/, etc.). Afterwards you'll have to change the autoloading file in app/autoload.php (formerly var/autoload.php which you must move too).
Basically it's the same in reverse order like upgrading from Symfony2 to Symfony3 (mentioned above).
Please be aware that Symfony 3.4 (next LTS) will be released in November 2017, so in my opinion it's not worth to downgrade, and then re-upgrade. Upgrading from 3.2 to 3.4 will be small and fast, Upgrading from 2.8 to 3.4 could be much more to do ...
I would like to install Symfony CMF into an existing Symfony2 project. I just want editing a few pages with CMF.
I am using this documentation : http://symfony.com/doc/master/cmf/book/installation.html ; just for new installation ...
did you run into a specific issue?
anyway you might also find this link useful http://symfony.com/doc/master/cmf/cookbook/editions/cmf_core.html
I'm writing an app using Laravel 4.2. This time, I needed some extra functionality and I decided to create a package. I used the workbench functionality as described in Laravel's docs.
Currently (and locally), the package is very small but it suits my app very well. I don't think this should be published to the community because it is still very green. I'll put a few hours into it when I finish with my app but I can't right now.
Now, I know the workbench/ directory is not to be pushed to production. Then, how do I use my package on production?
So far, I heard I have to push the package to GitHub (which I already did), and then publish it on Packagist. But I feel that publishing the script as is won't be helpful to others and might as well harm those in search of this functionality (like me a few days ago) on this so under developed package.
Is there a way to add my package to my app's composer.json and have it installed without publishing it to the community while it's under development?
What you are looking for is "private repository". Inside your composer.json file you can define an object repositories where you can define other locations to search for this repository
Detailed explanation can be found on Autoload bitbucket repository. The same principal is true for github.
I had a working Symfony2 application that uses several Sonata bundles (core, admin, doctrine-orm-admin, block). I have just pushed some revised code, and did a Composer update. Now, whilst app_dev.php seems to work fine, when I access the production version via app.php, I get an error;
Failed opening required 'vendor/sonata-project/easy-extends-bundle/Sonata/EasyExtendsBundle/SonataEasyExtendsBundle.php'
Looking in the vendors directory, the SonataEasyExtendsBundle.php is there, but it is in vendor/sonata-project/easy-extends-bundle, rather than in vendor/sonata-project/easy-extends-bundle/Sonata/EasyExtendsBundle/
Any ideas?
After much puzzling - it turned out to the APC cache. Clearing that resolved the issue. Doh.
I am trying to update my project written in Symfony 2.0 into Symfony 2.2.
Moving source codes into 2.2 project ended with config.yml and security.yml incompatibiliy.
Is there way how to properly migrate Symfony 2.0 project into Symfony 2.2?
It better to wait until Symfony 2.3 before migrating. It will be released somewhere in May. It's the first LTS (Long Time Support) release, meaning that it's maintained for three years. So: You don't have to worry about BC breaks for 3 years!
For the migrating of Symfony 2.0 to 2.3: There is nothing you can do. Read the UPGRADE-*.md files (which are stored in the root of the symfony/symfony package) and fix anything that is in their in your code. Every BC break that's important for normal users will be put in those UPGRADE files.
If you can't solve it after the fixing everything in the UPGRADE files, you should take a look at the CHANGELOG.md files in the root of the package (e.g. the symfony/security package). Try to find something that is changed and cause your code to break.
Finally, if you don't get your script working, there are a lot of active Symfony2 users who are waiting to help you. Take a look at the community page and find your place to ask questions.