Tray2

You need to set up your Virtual host properly,

You should have one for "laravel1" and another for laravel2.

This link should help you

https://laravel.io/forum/05-02-2015-multiple-hosts-how-to-onedomaincom-twodomaincom-onecom-twocom-virtualhost

Why not just use a single route for login?

There is no reason to have one for each user type.

A user is a user is a user.

Roles should determine what the user is.

Then open a new thread and give us more information about your issue.

Show your code.

Show us your code.

I had this issue as well with Twitter so I removed my twitter link and it uses the gravatar one again.

Make sure your document root is /storage/ssd1/745/15653745/public_html/public. Also make sure the your storage directory has the correct permissions

Wouldn't this work?

$products = Product::whereIn('id', $this->selected)
  ->with(['records', function ($query) {
      $query->doesntHave('parts');
  }])->get();

Still not making any sense.

If you create a sale you store it in a sales table with a created_at right?

Then you can count the records and group them by the sales date to get the number of sales that day.

Like this?

$posts = Post::doesntHave('comments')->get();

https://laravel.com/docs/8.x/eloquent-relationships#querying-relationship-absence

So the logic is

• 5-1 = 4
• 8-5 = 3
• 11-8 = 3

And so on?

If so you need a recursive query.

Not knowing what RDBMS you are using but here is some info about recursive queries

https://stackoverflow.com/questions/20215744/how-to-create-a-mysql-hierarchical-recursive-query

This might point you in the correct direction

https://haydenjames.io/mysql-server-has-gone-away-error-solutions/

I'm not running on a Windows machine here so I can't try to replicate the issue.

I suggest you check out Laravel/Sail then you will have a good lemp setup.

https://laravel.com/docs/8.x/sail

Most likely yes. They don't have any limit on the amount of requests but rather the amount of request within a certain time limit. They might have set it to 20 requests per minute or somesuch.

Not throttling a API can cause performance issues for the provider not to mention opening for DDOS. Even unintentional ones.

I suggest setting a sleep time between the calls to keep them outside the threshold.

This little post might help you knock that habit

https://dev.to/kenbellows/stop-using-so-many-divs-an-intro-to-semantic-html-3i9i

