Why do you want the lara and the hangar to work on one port?If you're making a SPA app, it's gonna be right to split the fron and buck. Separately pick up the angull and communicate with the baek through API.This is an example of a simple SPA with a lara and anolare https://developer.okta.com/blog/2018/10/23/php-laravel-angular-crud-app

Simple option: ask a programmer from 1C to download instead<Описание>Накладка-аккумулятор WK-DESIGN WP-020 iphone 7 (золотистый)</Описание> <ЗначенияСвойства> <Ид>33432d98-3b06-11e3-9566-00144f9b870d</Ид> <Значение>Чехол аккумулятор для iPhone 7 WK-DESIGN WP-020 </Значение> </ЗначенияСвойства> I'd like to get out of here.<Описание>Чехол аккумулятор для iPhone 7 WK-DESIGN WP-020</Описание> Option 2: If there is no access to 1C programmers. A name in exchange.<ЗначенияСвойства> <Ид>33432d98-3b06-11e3-9566-00144f9b870d</Ид> <Значение>Чехол аккумулятор для iPhone 7 WK-DESIGN WP-020 </Значение> </ЗначенияСвойства> On condition <Ид>33432d98-3b06-11e3-9566-00144f9b870d</Ид> Not changed in all goods.

Use or cukes or urles, or you'll always have conflicts. Those:Middleware checks the urles and gives pages according to the localeMiddleware checks the cubes and gives pages according to the established Locale I add that the use of the first logic is better for SEO to optimise the site: you will not, in a multilingual way, mislead the search engines.

Participants migration:public function up() { Schema::create('participants', function (Blueprint $table) { $table->bigIncrements('id'); $table->unsignedBigInteger('user_id'); $table->string('name'); $table->timestamps(); $table->foreign('user_id')->references('id')->on('users'); }); } "users" migration: public function up() { Schema::create('users', function (Blueprint $table) { $table->bigIncrements('id'); $table->string('name'); $table->string('email')->unique(); $table->timestamp('email_verified_at')->nullable(); $table->string('password'); $table->rememberToken(); $table->timestamps(); }); } In the User model:public function participant() { return $this->hasOne(Participant::class); } In "Participant" model:public function user() { return $this->belongsTo(User::class); } First is the migration of auser, second to second table

Try it. $this->metodOrConst;

To deal with such issues in design, we need to first understand what is written in the description of the error, and in this case, it says "Unspected variable prodyy on the page," if we use the search, we'll find it in the line:<div class="rating">Sale: {{$prodyy}}%</div> The mistake is that she has no default value, as accepted, if it is not defined! You have a @isset for the variable $prod, and there's no $prodyy. This can be corrected by such a design:{{ $proddy ?? 'Default' }} More detailed information can be found here (see above) https://laravel.ru/docs/v5/blade#%D0%BE%D1%82%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5 ) If I answered your question, please accept it!

