andreich1980

Do they really need to be in different tables?

Maybe you can store them all in users with diferent roles. You could even create separate Models for them if you want.

Route prefixes has nothing to do with "directories in public folder".

remove or rename dashboard directory from your public directory

check DashboardController authorization - maybe there's a policy or something else that needs you to have a specific role to open the route.

So you would show your DashboardController

You shouldn't save files to the public directory directly. Save them to the storage/app/public and make a symlink as described here https://laravel.com/docs/5.8/filesystem

You extract report logic from the controller method to a job.

Then dispatch the job in the controller method.

And call the job in the scheduler task.

The given advice is quite good.

@ELO - Try something like this. Add it to a temporary /test route.

symlink('/home/username/public_html/storage', '/home/username/public_html/storage/app/public');

get method returns a collection. I think you should paginate it before calling get.

$files = $files->latest('created_at')->paginate();

you should run php artisan symboli:link at the shared hosing as well.

your url is wrong. All the possible urls are at the pic https://appdividend.com/wp-content/uploads/2019/03/Laravel-5.8-CRUD-Tutorial-.png what do you expect to see? books list or a book? for books list it is localhost:81/books, for a specific book it would be localhost:81/books/1

Yes it's required. Your browser sends a request to homestead.test but there's no such a website and if you haven't added it to the hosts the browser will tell you that the website does not exist.

Have you added the IP and the domain name to your host's hosts file? It must he your host's machine hosts file

Do you have $(document).ready(function () { ... }) as it is described here? https://github.com/HemantNegi/jquery.sumoselect#usage

Well, pulled orchestral/testbench, tweaked my tests and some code and it worked like a charm.

I tried to downgrade all the dependencies to 1.1 but it didn't work for illuminate/container, because it depends on illuminate/notifications that doesn't have 1.1 version at all

@MARTINBEAN - My package is for fresh laravel version (5.8, maybe 5.7, probably it will work with older versions as well) I did composer require --dev illuminate/config=~5.8 then composer require --dev illuminate/foundation and got the same error

illuminate/foundation v1.1.2 requires illuminate/config 1.1.* -> satisfiable by illuminate/config[v1.1.0] but these conflict with your requirements or minimum-stability.

Do you mean I should install 1.1 version of config?

I'm creating a package that should use a job. The job looks like this

<?php

namespace Vendor\Package\Jobs;

use Illuminate\Foundation\Bus\Dispatchable;

class VerifyProxy implements ShouldQueue {

    use Dispatchable, ...;

    ...
}

To test my package I composer require --dev some pachages listIlluminate/database, illuminate/config. Now it seems that I need to pull the illuminate/foundation as well. But it doesn't work

$ composer require --dev illuminate/foundation
Using version ^1.1 for illuminate/foundation
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - illuminate/foundation v1.1.2 requires illuminate/config 1.1.* -> satisfiable by illuminate/config[v1.1.0] but these conflict with your requirements or minimum-stability.
    - illuminate/foundation v1.1.1 requires illuminate/config 1.1.* -> satisfiable by illuminate/config[v1.1.0] but these conflict with your requirements or minimum-stability.
    - illuminate/foundation v1.1.0 requires illuminate/config 1.1.* -> satisfiable by illuminate/config[v1.1.0] but these conflict with your requirements or minimum-stability.
    - Installation request for illuminate/foundation ^1.1 -> satisfiable by illuminate/foundation[v1.1.0, v1.1.1, v1.1.2].


Installation failed, reverting ./composer.json to its original content.

I looked it up and noticed that the package is marked as abandoned.

How can I solve this?

I think you should share the errors.

I really like the new design but there's one thing that hurt my eyes every day. https://imgur.com/a/NqYlZAx

It's just fantabulous.

I found an option in my hosting panel: disabled_function and there was some of them like exec, shell, including proc-open. So I just removed it and it all works :)

was it solved finally?

maybe it should be composer packages?

$member->groups gives you all the groups the $member is in.

I guess Eloquent does it automatically - you can set values to the model and call save(). If nothing has been changed it won't really hit the database.

or maybe you would like something like this? https://sweetalert2.github.io

@DAVY_YG - does it work? do you see the alert with 'success' text? is this what you want?

you would add a div with absolute positioning. https://www.w3schools.com/howto/howto_css_modals.asp

Will this help? https://stackoverflow.com/a/15153931/3071884

@FATIMA1 - depends on a technology you're using

Isn't it a duplicate for the https://laracasts.com/discuss/channels/laravel/update-row-of-database-on-laravel

my answer from there

There must be a query with a join between orders and inventories (or whatever the table name is), then you would add a where like this ->where('orders.user_order_id', '=', DB::raw('inventories.user_id')) and then call ->delete()

If you want to send the request with PHP - use Guzzle package. If you use Vue/JS - use axios or a vanila JS ajax request.

Or I didn't understand your question

Should project B use the API of the project A?

There must be a query with a join between orders and inventories (or whatever the table name is), then you would add a where like this ->where('orders.user_order_id', '=', DB::raw('inventories.user_id')) and then call ->delete()

{{ auth()->user()->personal_details->first_name

@petritr would you provide more info about your business process here? what are you going to do?

It's all a bit confusing.

You have a number of forms on the page. Then you do what? Click on a submit button in one of the forms? Then validate the form and submit it?

I think the problem is you can't use the same ID for different elements. You would change #save_device to .save_device as well as #submit-new-hidden.

And then change your forms declaration to <form class="save_device">. The same with buttons.

You forgot each for tasks.

You need to know how many attempts login user failed. Then you would decide shoud captcha be required or not.

Yes, you can do it this way

$request->validate([
    'name' => ($name) ? 'required' : 'nullable'
]);

or like this

$rules [
    'name' => 'required',
];

if ($loginAttemts >= 3) {
    rules['captcha'] = 'required';
}

$request->validate($rules);

Try this https://stackoverflow.com/a/49489310/3071884

check you browser console for any errors

I do my seeders with firstOrCreate. So I can run the seeder as many times as I want

If I'm not mistaken Socialite does nothing with your database. It only redirects you to the website (FB, GitHub), and then catches when you are redirected back with authenticated user data.

It's up on you what do you do with the data.

Of course you can look for a user by the email from a provider and only if you don't have one - create a brand new user.

json_encode(get_object_vars($yourModel));

https://stackoverflow.com/a/9896286/3071884

dd($clientProduct->exists)?

How do you know it is not saved?

Where do you get photos for the select form field?

You can skip users, who has usage_notification_sent_at filled, from checking

Or a separate table sent_notifications if you have more that 1 notification type to send.

usage_notification_sent_at column? in the users table?

@MDELSHAD - you have to add use App\Models\Article\Article; on the top of the file App\Models\Article\Traits\Relationship\ArticleRelationship.php. You are using User model but haven't imported one.

Hey bro. The error looks like you missed use App\Models\Article\Article; in a file inside of App\Models\Auth\Traits\Relationship. That's exactly what happens when you forget to import a class - it tries to find the class in the same namespace.

So, go through all the files inside App\Models\Auth\Traits\Relationship (or, all files that have this namespace) and check wheither or not you're using Article model in the files and if you do - check that it has use App\Models\Article\Article; at the top of the file.

@AHPENGGGGG - Ok, it was confusing when you were talking about "deleting a single array"