Tray2

That was exactly what I was refering to when I menat that the security is the tricky part :)

Yes, but which of the ones do you get duplicates from?

You really should TDD this stuff.

You should use TDD to do it.

An application like that isn't really that complex to build.

You need a media host that handles the streaming with a shitload of bandwidth and discspace.

The rest is a regular CRUD application for the web and a app for iOS, Android and all the Smart-TV brands out there.

Then you need to handle security to prevent downloading of the movies which hopefully the media host can provide. Then you need to handle subscriptions and max no of connections per user and so on. The payment you can handle with cashier. With Jetstream you have a lot of user handling built in.

The security will be the trickiest part.

That is incorrect.

this is allowed.

SELECT p.* 
FROM products p 
WHERE p.description like 'E%'

What they are refereing to is a query like this

SELECT title, count(*) AS quantity
FROM products
WHERE quantity = 10 
GROUP BY title

Then you are not allowed to use the alias in the where clause.

Change this

  foreach ($no as $idnx) {
                $noo = (int) $idnx->bill_no;
            }

            $tambah = $noo + 1;

To this

  $tambah = (int) $no->bill_no + 1;

Now which path does it take in the if statement?

 if ($request->slave_ID) {
      foreach ($request->slave_ID as $key => $value) {
        $data['slave_id'] =$request->slave_ID[$key],
        Sales::create($data); 
      }

    }else{
      $data['slave_id'] = ($request->has('slave_ID') && count($request->slave_ID) > 0)? count($request->slave_ID) : null;
      Sales::create($data); 
    }

Ah duplicates in the database I thought it was duplicate code.

Anyway my code made it cleaner :)

So what you want to do is pad the bill_number.

E210120210001
E210120210099
E210120210999
E210120211001
E210120211002

You can use str_pad for that

$bill_number = 'E' . Carbon::now()->format('dmy') . str_pad($tambah, 4, '0', STR_PAD_LEFT);

Instead of using the if statement.

This is probalby the issue

 $no = DB::select("SELECT max(right(bill_number,4)) as bill_no from sales WHERE date(updated_at)='$tgl'");

It will select the higest value in the last four characters in the bill_no. and nothing else.

So if its 0099 that is the highest it will fetch that.

So there is no need to loop over it.

Something like this

 $no = DB::select("SELECT max(right(bill_number,4)) as bill_no from sales WHERE date(updated_at)='$tgl'");
      
 $noo = (int) $no->bill_no +1;

Not really but all of that is doable in SQL.

Where do you get the data from?

If it's the database you should do the calculation and the sorting there.

What browser are you using?

There was another type-o in the else statement it said

Sales::create($data2);

It should be

Sales::create($data);

It should be $data I updated my reply.

A simple solution would be to always assign the common stuff then the parts that differs with slight duplication.

Something like

  $tgl = Carbon::now()->format('Y-m-d');
      $no = DB::select("SELECT max(right(bill_number,4)) as bill_no from sales WHERE date(updated_at)='$tgl'");
      foreach ($no as $idnx) {
          $noo = (int) $idnx->bill_no;
      }

      $tambah = $noo + 1;

      if ($tambah < 10) {
          $bill_number = "E" . Carbon::now()->format('dmy') . "000" . $tambah;
      } else if ($tambah < 100) {
          $bill_number = "E" . Carbon::now()->format('dmy') . "00" . $tambah;
      } else if ($tambah < 1000) {
          $bill_number = "E" . Carbon::now()->format('dmy') . "0" . $tambah;
      } else if ($tambah < 10000) {
          $bill_number = "E" . Carbon::now()->format('dmy') . $tambah;
      }

      $data =[

          'bill_number'       =>     $bill_number,
          'user_id'     =>    Auth::user()->id,
          'tag_id'      =>    Auth::user()->team_id,
          'unit_issue_id'     =>    $request->unit_id,
          'customer_agent'      =>    $request->customer_agent,
          'payment_method'      =>    $request->payment_method,
          'borderName'      =>    $request->borderName,
          'tag_area'      =>    $request->tag_area,
          'cargo_type'      =>    $request->cargo_type,
          'chasisNo'      =>    $request->chasisNo,
          'ITNo'      =>    $request->ITNo,
          'driverName'      =>    $request->driverName,
          'License'     =>    $request->License,
          'driverPhone'     =>    $request->driverPhone,
          'subT1'     =>    $request->subT1,
          'TruckNo'     =>    $request->TruckNo,
          'TrailerNo'     =>    $request->trailerNo,
          'container_no'      =>    $request->containerNo,
          'comments'      =>    $request->comment,
          'amount'      =>    $request->amount,
          'discount'      =>    $request->discount,
          'sale_type'     =>    $request->sale_type,
          'currency'      =>    $request->currency,
          'created_at'=>$date,
        ];


      if($request->filled('backdate')) {
                    $date = request('backdate');
                } else {
                    $date = Carbon::now()->format('Y-m-d H:i:s');
                }
    if ($request->slave_ID) {
      foreach ($request->slave_ID as $key => $value) {
        $data['slave_id'] =$request->slave_ID[$key],
        Sales::create($data); 
      }

    }else{
      $data['slave_id'] = ($request->has('slave_ID') && count($request->slave_ID) > 0)? count($request->slave_ID) : null;
      Sales::create($data); 
    }
