我正在使用Laravel 8为我的项目和更新表单,因此在控制器中,我添加了以下内容以显示成功消息:
Session::flash('success','asdasd');
但这并不显示刀片式服务器中的任何数据:
@if(\Session::has('success'))
<div class="alert alert-success" role="alert">
{{ \Session::get('success') }}
</div>
@endif
但是当我使用Session put时,它会正确显示警告框:
Session::put('success','asdasd');
但是在kernel.php
中,我已经确定了这一点:
protected $middleware = [
\Illuminate\Session\Middleware\StartSession::class,
...
到底出了什么问题如何使用session->flash提交一次会话?
以下是session.php
的完整代码:
<?php
use Illuminate\Support\Str;
return [
/*
|--------------------------------------------------------------------------
| Default Session Driver
|--------------------------------------------------------------------------
|
| This option controls the default session "driver" that will be used on
| requests. By default, we will use the lightweight native driver but
| you may specify any of the other wonderful drivers provided here.
|
| Supported: "file", "cookie", "database", "apc",
| "memcached", "redis", "dynamodb", "array"
|
*/
'driver' => env('SESSION_DRIVER', 'file'),
/*
|--------------------------------------------------------------------------
| Session Lifetime
|--------------------------------------------------------------------------
|
| Here you may specify the number of minutes that you wish the session
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
'lifetime' => env('SESSION_LIFETIME', 120),
'expire_on_close' => false,
/*
|--------------------------------------------------------------------------
| Session Encryption
|--------------------------------------------------------------------------
|
| This option allows you to easily specify that all of your session data
| should be encrypted before it is stored. All encryption will be run
| automatically by Laravel and you can use the Session like normal.
|
*/
'encrypt' => false,
/*
|--------------------------------------------------------------------------
| Session File Location
|--------------------------------------------------------------------------
|
| When using the native session driver, we need a location where session
| files may be stored. A default has been set for you but a different
| location may be specified. This is only needed for file sessions.
|
*/
'files' => storage_path('framework/sessions'),
/*
|--------------------------------------------------------------------------
| Session Database Connection
|--------------------------------------------------------------------------
|
| When using the "database" or "redis" session drivers, you may specify a
| connection that should be used to manage these sessions. This should
| correspond to a connection in your database configuration options.
|
*/
'connection' => env('SESSION_CONNECTION', null),
/*
|--------------------------------------------------------------------------
| Session Database Table
|--------------------------------------------------------------------------
|
| When using the "database" session driver, you may specify the table we
| should use to manage the sessions. Of course, a sensible default is
| provided for you; however, you are free to change this as needed.
|
*/
'table' => 'sessions',
/*
|--------------------------------------------------------------------------
| Session Cache Store
|--------------------------------------------------------------------------
|
| While using one of the framework's cache driven session backends you may
| list a cache store that should be used for these sessions. This value
| must match with one of the application's configured cache "stores".
|
| Affects: "apc", "dynamodb", "memcached", "redis"
|
*/
'store' => env('SESSION_STORE', null),
/*
|--------------------------------------------------------------------------
| Session Sweeping Lottery
|--------------------------------------------------------------------------
|
| Some session drivers must manually sweep their storage location to get
| rid of old sessions from storage. Here are the chances that it will
| happen on a given request. By default, the odds are 2 out of 100.
|
*/
'lottery' => [2, 100],
/*
|--------------------------------------------------------------------------
| Session Cookie Name
|--------------------------------------------------------------------------
|
| Here you may change the name of the cookie used to identify a session
| instance by ID. The name specified here will get used every time a
| new session cookie is created by the framework for every driver.
|
*/
'cookie' => env(
'SESSION_COOKIE',
Str::slug(env('APP_NAME', 'laravel'), '_').'_session'
),
/*
|--------------------------------------------------------------------------
| Session Cookie Path
|--------------------------------------------------------------------------
|
| The session cookie path determines the path for which the cookie will
| be regarded as available. Typically, this will be the root path of
| your application but you are free to change this when necessary.
|
*/
'path' => '/',
/*
|--------------------------------------------------------------------------
| Session Cookie Domain
|--------------------------------------------------------------------------
|
| Here you may change the domain of the cookie used to identify a session
| in your application. This will determine which domains the cookie is
| available to in your application. A sensible default has been set.
|
*/
'domain' => env('SESSION_DOMAIN', null),
/*
|--------------------------------------------------------------------------
| HTTPS Only Cookies
|--------------------------------------------------------------------------
|
| By setting this option to true, session cookies will only be sent back
| to the server if the browser has a HTTPS connection. This will keep
| the cookie from being sent to you when it can't be done securely.
|
*/
'secure' => env('SESSION_SECURE_COOKIE'),
/*
|--------------------------------------------------------------------------
| HTTP Access Only
|--------------------------------------------------------------------------
|
| Setting this value to true will prevent JavaScript from accessing the
| value of the cookie and the cookie will only be accessible through
| the HTTP protocol. You are free to modify this option if needed.
|
*/
'http_only' => true,
/*
|--------------------------------------------------------------------------
| Same-Site Cookies
|--------------------------------------------------------------------------
|
| This option determines how your cookies behave when cross-site requests
| take place, and can be used to mitigate CSRF attacks. By default, we
| will set this value to "lax" since this is a secure default value.
|
| Supported: "lax", "strict", "none", null
|
*/
'same_site' => 'lax',
];
更新:
public function update(Request $request)
{
$homie = HomeMainPage::where('id',1)->update([
'header' => $request->header,
'para' => $request->para,
'button' => $request->button,
'action' => $request->action,
]);
$request->session()->flash("success", "Hello, I am here");
return redirect()->back();
}
2条答案
按热度按时间mwkjh3gx1#
使用Laravel官方文档中提到的helper函数:
h22fl7wq2#
TLDR:
确保
StartSession
中间件只用于路由一次。详细信息:
在您的问题中,您指出
StartSession
中间件位于全局$middleware
堆栈中。但是,默认情况下,Laravel已经将StartSession
中间件包含在web
中间件组中。如果您已经将
StartSession
中间件添加到全局堆栈中,而没有从web
中间件组中删除该中间件,这意味着使用web
中间件组的任何路由都将运行StartSession
中间件两次。如果StartSession
中间件运行两次,您的闪存数据将永远不会到达下一个请求。在
StartSession
中间件的“after-middleware”部分,会话数据被保存并写入存储。保存会话数据的一部分是使闪存数据老化。这会将闪存数据从_flash.new
(本次请求中闪存的数据)移动到_flash.old
(下一次请求中可用的闪存数据),然后清空_flash.new
。然后,下一个请求通过查看_flash.old
来访问闪存数据。但是,如果
StartSession
中间件在同一个请求中运行两次,它将两次保存会话数据,从而两次老化闪存数据。因此,在第一次保存时,它会将新的闪存数据从_flash.new
移动到_flash.old
,并清除_flash.new
。但是,在第二次保存时,它会再次这样做,但由于_flash.new
已经被清空,它会将现在为空的_flash.new
复制到_flash.old
中,下一次请求时闪存数据将不存在。