jlrdw

Yes look in the documentation and find database transactions it's listed under the database chapter.

https://laravel.com/docs/6.x/database#database-transactions

If you have never used transactions, wouldn't hurt to Google that subject and read more about MySQL and database transactions.

Why would a seeder be needed to create a new user. Are you referring to each new user has their own unique table. Sorry if I am mis-understanding something.

Consider using laravel, regular pdo can be used in laravel. Just a suggestion.

Like where you have

    if(empty($username))
    {
        $username_error = "<p>Please enter your username!</p>";
    }

Instead put a message in session "username required" named err_username. Just example.

redirect to the login form, and if the session has err_username, display label in red under username field

"username required".

The login form just needs some conditional if else statements to handle errors.

Just fyi, been a while since I messed with non mvc php, quite a while.

Like where you have

    if(empty($username))
    {
        $username_error = "<p>Please enter your username!</p>";
    }

Instead put a message in session "username required" named err_username. Just example.

redirect to the login form, and if the session has err_username, display label in red under username field

"username required".

The login form just needs some conditional if else statements to handle errors.

Just fyi, been a while since I messed with non mvc php, quite a while.

You need to write an eloquent query or a regular query that does a group by by account_id.

Also you already have that in a nice array if that's all you need.

The on('users') just use same table name. That's very common in logistics software, you have pickups and drops, thus two equal child tables.

But I would normally write a special delete query for this type relation, delete all children first, then delete parent.

But that's up to you how to handle deleting.

You have to store an error message in session, and on the failed login form use an if statement to see if an error was passed in the session. Have a label under failed field that shows, for example, wrong password entered.

The label will only show if an error, so it's in an if statement.

From what you show above, that should point you in the correct direction. Basically make your own flash error message.

If @snapey is correct, then @gacho I recommend you install a fresh laravel and let's get going. Laravel is very flexible and easy to use. Flexibility is why I like it, you can do things the "laravel way" or the php / pdo way yet have the benefits of the mvc, controllers, models, views, etc.

I for example do use laravel authentication to login, but have custom code for authorization that works with roles. I do not recommend someone new to programming to use custom authorization, but only a programmer with experience in RBAC.

That was just an example.

Are you showing this, or is there a question.

Look into semantic versioning.

https://semver.org

In all actuality it doesn't hurt just to do a brand new install, and just migrate your existing code over like models controllers views etc.

It only takes a little while longer.

Take note 6.0 has the new UI.

But that's covered in the documentation.

First I would highly advise using out of box Authentication it works great and properly returns back to the login form if there are errors.

However if you are using custom validation you need to reread the chapter on validation and do a proper redirect back with the correct flash messages to show the errors.

In his introductory free videos he gives examples of this

Fix code by using laravel request for a first step and using the PDO is fine as long as you bind the parametets as like you are doing.

Even eloquent runs that stuff in the same PDO code , it's converted to regular PDO at runtime.

There's the getPdo () instance.

Also you need to break that up into model and controller.

If you already know laravel pretty well, one idea is to look at a couple of good packages on GitHub on eCommerce and browse source code to give you ideas.

If you are storing images for users you should have a child table for the images with user_id as a foreign key.

It's hard to know exactly what you need because it's your database.

Some people even have a separate folder for each uses images, it depends on how secure these images need to be.

image the same name you gave the actual file, but that name also has to be stored in the database.

@davy_yg if you want to see your query results, but include what is soft deleted, well that's what that does.

@jaytee are you having fun yet.

@davy_yg but he is correct please read and study those documentation examples, as they explain this stuff.

You need to store the filename in a database field. Like myimage.jpg.

I use the asset helper to display images.

The actual file is stored in the file system you're just using image tag to display the image.

Put another way you still have to save a database record in conjunction with the upload, that tutorial must be just how to upload.

That is code to store an image just make sure the path is correct.

In the docs example: quote

public function actions(Request $request)
{
    return [
        (new Actions\ActivateUser)
            ->confirmText('Are you sure you want to activate this user?')
            ->confirmButtonText('Activate')
            ->cancelButtonText("Don't activate"),
    ];
}

endquote

You are probably missing this line:

 (new Actions\ActivateUser)

Study the example again.

@ebrahemsamer if this has been answered, to where it helps you. Could you please mark it as answered. Much appreciated.

@amit123 is there any way you can show this answered, I just read through all the replies, got down to the bottom, not realizing it was resolved.

@khalid_hussain did you take the suggestion and look at a tutorial.

first, not your data here but an example of an eloquent groupby query:

$quy = Powner::query()->leftJoin('dc_pets', 'dc_powners.ownerid', '=', 'dc_pets.ownerid')
                ->select('dc_powners.ownerid', 'dc_powners.oname')
                ->selectRaw('count(dc_pets.petid) as countOfPets')
                ->groupby('dc_powners.ownerid')
                ->orderby('dc_powners.oname')
                ->get();

Results basically give:

ownerid, oname, countOfPets

Like:

5|Bob|3
4|Greg|9
2|Rob|1

