`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
when installing Nginx on docker, logs bring this up.
any idea how i can acess the container using SSH to change those errors?
Related
I've installed sonata + symfony 4.4 on new clean empty project.
Did everything according to https://symfony.com/doc/current/bundles/SonataAdminBundle/getting_started/installation.html
and executed the recipes , composer adviced me to apply.
But on pristine setup I'm having a few deprecations like:
User Deprecated: The "sonata.twig.deprecated_template_extension"
service is deprecated since sonata-project/twig-extensions 1.4.
User Deprecated: The "sonata.deprecated_text.twig.extension" service
is deprecated since sonata-project/admin-bundle 3.70. You should stop
using it, as it will be removed in 4.0.
The child node "legacy_twig_text_extension" at path
"sonata_admin.options" is deprecated since sonata-project/admin-bundle
3.70 and will be removed in 4.0.
Is it ok? I don't have any legacy I've just set up compeltely new project?
Can I somehow avoid these deprecations or is it just an expected behavior and I have to get used to it?
User Deprecated: Parameter names will be made case sensitive in Symfony 4.0.
Using "httpprotocol" instead of "httpProtocol" is deprecated since Symfony 3.4.
I don't understand where this is coming from in my code. I am about to upgrade Symfony from 3.4 to 4, but this deprecation must be solved first. is httpprotocol just an example? I can not find that value in my code.
I had a parameter defined in the config.yml:
parameters:
locale: en
httpProtocol: http
and referenced in routes.yml
route:
schemes: ['%httpProtocol%']
I changed all of the httpProtocol parameters to http_protocol which seems to have solved the issue. The deprecation notice message was a bit misleading though.
I have tried to set up use_strict_mode for sessions but I get the following error
Unrecognized option "use_strict_mode" under "framework.session"
What is strange is that in the documentation for symfony 2.7 this option appears under framework.session, but at the end of the file in the full configuration reference it does not.
https://symfony.com/doc/2.7/reference/configuration/framework.html#use-strict-mode
https://symfony.com/doc/2.7/reference/configuration/framework.html#full-default-configuration
Is it maybe because this option was introduced in another version, 2.8 , 3.0 maybe? And there is a mistake in the docs?
I'm migrating symfony 2.6 app to the 3.0.4, I'm in a trouble with security.secure_random service, I was using it with dependency injection. Which is representing in security.xml
but I cannot see in 3.0.x I checked changelog every pixel of the project where it does go ? That I'm missing something ?
The class deprecated in 2.8 and removed in 3.0 in favour of the random_bytes function.
Essentialy the SecureRandomInterface had one nextBytes method, which behaves exactly as the PHP7 random_bytes function.
You can install https://github.com/paragonie/random_compat for forward compatibility
After upgrade of my project to symfony 2.8 I get the following error when I push the code to staging server.
[Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]
Unrecognized option "firewall_name" under "hwi_oauth"
When i remove firewall_name option then I get an error that the option is required.
If someone provide some insight will be much appreciated.
You get this error now because when You was updating Symfony rest of dependencies was updated also.
This option was renamed to firewall_names to support multiple firewalls in this commit: https://github.com/hwi/HWIOAuthBundle/commit/9bdbc089ddffede12a5b575a441c4e0fa2ee9dd7 and released as part of 0.4.0 version.
Now it's value must be array. Example:
hwi_oauth:
firewall_names: [secured_area]