E_K is absolutely right! Despite the fact that resources have been earmarked in the documentation:(https://laravel.ru/docs/v5/controllers#%D1%80%D0%B5%D1%81%D1%83%D1%80%D1%81) With the name of the products.show for your example, the best solution in the present situation will be to look through the team:php artisan route:list The list of available rots, and if there's no Root in it, add it manually, like:Route::get('/products/{product}', 'ProductController@show')->name('products.show'); And if I answered your question, I hope you accept it!

You're gonna need to use Carbon for this. Here's the code, for you:use Carbon\Carbon; use App\Post; class PostController extends Controller{ public function create(Request $request) { Post::where('created_at','<', Carbon::now()->addDays(-30))->delete(); … } } If you've helped, please accept the answer!

I've been looking for this, too, but unfortunately, blade has no such functionality. This can be done with JavaScript and several hidden blocks in one blade file!

That's what I wrote. In Modules\Orders\Routes\route.phpRoute::group(['namespace' => 'App\Modules\Orders\Controllers'], function () { .... Route::post('/orders/store/{id}','OrdersController@store')->name('orders.store'); ... }); In the form, respectively:{!! Form::open([ 'route' => ['orders.store'], 'class' => 'form-horizontal' ]) !!}

Add the rule of bail to the rules of verification, example:$request->validate([ 'title' => 'bail|required|unique:posts|max:255', 'body' => 'required', ]); In this case, if the first one passes the test, the laravel will take the second field. (sighs) https://laravel.com/docs/6.x/validation#quick-writing-the-validation-logic ) I hope I can help!

If there are no mistakes, how do you correctly redirect to the original form? If it was an ordinary test, without AJAX, I'd have written return back with('message', 'The Changes are retained.'); after validation in the counteraller. How do you put the code in the JS? This is how the JS page is reloaded, recording the successful conclusion of the sessionPHP$request->session()->flash('success', 'Изменения сохранены.'); return response()->json(['reload' => 'true']); JSif (response.data.type == 'reload') { location.reload(true); } AJAX verification of CSRF is under way when the form is sent?Yes, CSRF is checking when sent through AJAX. Put it in HTML. <meta name="csrf-token" content="viju1hHCwy3IMpzCxCVwb5W3WM0coVPKFmzyjYml"> JSlet token = document.head.querySelector('meta[name="csrf-token"]'); if (token) { window.axios.defaults.headers.common['X-CSRF-TOKEN'] = token.content; } else { console.error('CSRF token not found!'); }

This will work:Middleware:public function handle(Request $request, \Closure $next) { $userData = $request->get('user'); if (empty($userData['email'])) { $userData['email'] = $userData['secondary_email']; $request->merge([ 'user' => $userData, ]); } return $next($request); } I mean, the problem is, the installation of the intended properties through the user.email doesn't work. I would also like to add that there is no need to change the data in the user &apos; s request. The data should come in the form in which, if the logic of your application requires data modifications, there are different solutions, such as DTO, billers, etc. Or, for example, you can just do in FormRequest ghetter class:public function getEmail(): string { return $this->has('email') ? $this->get('email') : $this->get('secondary_email'); }

In the counterpart responsible for this viewpublic function "имя метода"() { // совершаете выборки $positions = App\Positions::all(); $users = App\User::where('name','Алексей Назаров')->first(); $somethingElse = App\Something::all(); //передаете в шаблон return view('register',compact('users','positions', 'somethingElse')); } Users,positions + somethingElse will be available in the template.

SELECT * FROM `users` INNER JOIN `user_attributes` ON user_attributes.user_id = users.id LEFT JOIN likes ON likes.like_user = users.id WHERE user_attributes.gender = 2 AND user_attributes.city = "Витебск" AND user_attributes.age BETWEEN 18 and 35 AND likes.like_user IS NULL LIMIT 4 and, respectively, $users = DB::table('users') ->join('user_attributes', 'user_attributes.user_id','=', 'users.id') ->leftJoin('likes', 'likes.like_user', '=', 'users.id') ->select('user_attributes.user_id','user_attributes.age','user_attributes.avatar','user_attributes.fullname','users.id') ->where('user_attributes.gender','=', $gender) ->where('user_attributes.city','=', Auth::user()->attributes->city) ->whereBetween('user_attributes.age', [18, 35]) ->whereNULL('likes.like_user') ->inRandomOrder() ->take(4) ->get();

I didn't quite understand your question, but it might help in shape where type="file" Add your properties. multiple That at the end, <input type="file" name="myfiles" multiple>♪ and you'll get mass in the server ♪ myfiles[]

$uri = trim('/uk/page/lorem-ipsum', '/'); // чистим строку от слешей $default = 'en'; // локаль по умолчанию $hide_default = true; // скрывать дефолтную локаль $locales = ['uk', 'en', 'ru']; // доступные локали $locales_list = implode('|', $locales); // строка для регулярки uk|ru|en|etc $pattern = "@^($locales_list)@"; // @^(uk|ru|en|etc)@ $uri = preg_replace($pattern, '', $uri); // /page/lorem-ipsum foreach ($locales as $locale){ if (($locale == $default) && $hide_default) { echo 'http://example.com' . $uri; // http://examle.com/page/... } else { echo 'http://examle.com' . '/' . $locale . $uri; // http://examle.com/ru/page/... } } It's a pseudocod rather than a working option, but I hope the point is clear. Remove the elbow from the address line with a regular one, and then just set it up.

We need to finish the method. messages() who returns the body with reports of validation, for example:public function messages() { return [ 'title.required' => 'Заголовок обязательен', 'title.max' => 'Заголовок максимум 255 символов!', 'desc.required' => 'Заполните описание' ]; } I'm telling you to give me a letter. title This is a field. required rule

It's all right. If bash, a file of .bash_profile should be created to indicate the required code. Like this.LANG="en_US.UTF-8"; export LANG or (or both) LC_ALL="en_US.UTF-8"; export LC_ALL If cmd Start->Run->regedit Go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage] Change the “OEMCP” value to “1251” Requires computer restart If zsh or csh, let me see https://superuser.com/questions/1108443/utf8-characters-in-windows-10-bash-terminal

How will the user replace? You're transferring charcoal value.$fillable Only that when you call methods save()♪ create()♪ update() (and other similar) only those fields which are specified (e.g. field) may be modified id No one can change under any pretext, or you have another logic where the field must be strictly static.As soon as you and the rivervest begin to accept it, only then you have to check what you get and where you come from, and until then there's no cause for concern (fucking, if you don't give everyone the right to your code, but then it's the least of the problems you're facing).That's the option. dangerous.:protected function validator(array $data) { return Validator::make($data, [ 'name' => ['required', 'alpha_dash', 'string', 'min:4', 'max:18', 'unique:users'], 'password' => ['required', 'string', 'min:4', 'max:18'], //'role' => ['required', 'numeric', 'in:1'], - это обезопасит любое действие пользователя, но нет смысла давать ему такое, пока у Вас может быть только одна допустимая роль при отправке формы ]); } protected function create(array $data) { return User::create([ 'name' => $data['name'], 'password' => Hash::make($data['password']), 'role' => $data['role'], //Возможна подстановка любого значения, если нет проверки в валидации ]); } The default option in the database is appropriate, but may be uncomfortable. Moreover, sooner or later, you'll still be transferring not only the first role.