Global variable in controller laravel 8

Question

0.00/5 (No votes)

See more:

Why it returns empty in variable X

class ProduitController extends Controller
{
  private $X ;

  public function uploaderFils(){
      .
      .
      .
       $this->X=$imageName;
  }

  public function AddProduct(Request $request){
      . . .
    return   ("Image Name". $this->X);
  }
}

What I have tried:

Why it returns empty in variable X

Posted 29-Aug-22 7:10am

paradox02

Updated 29-Aug-22 7:27am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2022-08-29T07:27:00

I don't know Laravel at all, but in other Controller-based frameworks, a controller will only exist for the current request and then it dies afterwards, taking any variables with it.

So, in your example, if a client calls uploaderFils, the controller instance will die after that call ends, taking the value of $X with it. The client call to AddProduct gets a new controller instance with nothing in it, and $X will be empty.

You seem to be thinking in terms of a normal desktop application, not a web application. A web application is stateless, and works in a request->response paradigm. Once the response is sent back to the client, the controller no longer exists, and a new controller is created upon a new request.

You're also thinking in terms of a single-user application. Web apps are multi-user, so setting a "global" variable can be overwritten by a new user request.

If you want to save state between requests for individual users, you have to save that state information somewhere else, like a database, or cookies if the state is small enough. Laravel should have some mechanism to save state somewhere.