The changes between Laravel 6 and 8 are not big enough to warrant a new series (even if I wouldn't mind one myself).

I recommend watching the What is new in Laravel 7 and 8 series to get up to speed on the major changes.

I can recommend getting the Base Laravel course here https://baselaravel.com/

If you get stuck on something the community here will do it's best to help you solve the issues you face.

Where ever you defined this

\js\app.js

Try changing it to

/js/app.js

Most likely you have hit the max number of requests within a certain time span. Thus giving you the error.

You can leverage the database for that. Just pass in the country code and the weight and get the cost

Most likely because of this

 name="tool[{{ $key }}]

You have 6 for each tool and you have a a lot of tools to loop over.

Most likely because of this

 name="tool[{{ $key }}]

You have 6 for each tool and you have a a lot of tools to loop over.

@tykus so I noticed when I posted my reply.

If you are using blade you have a index variable you can use.

https://laravel.com/docs/8.x/blade#the-loop-variable

The you can use $loop->index as your row number.

How did you add it? What version of Laravel are you using?

Ask the DBA to increase the amount of connections then.

This might help you https://dba.stackexchange.com/questions/232126/what-settings-control-the-maximum-number-of-connections-per-user-in-oracle-12c

If you store the images on disk it's a bit of waste in bandwidth. Just put them on an S3 bucket and pass along the link and let the frontend people be responsible for the loading of the picture.

The best place to start is always here

https://laracasts.com/series/laravel-6-from-scratch

Then you can move on the the What's new in Laravel 7 and 8.

After that one of the courses using TDD.

Why are you passing the encoded image instead of just the path to the image?

Yes, a roles table is much better practice.

Add this after your query

dd($location); 

Then you will see what is wrong.

Since you get more than one row you need to loop over your collection.

When it comes to validations I usually do something like this

  /**
     * @test
     * @dataProvider storeValidationProvider
     * @param $fieldValue
     * @param $field
     */
    public function store_validation_tests($field, $fieldValue)
    {
        $book = Book::factory()->make([
            $field => $fieldValue
        ]);

        $response = $this->post('/books', $book->toArray());
        $response->assertStatus(302);
        $response->assertSessionHasErrorsIn($field);
    }

    public function storeValidationProvider()
    {
        return [
            'the title is required' => ['title', ''],
            'part must be numeric' => ['part', 'One'],
            'format_id is required' => ['format_id', ''],
            'format_id must exist in formats' => ['format_id', 100],
            'genre_id is required' => ['genre_id', ''],
            'genre_id must exist in genres' => ['genre_id', 100],
            'isbn is required' => ['isbn', ''],
            'invalid isbn10 cant be stored' => ['isbn', '123456789'],
            'invalid isbn13 cant be stored' => ['isbn', '9771234567890'],
            'released is required' => ['released', ''],
            'pages is required' => ['pages', ''],
            'pages must be numeric' => ['pages', 'Ten'],
            'blurb is required' => ['blurb', ''],
            'released cant be earlie than 1800' => ['released', 1799],
            'released cant be later than current year + 1' => ['released', Carbon::now()->addYear(2)->year],
            'reprinted cant be earlier than 1800' => ['reprinted',  1799],
            'reprinted cant be later than current year + 1' => ['reprinted', Carbon::now()->addYear(2)->year]
        ];
    }

So when thisd is 'the title is required' => ['title', ''] then I assert the the title field is in the errors

 $response->assertSessionHasErrorsIn($field);

You don't have php.exe in your path.

https://docs.alfresco.com/4.2/tasks/fot-addpath.html

You don't have php.exe in your path.

https://docs.alfresco.com/4.2/tasks/fot-addpath.html

Is there any specific reason for not using the new html 5 tags instead of using divs in your html?

I think the code becomes much more easy to read when using them.

And why aren't you using a table to display the tabular data in the future weather?

This is your problem

(2020-04-06 12:46:31.000000, 3, UTC)

Since you use in in your query it reads the , as that the next is a new value.

Where is the controller code that creates the query cause there most likely lies the issue.

No issues what so ever found so far.

You need to uninstall Valet and install it again and most likely run

valet use [email protected]

You can always check this link as well

https://github.com/laravel/valet/issues/861

Also try this

brew unlink [email protected]
brew link [email protected]

You mean something like tinymce or ckeditor?

You need to uninstall Valet and install it again and most likely run

valet use [email protected]

You can always check this link as well

https://github.com/laravel/valet/issues/861

Also try this

brew unlink [email protected]
brew link [email protected]

Can you give us the full error message?

If I were you I'd stick to blade where ever I could get away with it and just use javascript where needed.

Are you sure you are running it?

Check your DatabaseSeeder Class that you have the following line

$this->call(ProductVariationsTableSeeder::class);

I bet you will :)

The id will always be a little bit faster since it's numeric and is then "easier" for the database to index and perform searches against. However an indexed slug should not post any major slowdowns in a reasonably large table. There are more ways to handle performance if you have performance issues with a huge table even if it's indexed properly. In that case you can partition the table.

You can also use two fields for uniqueness to help the index along. For a simple blog you could consider using they year + the slug as the unique key.

42

You have two options

1. Don't use json fields in your database for other things than store the payload before parsing it into normal fields in a table.
2. Use a MySQL database for your tests.

I would go with option 1. seven days a week, since a storing json in your database like that defeats the whole purpose of a relational database.

Not sure what you mean?

Are you saying that you want to validate that if a checkbox is checked then a textbox is required?

If so check the rule requiredif

https://laravel.com/docs/8.x/validation#rule-required-if

One option is to use an Artisan command that updates the files/tables you need.

I would add and remove CSS classes with js when the button is clicked. I would do the initial rendering of the class list in my blade template.