Mixing
Read from parameters in Symfony 3.4 getParameter null
I can't read a parameter from parameters.yml in my controller.
I want to do this:
//My Controller
class ExampleController extends Controller
{
function someMethod($argument)
{
dump($this->getParameter('free_proxy'));die();
and in parameters.yml I got:
parameters:
free_proxy: "http://xxx:8080"
I get an error: Call to a member function getParameter() on null
I've tested some solutions like adding some services and using get and stuff but nothing works.
EDIT: also, I tried this:
services:
_defaults:
autowire: true
autoconfigure: true
public: false
bind:
$freeProxy: '%free_proxy%'
Then using:
$this->container->getParameter('free_proxy');
But I got an error: Unused binding "$freeProxy" in service...
symfony
asked Jan 2 at 15:47
pmirndpmirnd
79921133
|
show 5 more comments
I can't read a parameter from parameters.yml in my controller.
I want to do this:
//My Controller
class ExampleController extends Controller
{
function someMethod($argument)
{
dump($this->getParameter('free_proxy'));die();
and in parameters.yml I got:
parameters:
free_proxy: "http://xxx:8080"
I get an error: Call to a member function getParameter() on null
I've tested some solutions like adding some services and using get and stuff but nothing works.
EDIT: also, I tried this:
services:
_defaults:
autowire: true
autoconfigure: true
public: false
bind:
$freeProxy: '%free_proxy%'
Then using:
$this->container->getParameter('free_proxy');
But I got an error: Unused binding "$freeProxy" in service...
symfony
asked Jan 2 at 15:47
pmirndpmirnd
79921133
Things have changed a bit with the introduction of autowire. Read through here for several recommended approaches. Or else consult the container docs to see how to inject the container into your controller.
– Cerad
Jan 2 at 15:54
@Cerad I tried some solution like that. I don't get it, why so complicated. In Laravel is ENV.free_proxy and that's all. I've read different aproaches to to this for symonfy 3.4, for 3.3 and for above 2.8 (which is symfony 3.3 and 3.4 too)
– pmirnd
Jan 2 at 16:19
Many things seem complicated the first time you work through them but after awhile they become routine. Just bind $freeProxy to your value and then all you need to do is to name a variable $freeProxy in your action method. From a bigger point of view, injecting the complete container has always been considered to be a bit of an anti-pattern which was tolerated because it made life much simpler. Sort of like a rich but obnoxious uncle. But the fairly new autowire functionality has made eliminating the container more practical.
– Cerad
Jan 2 at 16:26
I might add that configuring and injecting services/parameters is one of the key cornerstones of Symfony. It's well worth taking the time to understand.
– Cerad
Jan 2 at 16:28
I'll edit my answer withservices.ymlfor more help, because it didn't work for me.
– pmirnd
Jan 2 at 16:39
|
show 5 more comments
I can't read a parameter from parameters.yml in my controller.
I want to do this:
//My Controller
class ExampleController extends Controller
{
function someMethod($argument)
{
dump($this->getParameter('free_proxy'));die();
and in parameters.yml I got:
parameters:
free_proxy: "http://xxx:8080"
I get an error: Call to a member function getParameter() on null
I've tested some solutions like adding some services and using get and stuff but nothing works.
EDIT: also, I tried this:
services:
_defaults:
autowire: true
autoconfigure: true
public: false
bind:
$freeProxy: '%free_proxy%'
Then using:
$this->container->getParameter('free_proxy');
But I got an error: Unused binding "$freeProxy" in service...
symfony
asked Jan 2 at 15:47
pmirndpmirnd
79921133
I can't read a parameter from parameters.yml in my controller.
I want to do this:
//My Controller
class ExampleController extends Controller
{
function someMethod($argument)
{
dump($this->getParameter('free_proxy'));die();
and in parameters.yml I got:
parameters:
free_proxy: "http://xxx:8080"
I get an error: Call to a member function getParameter() on null
I've tested some solutions like adding some services and using get and stuff but nothing works.
EDIT: also, I tried this:
services:
_defaults:
autowire: true
autoconfigure: true
public: false
bind:
$freeProxy: '%free_proxy%'
Then using:
$this->container->getParameter('free_proxy');
But I got an error: Unused binding "$freeProxy" in service...
symfony
symfony
asked Jan 2 at 15:47
pmirndpmirnd
79921133
asked Jan 2 at 15:47
pmirndpmirnd
79921133
edited Jan 2 at 16:44
pmirnd
asked Jan 2 at 15:47
pmirndpmirnd
79921133
asked Jan 2 at 15:47
pmirndpmirnd
79921133
asked Jan 2 at 15:47
pmirndpmirnd
79921133
79921133
Things have changed a bit with the introduction of autowire. Read through here for several recommended approaches. Or else consult the container docs to see how to inject the container into your controller.
– Cerad
Jan 2 at 15:54
@Cerad I tried some solution like that. I don't get it, why so complicated. In Laravel is ENV.free_proxy and that's all. I've read different aproaches to to this for symonfy 3.4, for 3.3 and for above 2.8 (which is symfony 3.3 and 3.4 too)
– pmirnd
Jan 2 at 16:19
Many things seem complicated the first time you work through them but after awhile they become routine. Just bind $freeProxy to your value and then all you need to do is to name a variable $freeProxy in your action method. From a bigger point of view, injecting the complete container has always been considered to be a bit of an anti-pattern which was tolerated because it made life much simpler. Sort of like a rich but obnoxious uncle. But the fairly new autowire functionality has made eliminating the container more practical.
– Cerad
Jan 2 at 16:26
I might add that configuring and injecting services/parameters is one of the key cornerstones of Symfony. It's well worth taking the time to understand.
– Cerad
Jan 2 at 16:28
I'll edit my answer withservices.ymlfor more help, because it didn't work for me.
– pmirnd
Jan 2 at 16:39
|
show 5 more comments
Things have changed a bit with the introduction of autowire. Read through here for several recommended approaches. Or else consult the container docs to see how to inject the container into your controller.
– Cerad
Jan 2 at 15:54
@Cerad I tried some solution like that. I don't get it, why so complicated. In Laravel is ENV.free_proxy and that's all. I've read different aproaches to to this for symonfy 3.4, for 3.3 and for above 2.8 (which is symfony 3.3 and 3.4 too)
– pmirnd
Jan 2 at 16:19
Many things seem complicated the first time you work through them but after awhile they become routine. Just bind $freeProxy to your value and then all you need to do is to name a variable $freeProxy in your action method. From a bigger point of view, injecting the complete container has always been considered to be a bit of an anti-pattern which was tolerated because it made life much simpler. Sort of like a rich but obnoxious uncle. But the fairly new autowire functionality has made eliminating the container more practical.
– Cerad
Jan 2 at 16:26
I might add that configuring and injecting services/parameters is one of the key cornerstones of Symfony. It's well worth taking the time to understand.
– Cerad
Jan 2 at 16:28
I'll edit my answer withservices.ymlfor more help, because it didn't work for me.
– pmirnd
Jan 2 at 16:39
Things have changed a bit with the introduction of autowire. Read through here for several recommended approaches. Or else consult the container docs to see how to inject the container into your controller.
– Cerad
Jan 2 at 15:54
Things have changed a bit with the introduction of autowire. Read through here for several recommended approaches. Or else consult the container docs to see how to inject the container into your controller.
– Cerad
Jan 2 at 15:54
@Cerad I tried some solution like that. I don't get it, why so complicated. In Laravel is ENV.free_proxy and that's all. I've read different aproaches to to this for symonfy 3.4, for 3.3 and for above 2.8 (which is symfony 3.3 and 3.4 too)
– pmirnd
Jan 2 at 16:19
@Cerad I tried some solution like that. I don't get it, why so complicated. In Laravel is ENV.free_proxy and that's all. I've read different aproaches to to this for symonfy 3.4, for 3.3 and for above 2.8 (which is symfony 3.3 and 3.4 too)
– pmirnd
Jan 2 at 16:19
Many things seem complicated the first time you work through them but after awhile they become routine. Just bind $freeProxy to your value and then all you need to do is to name a variable $freeProxy in your action method. From a bigger point of view, injecting the complete container has always been considered to be a bit of an anti-pattern which was tolerated because it made life much simpler. Sort of like a rich but obnoxious uncle. But the fairly new autowire functionality has made eliminating the container more practical.
– Cerad
Jan 2 at 16:26
Many things seem complicated the first time you work through them but after awhile they become routine. Just bind $freeProxy to your value and then all you need to do is to name a variable $freeProxy in your action method. From a bigger point of view, injecting the complete container has always been considered to be a bit of an anti-pattern which was tolerated because it made life much simpler. Sort of like a rich but obnoxious uncle. But the fairly new autowire functionality has made eliminating the container more practical.
– Cerad
Jan 2 at 16:26
I might add that configuring and injecting services/parameters is one of the key cornerstones of Symfony. It's well worth taking the time to understand.
– Cerad
Jan 2 at 16:28
I might add that configuring and injecting services/parameters is one of the key cornerstones of Symfony. It's well worth taking the time to understand.
– Cerad
Jan 2 at 16:28
I'll edit my answer with
services.yml for more help, because it didn't work for me.– pmirnd
Jan 2 at 16:39
I'll edit my answer with
services.yml for more help, because it didn't work for me.– pmirnd
Jan 2 at 16:39
|
show 5 more comments
2 Answers
2
active
oldest
votes
So there are two mysteries here. First is why is the container not being injected which in turn causes getParameter to fail. And second, why does bind generate that unused binding error.
You did not show your routing but I suspect that somewhere along the line you actually have:
$exampleController = new ExampleController();
If so then this explains why getParameter is failing. You really need to let Symfony create the controller based on the route. Otherwise the container is not injected and other controller magic is skipped.
I installed a fresh 3.4 app with the old directory structure and added a parameter
composer create-project symfony/framework-standard-edition s34
# app/config/parameters.yml
parameters:
free_proxy: "http://xxx:8080"
I then tweaked the default controller using the default route annotation:
class DefaultController extends Controller
{
/**
* @Route("/", name="homepage")
*/
public function indexAction(Request $request)
{
$freeProxy = $this->getParameter('free_proxy');
// replace this example code with whatever you need
return $this->render('default/index.html.twig', [
'base_dir' => realpath($this->getParameter('kernel.project_dir')).DIRECTORY_SEPARATOR.$freeProxy,
]);
}
}
And everything worked as expected. The Symfony request handler takes care of injecting the container and thus gives you access to the parameters. If you cannot get this working then please update your question with your routing information.
I then took a look at the bind issue. You really want to inject these parameters instead of pulling them. I updated services.yml
# app/config/services.yml
services:
bind:
$freeProxy: '%free_proxy%'
And started getting those unused binding errors. It turns out that bind does not work for action injection. Not really sure why. I don't use it much but I really would have expected that just adding $freeProxy to your action method would work. In any event, here is a working example of the proper way to do things.
class ExampleController extends Controller
{
private $freeProxy;
public function __construct($freeProxy)
{
$this->freeProxy = $freeProxy;
}
/**
* @Route("/example", name="example")
*/
function someMethod()
{
dump($this->freeProxy);
dump($this->getParameter('free_proxy'));die();
}
}
I then went to a fresh 4.2 project and tried action injection:
class IndexController extends AbstractController
{
public function index($freeProxy)
{
return new Response("Index $freeProxy");
}
}
Action injection works as expected for 4.2 but not 3.4. Constructor injection works fine in either version.
answered Jan 3 at 14:54
CeradCerad
36.1k76371
add a comment |
documentation show like this :
parameters.yml :
parameters:
mailer.transport: sendmail
to set :
$container->setParameter('mailer.transport', 'sendmail');
to get :
$container->getParameter('mailer.transport');
edited Jan 3 at 13:03
hrust
5261825
answered Jan 3 at 12:51
Aym2ricAym2ric
65
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54009230%2fread-from-parameters-in-symfony-3-4-getparameter-null%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
So there are two mysteries here. First is why is the container not being injected which in turn causes getParameter to fail. And second, why does bind generate that unused binding error.
You did not show your routing but I suspect that somewhere along the line you actually have:
$exampleController = new ExampleController();
If so then this explains why getParameter is failing. You really need to let Symfony create the controller based on the route. Otherwise the container is not injected and other controller magic is skipped.
I installed a fresh 3.4 app with the old directory structure and added a parameter
composer create-project symfony/framework-standard-edition s34
# app/config/parameters.yml
parameters:
free_proxy: "http://xxx:8080"
I then tweaked the default controller using the default route annotation:
class DefaultController extends Controller
{
/**
* @Route("/", name="homepage")
*/
public function indexAction(Request $request)
{
$freeProxy = $this->getParameter('free_proxy');
// replace this example code with whatever you need
return $this->render('default/index.html.twig', [
'base_dir' => realpath($this->getParameter('kernel.project_dir')).DIRECTORY_SEPARATOR.$freeProxy,
]);
}
}
And everything worked as expected. The Symfony request handler takes care of injecting the container and thus gives you access to the parameters. If you cannot get this working then please update your question with your routing information.
I then took a look at the bind issue. You really want to inject these parameters instead of pulling them. I updated services.yml
# app/config/services.yml
services:
bind:
$freeProxy: '%free_proxy%'
And started getting those unused binding errors. It turns out that bind does not work for action injection. Not really sure why. I don't use it much but I really would have expected that just adding $freeProxy to your action method would work. In any event, here is a working example of the proper way to do things.
class ExampleController extends Controller
{
private $freeProxy;
public function __construct($freeProxy)
{
$this->freeProxy = $freeProxy;
}
/**
* @Route("/example", name="example")
*/
function someMethod()
{
dump($this->freeProxy);
dump($this->getParameter('free_proxy'));die();
}
}
I then went to a fresh 4.2 project and tried action injection:
class IndexController extends AbstractController
{
public function index($freeProxy)
{
return new Response("Index $freeProxy");
}
}
Action injection works as expected for 4.2 but not 3.4. Constructor injection works fine in either version.
answered Jan 3 at 14:54
CeradCerad
36.1k76371
add a comment |
So there are two mysteries here. First is why is the container not being injected which in turn causes getParameter to fail. And second, why does bind generate that unused binding error.
You did not show your routing but I suspect that somewhere along the line you actually have:
$exampleController = new ExampleController();
If so then this explains why getParameter is failing. You really need to let Symfony create the controller based on the route. Otherwise the container is not injected and other controller magic is skipped.
I installed a fresh 3.4 app with the old directory structure and added a parameter
composer create-project symfony/framework-standard-edition s34
# app/config/parameters.yml
parameters:
free_proxy: "http://xxx:8080"
I then tweaked the default controller using the default route annotation:
class DefaultController extends Controller
{
/**
* @Route("/", name="homepage")
*/
public function indexAction(Request $request)
{
$freeProxy = $this->getParameter('free_proxy');
// replace this example code with whatever you need
return $this->render('default/index.html.twig', [
'base_dir' => realpath($this->getParameter('kernel.project_dir')).DIRECTORY_SEPARATOR.$freeProxy,
]);
}
}
And everything worked as expected. The Symfony request handler takes care of injecting the container and thus gives you access to the parameters. If you cannot get this working then please update your question with your routing information.
I then took a look at the bind issue. You really want to inject these parameters instead of pulling them. I updated services.yml
# app/config/services.yml
services:
bind:
$freeProxy: '%free_proxy%'
And started getting those unused binding errors. It turns out that bind does not work for action injection. Not really sure why. I don't use it much but I really would have expected that just adding $freeProxy to your action method would work. In any event, here is a working example of the proper way to do things.
class ExampleController extends Controller
{
private $freeProxy;
public function __construct($freeProxy)
{
$this->freeProxy = $freeProxy;
}
/**
* @Route("/example", name="example")
*/
function someMethod()
{
dump($this->freeProxy);
dump($this->getParameter('free_proxy'));die();
}
}
I then went to a fresh 4.2 project and tried action injection:
class IndexController extends AbstractController
{
public function index($freeProxy)
{
return new Response("Index $freeProxy");
}
}
Action injection works as expected for 4.2 but not 3.4. Constructor injection works fine in either version.
answered Jan 3 at 14:54
CeradCerad
36.1k76371
add a comment |
So there are two mysteries here. First is why is the container not being injected which in turn causes getParameter to fail. And second, why does bind generate that unused binding error.
You did not show your routing but I suspect that somewhere along the line you actually have:
$exampleController = new ExampleController();
If so then this explains why getParameter is failing. You really need to let Symfony create the controller based on the route. Otherwise the container is not injected and other controller magic is skipped.
I installed a fresh 3.4 app with the old directory structure and added a parameter
composer create-project symfony/framework-standard-edition s34
# app/config/parameters.yml
parameters:
free_proxy: "http://xxx:8080"
I then tweaked the default controller using the default route annotation:
class DefaultController extends Controller
{
/**
* @Route("/", name="homepage")
*/
public function indexAction(Request $request)
{
$freeProxy = $this->getParameter('free_proxy');
// replace this example code with whatever you need
return $this->render('default/index.html.twig', [
'base_dir' => realpath($this->getParameter('kernel.project_dir')).DIRECTORY_SEPARATOR.$freeProxy,
]);
}
}
And everything worked as expected. The Symfony request handler takes care of injecting the container and thus gives you access to the parameters. If you cannot get this working then please update your question with your routing information.
I then took a look at the bind issue. You really want to inject these parameters instead of pulling them. I updated services.yml
# app/config/services.yml
services:
bind:
$freeProxy: '%free_proxy%'
And started getting those unused binding errors. It turns out that bind does not work for action injection. Not really sure why. I don't use it much but I really would have expected that just adding $freeProxy to your action method would work. In any event, here is a working example of the proper way to do things.
class ExampleController extends Controller
{
private $freeProxy;
public function __construct($freeProxy)
{
$this->freeProxy = $freeProxy;
}
/**
* @Route("/example", name="example")
*/
function someMethod()
{
dump($this->freeProxy);
dump($this->getParameter('free_proxy'));die();
}
}
I then went to a fresh 4.2 project and tried action injection:
class IndexController extends AbstractController
{
public function index($freeProxy)
{
return new Response("Index $freeProxy");
}
}
Action injection works as expected for 4.2 but not 3.4. Constructor injection works fine in either version.
answered Jan 3 at 14:54
CeradCerad
36.1k76371
So there are two mysteries here. First is why is the container not being injected which in turn causes getParameter to fail. And second, why does bind generate that unused binding error.
You did not show your routing but I suspect that somewhere along the line you actually have:
$exampleController = new ExampleController();
If so then this explains why getParameter is failing. You really need to let Symfony create the controller based on the route. Otherwise the container is not injected and other controller magic is skipped.
I installed a fresh 3.4 app with the old directory structure and added a parameter
composer create-project symfony/framework-standard-edition s34
# app/config/parameters.yml
parameters:
free_proxy: "http://xxx:8080"
I then tweaked the default controller using the default route annotation:
class DefaultController extends Controller
{
/**
* @Route("/", name="homepage")
*/
public function indexAction(Request $request)
{
$freeProxy = $this->getParameter('free_proxy');
// replace this example code with whatever you need
return $this->render('default/index.html.twig', [
'base_dir' => realpath($this->getParameter('kernel.project_dir')).DIRECTORY_SEPARATOR.$freeProxy,
]);
}
}
And everything worked as expected. The Symfony request handler takes care of injecting the container and thus gives you access to the parameters. If you cannot get this working then please update your question with your routing information.
I then took a look at the bind issue. You really want to inject these parameters instead of pulling them. I updated services.yml
# app/config/services.yml
services:
bind:
$freeProxy: '%free_proxy%'
And started getting those unused binding errors. It turns out that bind does not work for action injection. Not really sure why. I don't use it much but I really would have expected that just adding $freeProxy to your action method would work. In any event, here is a working example of the proper way to do things.
class ExampleController extends Controller
{
private $freeProxy;
public function __construct($freeProxy)
{
$this->freeProxy = $freeProxy;
}
/**
* @Route("/example", name="example")
*/
function someMethod()
{
dump($this->freeProxy);
dump($this->getParameter('free_proxy'));die();
}
}
I then went to a fresh 4.2 project and tried action injection:
class IndexController extends AbstractController
{
public function index($freeProxy)
{
return new Response("Index $freeProxy");
}
}
Action injection works as expected for 4.2 but not 3.4. Constructor injection works fine in either version.
answered Jan 3 at 14:54
CeradCerad
36.1k76371
answered Jan 3 at 14:54
CeradCerad
36.1k76371
answered Jan 3 at 14:54
CeradCerad
36.1k76371
answered Jan 3 at 14:54
CeradCerad
36.1k76371
36.1k76371
add a comment |
add a comment |
documentation show like this :
parameters.yml :
parameters:
mailer.transport: sendmail
to set :
$container->setParameter('mailer.transport', 'sendmail');
to get :
$container->getParameter('mailer.transport');
edited Jan 3 at 13:03
hrust
5261825
answered Jan 3 at 12:51
Aym2ricAym2ric
65
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
add a comment |
documentation show like this :
parameters.yml :
parameters:
mailer.transport: sendmail
to set :
$container->setParameter('mailer.transport', 'sendmail');
to get :
$container->getParameter('mailer.transport');
edited Jan 3 at 13:03
hrust
5261825
answered Jan 3 at 12:51
Aym2ricAym2ric
65
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
add a comment |
documentation show like this :
parameters.yml :
parameters:
mailer.transport: sendmail
to set :
$container->setParameter('mailer.transport', 'sendmail');
to get :
$container->getParameter('mailer.transport');
edited Jan 3 at 13:03
hrust
5261825
answered Jan 3 at 12:51
Aym2ricAym2ric
65
documentation show like this :
parameters.yml :
parameters:
mailer.transport: sendmail
to set :
$container->setParameter('mailer.transport', 'sendmail');
to get :
$container->getParameter('mailer.transport');
edited Jan 3 at 13:03
hrust
5261825
answered Jan 3 at 12:51
Aym2ricAym2ric
65
edited Jan 3 at 13:03
hrust
5261825
edited Jan 3 at 13:03
hrust
5261825
edited Jan 3 at 13:03
hrust
5261825
5261825
answered Jan 3 at 12:51
Aym2ricAym2ric
65
answered Jan 3 at 12:51
Aym2ricAym2ric
65
answered Jan 3 at 12:51
Aym2ricAym2ric
65
65
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
add a comment |
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
maybe you need to set before get and this can explain : " I get an error: Call to a member function getParameter() on null "
– Aym2ric
Jan 3 at 13:05
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54009230%2fread-from-parameters-in-symfony-3-4-getparameter-null%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Things have changed a bit with the introduction of autowire. Read through here for several recommended approaches. Or else consult the container docs to see how to inject the container into your controller.
– Cerad
Jan 2 at 15:54
@Cerad I tried some solution like that. I don't get it, why so complicated. In Laravel is ENV.free_proxy and that's all. I've read different aproaches to to this for symonfy 3.4, for 3.3 and for above 2.8 (which is symfony 3.3 and 3.4 too)
– pmirnd
Jan 2 at 16:19
Many things seem complicated the first time you work through them but after awhile they become routine. Just bind $freeProxy to your value and then all you need to do is to name a variable $freeProxy in your action method. From a bigger point of view, injecting the complete container has always been considered to be a bit of an anti-pattern which was tolerated because it made life much simpler. Sort of like a rich but obnoxious uncle. But the fairly new autowire functionality has made eliminating the container more practical.
– Cerad
Jan 2 at 16:26
I might add that configuring and injecting services/parameters is one of the key cornerstones of Symfony. It's well worth taking the time to understand.
– Cerad
Jan 2 at 16:28
I'll edit my answer with
services.ymlfor more help, because it didn't work for me.– pmirnd
Jan 2 at 16:39