-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconfig.php
146 lines (139 loc) · 5.46 KB
/
config.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
<?php
/*
|--------------------------------------------------------------------------
| Confirm New Email Settings
|--------------------------------------------------------------------------
|
| The settings contained within this configuration file relate to
| the Laravel package to confirm a users new email address.
| https://github.com/AlexWinder/laravel-confirm-new-email
|
*/
return [
/*
|--------------------------------------------------------------------------
| Email Verify Settings
|--------------------------------------------------------------------------
|
| The email-verify setting is used to determine if the users
| email_verified_at value should also be updated when the user confirms
| the update of their new email address. When setting this value to true
| be sure to check that the user.fields.verified_datetime value is correct
| for your user model. You also may need to add the value set in
| user.fields.verified-datetime to your $fillable array in your user model
| to allow for mass-assignment. Please see README for further details.
|
*/
'email-verify' => false,
/*
|--------------------------------------------------------------------------
| Redirect Settings
|--------------------------------------------------------------------------
|
| These values are used to specify where you wish specific actions to
| redirect the user. These values should be set to named routes, so
| ensure that your redirection is correctly named. If you do not use a
| valid named route then this will not correctly redirect the user.
|
*/
'redirect' => [
/**
* Where you would like to redirect the user after successful verification
* of their new email address. By default this is set to the edit page.
* If you edit the name of edit route then be sure to also update this.
*/
'update-confirm' => 'confirm-new-email.edit',
],
/*
|--------------------------------------------------------------------------
| Route Settings
|--------------------------------------------------------------------------
|
| These values can be customised to avoid conflicting URI's or route names
| from inside your application, or if you wish to change the name for
| cosmetic purposes. For convenience a route name has also been defined
| and should also be updated if this is likely to conflict with other
| route names inside your application. It is important that all values
| set in these routes should all contain unique 'name' values.
|
*/
'route' => [
/**
* The edit route is that which is used to display the form to allow the user
* to edit their email address.
*/
'edit' => [
'uri' => '/settings/email/edit',
'name' => 'confirm-new-email.edit',
],
/**
* The update-request route is that which is used to request an update to the
* users email address.
*/
'update-request' => [
'uri' => '/settings/email/edit',
'name' => 'confirm-new-email.update-request',
],
/**
* The update-confirm route is that which is used to confirm the update to the
* users email address. The URI value set here should not match the URI value
* of any other route.
*/
'update-confirm' => [
'uri' => '/settings/email/update',
'name' => 'confirm-new-email.update-confirm',
],
],
/*
|--------------------------------------------------------------------------
| Update Expiry Settings
|--------------------------------------------------------------------------
|
| These values relate to if the update has an expiry. If so then the user
| must confirm their updated email within this time limit to complete
| the update. The update-expiry.enabled value must be set to true
| for the update-expiry.limit value to specify the number of minutes
| for the update to expire.
|
*/
'update-expiry' => [
/**
* If set to true then the update-expiry.limit value will be used to set an
* expiry on the update to the email address.
*/
'enabled' => true,
/**
* The limit is the number of minutes that the update expires in, if the
* update-expiry.enabled value is set to true. If this is set to 0
* then the update-expiry will be disabled.
*/
'limit' => 60,
],
/*
|--------------------------------------------------------------------------
| User Settings
|--------------------------------------------------------------------------
|
| These values relate to settings of the user which is having their e-mail
| address updated. In addition to these please also ensure that the
| auth.providers.users config values are set. Please see README for
| further details.
|
*/
'user' => [
/**
* Specific fields of the database which are to be used to be updated.
*/
'fields' => [
/**
* The field of the user table which stores the email address.
*/
'email' => 'email',
/**
* The field of the user table which stores the datetime that the
* user was verified.
*/
'verified-datetime' => 'email_verified_at',
],
],
];