return $this->print_sales_bill_cash($bill_number);

This was the case as well with a thread where the OP was named "David Something" (not really something but anyways) and when trying to tag the OP the tagged became another user that had the name "David".

I think it's more or less impossible to handle this in the @ functionality and I think it's better to not allow spaces in the names.

In this store method I update four tables

  $bookData = $request->validated();
  $book = Book::create($bookData);
  $book->addAuthors($request, $book);
  $book->addToCollection($book);
  $book->markAsRead($request, $book);

The book is the one I validate then I send the book and the request onto the add authors method and so on. I've placed these additional methods in the Book model. You can of course place them on their own model but I wanted to KISS.

public function addAuthors(BookFormRequest $request): void
    {
        if (isset($request->additional_authors)) {
            $authors = array_merge([$request->author_id], $request->additional_authors);
        } else {
            $authors = [$request->author_id];
        }
        foreach ($authors as $author) {
            AuthorBook::create([
                'author_id' => $author,
                'book_id' => $this->id
            ]);
        }
    }

What do you mean by deploy app.php?

Are we talking a laravel project, a single app.php file or something totally different?

Check this guide, it says Ubuntu but ubuntu is based on debian.

https://www.howtoforge.com/tutorial/install-laravel-on-ubuntu-for-apache/

Open a new thread and ask your question. Supply information about your tables and the code used to fetch the data. Then we should be able to help you.

I suggest you check out this course when it comes to laravel and docker.

https://laraveldocker.com/

Create stores it in the database you should use make instead.

