Accessing Session Values Laravel

### Using the `session()` Helper

You can retrieve session values using the `session()` helper like this:

$email = session('user');
$loggedUid = session('loggeduid');

### Using the `Session` Facade

Alternatively, you can use the `Session` facade to get session values:

use IlluminateSupportFacadesSession;

// Inside your controller method
$email = Session::get('user');
$loggedUid = Session::get('loggeduid');

### Example in a Controller

Here’s an example of how you might use it in a different controller:

namespace AppHttpControllers;

use IlluminateHttpRequest;
use IlluminateSupportFacadesSession;

class AnotherController extends Controller
{
    public function someMethod(Request $request)
    {
        $email = session('user'); // or use Session::get('user');
        $loggedUid = session('loggeduid'); // or use Session::get('loggeduid');

        // Now you can use $email and $loggedUid as needed
        return response()->json([
            'email' => $email,
            'loggedUid' => $loggedUid,
        ]);
    }
}

### Important Note

Make sure that the session is correctly started and that the session values are set before you try to access them in another controller. If the session values are not available, you may need to check the session configuration or ensure that the session data is correctly being set in the previous controller.

### 1. Check Session Configuration

Ensure that your session is correctly configured in the `config/session.php` file. Common settings to review include:

– **Session Driver**: Ensure you're using an appropriate session driver (e.g., `file`, `database`, `cookie`, etc.). The default is usually `file`, which stores session files in the `storage/framework/sessions` directory.

'driver' => env('SESSION_DRIVER', 'file'),

### 2. Verify Session Middleware

Make sure your controller is using the session middleware. By default, all controllers should have session middleware, but if you have custom routes or middleware configurations, ensure that `IlluminateSessionMiddlewareStartSession::class` is included.

You can check this in your `app/Http/Kernel.php` file:

protected $middlewareGroups = [
    'web' => [
        AppHttpMiddlewareEncryptCookies::class,
        IlluminateSessionMiddlewareStartSession::class,
        IlluminateViewMiddlewareShareErrorsFromSession::class,
        // ...
    ],
];

### 3. Confirm Session Value is Set

In the controller where you set the session values, make sure that the values are indeed being set. You can check by logging or debugging right after setting them:

$request->session()->regenerate();
Session::put('user', $request->email);
Session::put('loggeduid', Auth::guard($this->guard)->user()->id);

// Debugging
logger('User session set: ' . $request->email);
logger('Logged UID session set: ' . Auth::guard($this->guard)->user()->id);

### 4. Check for Session Expiration

If you're using a custom session expiration time, ensure that the session hasn't expired by the time you try to access it. You can set the expiration time in your `config/session.php`:

'lifetime' => 120, // Time in minutes
'expire_on_close' => false,

### 5. Session Flash Data

If you are using `Session::flash()` instead of `Session::put()`, remember that flash data is only available for the next request. If you need the data to persist beyond a single request, make sure to use `Session::put()`.

### 6. Debugging in the Other Controller

When retrieving session values in the other controller, add debugging logs to see what is being retrieved:

public function someMethod(Request $request)
{
    $email = session('user'); // or use Session::get('user');
    $loggedUid = session('loggeduid'); // or use Session::get('loggeduid');

    // Debugging
    logger('Email from session: ' . $email);
    logger('Logged UID from session: ' . $loggedUid);

    return response()->json([
        'email' => $email,
        'loggedUid' => $loggedUid,
    ]);
}

### Summary

After checking these areas, try accessing the session values again. If the issue persists, you might want to look into the overall session management in your application, including any potential session storage problems or browser settings that might be affecting session handling.