You probably need just need to work out a query where you show a warehouse with product and count to start with:

pseudocode

Foreach warehouse_id
       product_id  | product_name | product_count

Then a routine can be written to pick which ware house to "build" the order from.

Have a "pending" field somewhere. Save the order to the db, and once fulfilled and once pending changes to complete, use yet another routine to update the stock (quantity) of each product.

Not having that system to work with it's hard to guess.

Also REMEMBER, these complex queries can take some trial and error to figure out.

Note, you may need a nested group by, i.e., a grouping by warehouse, sub group by products. But more than one way.

My example of course only backs up a database not the application.

Sorry I thought that's what O.P. was after. Spatie also takes a dump of the database.

I just use a bitbucket repo to actually backup the app, I just keep a good copy there.

And yes it works.

I have done this:

    public function backup()
    {
        $this->chklogin();  // custom framework not laravel
        include ROOTUP . 'dbconfig.php';  
        $mysqlExportPath = 'myback_';
        $date = date("Y-m-d-H-i-s");
        $command = 'mysqldump --opt -h' . $mysqlHostName . ' -u' . $mysqlUserName . ' -p' . $mysqlPassword . ' ' . $mysqlDatabaseName . ' > ../../' . $mysqlExportPath . $date . '.sql';
        exec($command, $output = array(), $worked);
        switch ($worked) {
            case 0:
                echo 'Database successfully exported;
                break;
            case 1:
                echo 'There was a warning during export';
                break;
            case 2:
                echo 'There was an error during export;
                break;
        }
        
        //  redirect somewhere as needed.
    }

Goes without saying adjust

 ../../

as needed.

Is there fields to store this extra data, or is it in a related table with something like article_id. And how do you plan on showing in an edit situation. You will need a foreach loop.

Did you follow: https://laravel.com/docs/6.x/routing#form-method-spoofing

That depends on your use case.

For example I have seen some forms where if you answer yes then there's a text area to please explain if answer was yes.

Don't overthink this stuff just use as needed.

Also are you aware that Jeffrey has free video lessons and he covers basic crud.

Have you seen and or worked some of the examples here: https://laravel.com/docs/6.x/queries#ordering-grouping-limit-and-offset

Just curious why not take a good Javascript tutorial.

https://www.w3schools.com/js/js_htmldom.asp

Then just upload with laravel techniques.

Did you update laravel prior to updating the framework. Especially any changed composer dependencies. Something tells me you skipped this step.

I would also recommend finding a good tutorial on jQuery that includes dealing with checkboxes.

Try whereIn

//part of query
->whereIn('id', [1, 2, 3])
//rest of query

Upload the image on imgur.com

Once uploaded, right click image and click view image.

Copy that URL.

Put that url here in a regular image tag.

Note create an account first on imgur.

You do know you have to see if a checkbox is checked:

if ($('#imynput').prop('checked')) {
    // do what you need here.
}

And of course if a checkbox is not checked nothing is passed so you have to check for that in the back end using if request has...

Upload the image on imgur.com

Once uploaded, right click image and click view image.

Copy that URL.

Put that url here in a regular image tag.

Note create an account first on imgur.

Here is an article https://laravel-news.com/sending-receiving-sms-laravel-nexmo

@davy_yg that is correct and even Jeffrey highly recommends just using Blade with HTML just like he does in the videos.

Believe me when I say it made things harder to do.

Have you ever made an image a link, that would be step one finding a small tutorial on doing that.

also if this is a real professional site, I highly suggest one of two things, 1 actually find a good well maintained shopping cart on GitHub and use it or at least view the code on some of them and learn how things work by a study of the code.

Just a suggestion.

But you just use the image as a link no different than like in edit page, just use a route and find the data in the controller really no different than in edit page but you're just using the image instead of a edit or view link button.

@davy_yg that is correct and even Jeffrey highly recommends just using Blade with HTML just like he does in the videos.

Believe me when I say it made things harder to do.

@jaytee it's kind of funny, the very second I saw Jeffrey had said that I immediately bookmarked that.

If they won't believe me, surely they'll believe Jeffrey.

Pal, hehe.

A good start is https://spring.io/guides I never used a framework I just did straight servlets, JSP, and and ejb.

Java was MVC anyway but many times for small things I just used servlet and jsp for The View.

I find using jdbc and PDO are very similar with the bindings, etc

But haven't used since 2007.

P.S. I hope I never have to set up a tomcat server again of course the dedicated host had TomEE.

I would imagine in this Modern Age they have easy installers, unlike the old manual setting it up.

But your browser tools will show you exactly the request and responses.

Did you reboot server.

See this https://laracasts.com/discuss/channels/general-discussion/noob-here

and read @jeffreyway answer, drop the collective and just use html and blade.

https://docs.microsoft.com/en-us/sql/connect/php/connection-options?view=sql-server-ver15

Start there.

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.

So as suggested to you in the past, use your browser developer tools and look at what's going on.

Try now to remember to always do that as a first step. That's how most of us figure this stuff out.