I recommend using a dataprovider it makes it must cleaner

   /**
     * @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', ''],
        ];
    }

I would go with

/shoes  (index)
/shoes/black-slippers (show)

You can use a middleware to protect your routes or you can use a gate

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

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

You could assert that you location is your dashboard.

I would use Dusk or Cypress to test it though.

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

https://www.cypress.io/

I would most likely move the staff specific data to it's own table and then you can easily check if the user id exists in the staffs table.

You should ony have one user table and then you set the type of user or a user role.

Couldn't have said it better myself :)

So let me get this straight. You want to mark the input red if the user inputs a value that is not a date like 2020-01-35?

I would store a timestamp instead of a boolean.

You can use a middleware to protect your routes or you can use a gate

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

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

It's always easier if you show us your migrations, your data and the expected result.

I would go with a regular <input type="text" name="tags"> and have the user seperate them with a ,.

Then I would explode and trim them into an array in the store method.

If you solved the issue please mark the answer that helped you as best.

As a rule of thumb, Never pull more out of the database than you need.

So if you have one table containing lots of columns then you shouldn't just do

Model::where('field', $value)->get();

You should tell it which columns to fetch for you

Model::where('field', $value)->get(['field1', 'field3', 'field6');

However you also need to consider that if one of the fields are a clob or a blob then you probably benefit by moving it to another table.

I like to think of groups when it comes to how I divide my tables.

Let's say that you have a users table that is used for authentiction and stores the users profile. then it might be a good idea to create a profiles table to store the profile specific information.

It all depends like mentioned before, how static is the table, what kind of data is stored, how many records the database contains and how many users.

In your case I probably stick with one table for the activity and then check for repetition of data in the table.

If you notice something like this it's probably a good idea to extract the activity

title   | location_id
Horseback riding | 1
Horseback riding | 2

And make it

activity_id   | location_id
1 | 1
1 | 2

With a union I would still use id but add a virual column of type or origin so I know which table it comes from.

SELECT id, title, 'books' as origin
FROM books
UNION ALL 
SELECT id, title, 'movies' as origin
FROM movies

Your code makes no sense at all. What is it you are trying to do?

If I have to guess this is what you are looking for

$users = User::whereIn('id', [1, 2, 3])->get();

Or

$users = User::where('id', <= 3)->get();

Are you talking about unsetting the data in the after the return in your controller?

That is not possible to do since you returned.

You might be able to force a gc to run directly in your view by calling gc_collect_cycles(). Don't know though if it cleans a bit too much.

On the other hand your security team doesn't seem to know their drill so to speak. Regular gc is quite enough to handle this safetly.

If you have a collection of arrays/collections you can do something like this

$filtered = $books->filter(function($value, $key) {
	if($value['title'] == 'The Great Hunt') {
		return $value;
    }
});

That will give you all the books with the title of The Great Hunt.

I take it you are getting the data you want to filter from the database? Then you should let the database do the filtering since it's way faster and uses way less resources.

If you have a collection of arrays/collections you can do something like this

$filtered = $books->filter(function($value, $key) {
	if($value['title'] == 'The Great Hunt') {
		return $value;
    }
});

That will give you all the books with the title of The Great Hunt.

I take it you are getting the data you want to filter from the database? Then you should let the database do the filtering since it's way faster and uses way less resources.

You need to assign the filtered values to something.

$filtered = $collection->filter(function ($value, $key) {
    return $value > 2;
});

https://laravel.com/docs/8.x/collections#method-filter

You can use the Auth::id() in your controller or the $request->user()->idto get the logged int user id.

Then you can determine if the user can update or not.

You can use the Auth::id() in your controller or the $request->user()->idto get the logged int user id.

Then you can determine if the user can update or not.

Either you don't pull both from the database by adding the fields you want in a pluck or get or you give it an alias.

I would go with the first option

Location_assignment::where('customer_id', $id)->join('tenants', 'location_assignment.tenant_id', '=', 'tenants.id')->where('position','=','Doctor')->get(['<table.field>','<table.field>' ]);

With the additional fields.

This is an example:

Book::get(['books.title', 'books.pages']);

The result

[!] Aliasing 'Book' to 'App\Models\Book' for this Tinker session.
=> Illuminate\Database\Eloquent\Collection {#2080
     all: [
       App\Models\Book {#2081
         title: "The Eye Of The World",
         pages: 814,
       },
       App\Models\Book {#2082
         title: "The Great Hunt",
         pages: 70,
       },
       App\Models\Book {#2083
         title: "A Memory Of Light",
         pages: 700,
       },
       App\Models\Book {#2084
         title: "Pawn Of Prophecy",
         pages: 304,
       },
     ],
   }

You could assert that you location is your dashboard.

I would use Dusk or Cypress to test it though.

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

https://www.cypress.io/

Where do you order it?

In the query to the database or somewhere else?

What OS are you running on your local machine?

Sure, here's one

https://laracasts.com

You can use whatever you like on your frontend, nobody forces you to use anything.

Vue is very good but it takes some time to learn it. The same goes for any other Javascript framework.

Don't bash the developer of something just because you don't have the knowledge yet how to use it. I really dislike jQuery but I would never state that some developer is better than the people developing it are. jQuery served it's purpose well in the past since it made stuff easier when dealing with inconsistant browsers.

The thing about newer JavaScript frameworks is that they require some new ways of working rather than just pulling in a javascript file from a CDN.

I believe this course is free and I suggest you watch it and Vue might no longer be the pain in the ass you describe.

https://laracasts.com/series/learn-vue-2-step-by-step

Like they do here

https://laravel.com/docs/8.x/authentication#logging-out

You can use signed urls

https://laravel.com/docs/8.x/urls#signed-urls

You need a label for each checkbox.

https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_type_checkbox

@foreach($permission as $value)
    <label class="checkbox-inline">{{ $value->name }}
    <input type="checkbox" name="permission[]" class="form-control name" value="{{$value->id}}" 
   @if($role->permissions->contains($value->id)) 'checked' @endif>
</label>                                    
@endforeach

You need a label for each checkbox.

https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_type_checkbox

@foreach($permission as $value)
    <label class="checkbox-inline">{{ $value->name }}
    <input type="checkbox" name="permission[]" class="form-control name" value="{{$value->id}}" 
   @if($role->permissions->contains($value->id)) 'checked' @endif>
</label>                                    
@endforeach

Something like this should work.

$ids = [];

foreach($values as value) {
 $ids[] = value['id'];
}

However if you are fetching from the database to something like this

$ids = Model::get('id');