Chapters

7 Chapters | 36:14 |

01

How to Upgrade to Symfony 2.8

3:02
02

Upgrading to the Symfony 3.0 Directory Structure

13:36
03

Fix Deprecation Warnings from Bundles

4:31
04

Deprecation Fixing Tools

2:56
05

Fix My Deprecations

5:08
06

Upgrade Outdated Libraries!

2:57
07

Upgrading to Symfony 3!

4:04

> Symfony 2 > How to Upgrade to Symfony 2.8, then 3.0!

Buy Access to Course Buy Access

01.

How to Upgrade to Symfony 2.8

|

Autoplay

Next Chapter

Login or Register to check out the script

13 Comments

Sort By

Login or Register to join the conversation

Christopher M. 7 years ago

Hello,

I am getting this first error. I am trying to update my current symfony app 2.6 to 2.8 (dont judge me! lol)

> Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap
Cannot load Zend OPcache - it was already loaded

|

sadikoff Christopher M. 7 years ago edited

Hi Christopher M.

Which php version do you use and have you enabled opcache extension?

Cheers!

|

Christopher M. sadikoff 7 years ago

I am currently using php 7.1 and I don’t think I have enable opcache extension

|

sadikoff Christopher M. 7 years ago edited

Hey Christopher M.

Sorry for late answer, could you please provide more info, like output of php -v
And check for loaded extension, probably there is some php misconfiguration.

Cheers!

|

Christopher M. sadikoff 7 years ago

I was able to move from that error, but i am not getting this.

symfony FatalThrowableError in app_dev.php line 25:

|

MolloKhan SFCASTS Christopher M. 7 years ago edited

Hey Christopher M.

I left you some questions in your other thread

|

Skylar 7 years ago

Hello, After the update, Cache:clear fails with [RuntimeException] merge() expects a normalized config array. I am assuming it means that it does not like a config file. How do I find out which one?

|

Skylar Skylar 7 years ago edited

So I found the culprit. For swiftmailer my config.yml has this:


# Swiftmailer Configuration
swiftmailer:
    transport: "%mailer_transport%"
    host:      "%mailer_host%"
    username:  "%mailer_user%"
    password:  "%mailer_password%"
    auth_mode: "%mailer_auth_mode%"
    port:      "%mailer_port%"
    encryption: "%mailer_encryption%"
#    spool:     { type: memory }
    logging:  true
    stream_options:
        ssl:
            allow_self_signed: true
            verify_peer: false
            verify_peer_name: false```


but my config_dev.yml has this:

swiftmailer:

spool:     { type: memory }
stream_options:
    ssl:
        allow_self_signed: true
        verify_peer: false
        verify_peer_name: false
        cafile: "C:\\php7\\cacert.pem"


Notice the extra line for the "cafile" that is not in the config.yml.  

Why should this make a difference?

|

weaverryan SFCASTS Skylar 7 years ago edited

Hey Skylar!

Fascinating! I've never heard of this - I think you stumbled upon an edge case in Symfony's config system that probably doesn't quite work as well as it should. Here's an issue about it: https://github.com/symfony/symfony/issues/17436

So basically, this usually works - the keys are all merged together just fine. The difference is that, for most of the config keys, there is a Configuration file that determines literally every valid key that is allowed - https://github.com/symfony/swiftmailer-bundle/blob/master/DependencyInjection/Configuration.php. However, this ssl key is a bit special - you're allowed to pass any array with any keys you want - https://github.com/symfony/swiftmailer-bundle/blob/a9b8d20b86eda7c52f6b8b5c2f7877dec9f013e4/DependencyInjection/Configuration.php#L103-L105 - and when you have THAT situation... apparently the arrays cannot be merged unless they all have the same keys. I know - super weird.

So, ideally you can work around it by, for example, setting cafile: null or something similar in your main config.yml... but that could have side effects. If you can't find a work around - let me know - there is always a work around ;).

Cheers!

|

Rajaona F. 8 years ago

Fatal error: Uncaught TypeError: Return value of Doctrine\Common\Annotations\AnnotationRegistry::registerLoader() must be an instance of Doctrine\Common\Annotations\void, none returned in /home/ywoume/www/upgrade/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationRegistry.php on line 117

i use php7.1

|

MolloKhan SFCASTS Rajaona F. 8 years ago edited

Hey Rajaona F.

Could you tell us more information about that error.
What were you doing when it ocurred?

Cheers!

|

Rajaona F. MolloKhan 8 years ago

i have this error then i upgrade to symfony 2.8 when i do : composer update symfony/symfony --with-dependencies , when the vendor is installed i have this error when i refresh my broswer

|

MolloKhan SFCASTS Rajaona F. 8 years ago

Hmm, interesting, which version of `doctrine-bundle` are you using? Try using 1.6
And make sure you are really running in PHP 7.1, that error is related to PHP 7.0

Cheers

|

Symfony 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.3.9",
        "ext-pdo_sqlite": "*",
        "doctrine/doctrine-bundle": "~1.5", // 1.6.3
        "doctrine/doctrine-fixtures-bundle": "~2.2", // 2.3.0
        "doctrine/orm": "~2.4", // v2.5.4
        "erusev/parsedown": "~1.5", // 1.6.0
        "ezyang/htmlpurifier": "~4.7", // v4.7.0
        "incenteev/composer-parameter-handler": "~2.1", // v2.1.2
        "ircmaxell/password-compat": "~1.0", // v1.0.4
        "knplabs/knp-paginator-bundle": "~2.4", // 2.5.3
        "leafo/scssphp": "~0.1.5", // v0.1.10
        "patchwork/jsqueeze": "~1.0", // v1.0.7
        "sensio/distribution-bundle": "^5.0", // v5.0.7
        "sensio/framework-extra-bundle": "~3.0", // v3.0.16
        "symfony/assetic-bundle": "~2.8", // v2.8.0
        "symfony/monolog-bundle": "~2.7", // 2.11.1
        "symfony/swiftmailer-bundle": "~2.3", // v2.3.11
        "symfony/symfony": "3.0.*", // v3.0.9
        "twig/extensions": "~1.2" // v1.3.0
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0" // v3.0.7
    }
}

Next Chapter