laragon | Laragon

Many of the Blade directives become specific if statements in the compiled view. In this case, you have @error() but no @enderror (and also no code to put between them to be shown when there is an error). See the @error directive documentation.

I manage to create the nextJS project on Users/ directory and it turns out to fix the error. Before that, I created the project outside of Users/ directory (directly on C: and create folder on there). So maybe it was a permission thing that make the project can't run.

would like to share My solution for this I used 64bit version and its in my PC "D" drive with no mysql root password

1.Install c++ redistribution package from Microsoft site "VC_redist.x64.exe"

2-Download mysql8.0.x-winx64.zip archive

3-Extract to "D:\laragon\bin\mysql" directory change drive letter accordingly

4-Stop laragon and and select mysql8.0-winx64 version from Laragon Menu ->version->mysql-8.0.x-win64

5-Now start the Service wait for few seconds to allow initialization

6-Stop mysql server go to directory "D:\laragon\bin\mysql\mysql-8.0.x-winx64\bin" run "mysqld stop" this will stop sql

7-Go to "D:\laragon\data" rename existing "mysql-8" folder to mysql.bk and rename "mysql" folder to mysql-8

8-Stop Laragon and restart it again

open cmd.exe as Administrator

9-go to directory "D:\laragon\bin\mysql\mysql-8.0.x-winx64" run "mysql_upgrade.exe -u root -p" I didnt have password so i left it blank after -p

10-Click Enter without password when prompted Wait for Few minutes to allow mysql do the upgrade

11-now go to mysql terminal from Laragon enter comand "mysql -u root -p" Click Enter without password

12.Now enter the following comand "ALTER USER 'root'@'localhost' IDENTIFIED BY 'NewPassword';" replace NewPassword with your own one

13.Now Restart Laragon again

If you have Phpmyadmin installed it should work now if you dont have install it from add feature

Chears

I found what was causing the problem, I had a space between content and ="Hello There" by removing it and leaving it like content="Hello There" solves the problem.

the first ensure if the data get correctly test it on postman or on browser you can use method dd() so if the data come correct

the problem in view index.blade.php
I think it works on first method because you get one object (one record)

and it doesn't work for get method because it gets array of object so the way of display this array it is different from the one object

ensure the way of display it and use foreach in index.blade.php

hopefully that is help you

update:

keep the store function empty remove $id also .like this

Are your imports fine? If Schede is a model, it should be imported from models.py I believe. And it's better to specify your_app name in imports.

Since you have already loaded the entire contents of the spreadsheet into the $validatedFile variable, why make a LazyCollection object? Their only purpose is to save memory by not loading large data sets into memory. Your validation rules using closures can also be cleaned up. This isn't just a cosmetic change: in_array() is notoriously slow.

In many os the errors output (stderr) of the commands isn't the same that the normal output (stdout), you need to redirect the errors to the stdout. so the command must be:

$ command $arg1 $arg2 ... 2>&1

This cause that the errors messages will be sent to the stdout, Is util remember this when you are working with system calls.

Now in your code i prefer to use the exec function in php