Tray2

so something like this then?

SELECT * FROM table1
UNION ALL
SELECT * FROM table2

Wohoo! I stole one from the all mighty @sinnbeck and that my friends is a big achievment :)

I agree with @sinnbeck that you should use a symlink to acheive that.

Other than that something like

$path = base_path() . '/../../';

migth work.

While you upload is a bit tricky since it requires certain software installed on the users computer.

However you can use ffmpeg to get loads of information after the upload is done.

https://github.com/PHP-FFMpeg/PHP-FFMpeg

You can of course do it from the command line as well and not use the library.

Here is a little script that I made a while back that takes all the media files in a directory and recodes them at a lower resolution.

<?php
  $dir = $argv[1];
  $list = $argv[2];
function getDirContents($dir, &$results = array()){
    $files = scandir($dir);

    foreach($files as $key => $value){
        $path = realpath($dir.DIRECTORY_SEPARATOR.$value);
        if(!is_dir($path)) {
            $results[] = $path;
        } else if($value != "." && $value != "..") {
            getDirContents($path, $results);
            $results[] = $path;
        }
    }

    return $results;
}

function getMediaFiles($contentList)
{
	$allowedTypes = ['mpg', 'mp4', 'mkv', 'flv', 'mov', 'mpeg', 'avi', 'wmv'];
	$mediaFiles = [];

	foreach($contentList as $row) {
		if(is_file($row)) {
			$extension = pathinfo($row, PATHINFO_EXTENSION);
			if(in_array($extension, $allowedTypes)) {
				$mediaFiles[] = $row;
			}
		}
	}

	return $mediaFiles;
}

function getMediaFilesToResize($mediaList)
{
	$mediaToResize = [];
	foreach($mediaList as $row) {
		$command = 'ffmpeg -i ' . str_replace(' ', '\ ', $row) . ' 2>&1 | grep Video: | grep -Po \'\d{3,5}x\d{3,5}\' | cut -d\'x\' -f2';
		$height = (int)exec($command);
        if ($height > 720) {
            $mediaToResize[] = $row;
        }
	}
	return $mediaToResize;
}

function startResize($mediaToResize)
{
	$num = 1;
	$total = count($mediaToResize);
	$originalSize = 0;
	$newSize = 0;
	
	foreach($mediaToResize as $row) {
		$extension = pathinfo($row, PATHINFO_EXTENSION);
		$filename = trim(str_replace(' ', '_', basename($row, $extension)), '.');
		echo "Processing file $num of $total\n";
	    echo "Starting conversion of $filename\n";
		$originalSize += filesize($row);
		$command = 'ffmpeg -loglevel quiet -stats -i ' . str_replace(' ', '\ ', $row) . ' -vf scale=1280:720 ' . str_replace(' ', '\ ',pathinfo($row, PATHINFO_DIRNAME)) .'/' . $filename . '-720p.' . $extension;
		exec($command);
		unlink($row);
		$newSize += filesize(pathinfo($row, PATHINFO_DIRNAME).'/' . $filename . '-720p.' . $extension);
		$num++;
		echo "Done processing $row!\n";
	}

	return ['old_size' => $originalSize, 'new_size' => $newSize];
}

function getEarnedSpace($result)
{
	return round(($result['old_size'] - $result['new_size']) / 1024 / 1024 / 1024, 3);
}

function main($dir, $list = null)
{
	$files = getDirContents($dir);
	$mediaFiles = getMediaFiles($files);
	$mediaToResize = getMediaFilesToResize($mediaFiles);
    if ($list == null) {
        $result = startResize($mediaToResize);
        $freedSpace = getEarnedSpace($result);
        echo "Conversion Finshed\n";
        echo "You have freed up $freedSpace Gb of space on your harddrive\n";
    } else {
		print_r($mediaToResize);
	}
}

main($dir, $list);

Usually it's good to add another join condition to the query but that depends on how the tables look and what the expected result is.

That is why I asked you to share the generated sql.

I'm not a big fan of the "new" join syntax, I prefer doing then the old fashioned way in my SQL.

This part looks like an unconditional join to me

->join('category_product', function($join) {
		$join->on('category_product.product_id', '=', 'manufacturer_product.product_id')
			->where('category_product.category_id', '=', $this->id);

You probably need to add some conditions to it

->join('category_product', function($join) {
		$join->on('category_product.product_id', '=', 'manufacturer_product.product_id')
			->where('category_product.category_id', '=', $this->id)->on(<condition here>);

Mark the answer that helped you as best :)

You have something called a cartesian product there.

It means that one of your joins gets joined in 1 to all instead of 1 to 1.

Look att the genereated sql from the code below.

dd( Manufacturer::select('manufacturers.*')
	->withTranslations( LanguageHelper::getLangId() )
	->with('image')
	->join('manufacturer_product', 'manufacturers.id', '=', 'manufacturer_product.manufacturer_id')
	->join('category_product', function($join) {
		$join->on('category_product.product_id', '=', 'manufacturer_product.product_id')
			->where('category_product.category_id', '=', $this->id);
	})->toSql());

Thank m8 :) There will be cake today ;)

Since you pull the record from the database you only need to update it if a file has been provided

if ($request->hasFile('logo')) {
    //Do the stuff here to update the image
}

If it has no image provided it will use the one you alredy got.

Distinct should be avoided if possible.

However what do you mean by two query responses?

Are the tables related like author and book or is it more like authors and artists and you want to list both the artists and the authors with one query?

A components table perhaps

• id
• name
• tag

Where the tag is the <x-component />

You could also have a componen_parameters table where the parameters that can be passed to the component

• id
• component_id
• parameter
• default_value

@sinnbeck I appriciate that :)

Yes

'logo' => 'image|max:512|nullable',

But I prefer to have this order instead

'logo' => 'nullable|image|max:512',

But that is just my preference.

Stealing my thunder again I see ;p

I'm just starting to learn about docker for laravel but I really recommend this course on it.

https://gumroad.com/l/cwYKw

It covers a lot on developing and on deploying to production

You can use nullable in your validation rule.

Make sure to only update the value if a file is present.

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

A components table perhaps

• id
• name
• tag

Where the tag is the <x-component />

You could also have a componen_parameters table where the parameters that can be passed to the component

• id
• component_id
• parameter
• default_value

I agree with @sinnbeck that you should use a symlink to acheive that.

Other than that something like

$path = base_path() . '/../../';

migth work.

I'd say it's a many to many in this case.

If you have a pages table and a components table you create a component_page pivot table.

Then you take your page and attach the components

$page->attach($component->id);

More info can be found here

https://laravel.com/docs/8.x/eloquent-relationships#updating-many-to-many-relationships

I would use this kinds of database model

• products
• material_units
• material_unit_contents

The product contains the information about the product such as part number, color, title, type and such. The material unit contains information about where it is and when it was created/recieved from the supplier. The material_unit_contents connects the product with the material unit. It has the current stock of that material unit.

So a product can have many material units through the material unit contents. By doing it this way you can have the quantity in different formats.

Let's say that you have two products.

Product 1 is a graphics card and you have ten pieces in two different material units. Product 2 is a network cat6 cable the you cut the length the customer wants.

You can use the same structure and you put a meassure of unit in the product table and the unit for the graphic cards can be pcs and the network cable cm.

You should also create a table for the measure_of_units so you can put a constrint on it in the products table.

When you sell a graphics card you decrease the quantity in the material_unit_contents table for the oldest material unit. unless of course you implement scanning of the material unit number you pick from.

Have you installed SQLite 3?

The easiest way is to create a spinner

<section id="loading">
    <div id="loading-content"></div>
</section>

.loading {
	z-index: 20;
	position: absolute;
	top: 0;
	left:-5px;
	width: 100%;
	height: 100%;
    background-color: rgba(0,0,0,0.4);
}
.loading-content {
	position: absolute;
	border: 16px solid #f3f3f3; /* Light grey */
	border-top: 16px solid #3498db; /* Blue */
	border-radius: 50%;
	width: 50px;
	height: 50px;
	top: 40%;
	left:35%;
	animation: spin 2s linear infinite;
	}
	
	@keyframes spin {
		0% { transform: rotate(0deg); }
		100% { transform: rotate(360deg); }
	}

function showLoading() {
  document.querySelector('#loading').classList.add('loading');
  document.querySelector('#loading-content').classList.add('loading-content');
}

function hideLoading() {
  document.querySelector('#loading').classList.remove('loading');
  document.querySelector('#loading-content').classList.remove('loading-content');
}

You can create a component for each section using blade components.

https://laravel.com/docs/8.x/blade#components

in your page you just include the component

<x-compoent />

And pass the desired data to them

<x-component :message="$message"/>

Something like this should work when creating.

/**
 * @test
 */
public function when_validation_fails_old_values_are_show,()
{
    $this->signIn();
    $artist = Artist::factory()->make(['name' => '']);

    $response = $this->post('/artists', $artist->toArray());

    $response->assertSee($artist->dob);
}

And something like this in updating

/**
* @test
*/
public function old_value_is_shown_when_validation_fails()
{
    $this->signIn();
    $artist = Artist::factory()->create();
    $artist->name = '';
    $this->patch('/artists/' . $artist->id, $artist->toArray());
    $this->assertSee($artist->dob);
}

If you still are in the development stage (not having put it to production) update the migrations instead of adding new ones.

Since there is no before option in SQL it's kinda tricky to acheive but since you should now the column before you should be able to use that.

From https://www.mysqltutorial.org/mysql-add-column/

Third, MySQL allows you to add the new column as the first column of the table by specifying the FIRST keyword. It also allows you to add the new column after an existing column using the AFTER existing_column clause. If you don’t explicitly specify the position of the new column, MySQL will add it as the last column.

Not sure exactly what it is you want but something like this adds and removes rows in a html table.

<table>
<thead>
<tr><th>Field</th><th>Delete</th></tr>
</thead>
<tbody id="the-body"></tbody>
</table>

<button onclick="addRow()">Add</button>

let rows = 0;

function addRow() {
  rows++;
  const el = document.querySelector('#the-body');
  el.innerHTML += `<tr><td>${rows}</td><td><button onclick="deleteRow(event)">x</button></td></tr>`;
}

function deleteRow(event) {
	event.target.parentNode.parentNode.remove();
}

The naming convention for field names is catalog_number, I agree that it looks a bit of when you use camelcase in you variable and method names but it's there for a reason. SQL doesn't really care about the case so ´catalogNumberandcatalognumber` is the same thing most of the time. In some databases there is a difference when you create a table depending on if you use quotes or not which can lead to strange issues later on. So stick with lowercase letters and seperate the words with an underscore to avoid later headaches.

In your form you put a name to the input

<input type="text" name="title">

That name becomes the property used to access the value sent to the server.

You can access it like this

$request->title

Everything should be validated so you can do this

$validData = $request->validate(['title' => 'required']);

Then you need to create the record in the database which you can do like this

Model::create($validData);

The validation can be inlined like this

Model::create($request->validate(['title' => 'required']));

There are more than one way to do the above but that is one way to do it.

You need to allow for massassignment in your model and there are several ways to do that but since you are a good programmer and validate everything you can get away with

protected $guarded = [];

Which means you can assign all fields in the table.

The section above in the docs perhaps.

https://laravel.com/docs/8.x/session#storing-data

https://laravel.com/docs/8.x/session#pushing-to-array-session-values

I take it you get the data from a database.

I suggest you filter it down there with a group by or in worst case a distinct.

If you are using SQLite make sure you have enbled foreign key constraints.

Not sure but shouldn't item be items on this line

return view('livewire.shoppingcart', ['item' => $this->Items]);

Sounds a bit more like SBTW rather than an error on your side.

You should checkout scopes for that.

https://laravel.com/docs/8.x/eloquent#query-scopes

Are you redirecting back or to the url?

Since just redirecting back doesn't always update, it uses the cached page.

Lots of things can be wrong. Without more information it's impossible to help you.

I take it you want to use laravel on a server that is not connected to the internet.

This guide will help you get up and running with the server and laravel. https://www.howtoforge.com/tutorial/install-laravel-on-ubuntu-for-apache/

You will need internet access to set it up but after that you can disconnect it from the internet.

Yes it caches some of the get requests like files and such but rest services are not cached in that way.

In my opinion it's not a good idea to use the same method for both updating and creating. However createOrUpdate is the one you can use.

https://laravel.com/api/8.x/Illuminate/Database/Eloquent/Builder.html#method_updateOrCreate

The only affect it will have is that the first request will take a tiny bit longer.

Looks like you are hardcoding a path to where the logs are supposed to go somewhere in your settings.

"C:\wamp64\www\lms\storage\logs

I would check the .env file first.

This is most likely the issue.

"catalogNumber" => "123456"

it should be

"catalog_number" => "123456"

When naming fields in the database the words are seperated with an underscore.

Make sure the name of the field in your migration is catalog_number and that you have made the change in your form, validation and store method.

@jlrdw you might wanna check out Develop And Deploy Laravel Applications With Docker by https://twitter.com/aschmelyun.

https://gumroad.com/l/cwYKw

I watched the four or five first lessons and so far it looks really good.

Linux loves symlinks and they are good in *nix systems but on windows it better to copy the file to where it's supposed to be.

Yes it's Linux only but the part about the virtual host setting are still valid. You need to change some paths other than that you should be good.

Couldn't find a good one for windows though.

This line like I said in my previuos comment

$data = base64_decode($base64_str);

Yes it's Linux only but the part about the virtual host setting are still valid. You need to change some paths other than that you should be good.

Couldn't find a good one for windows though.

This line like I said in my previuos comment

$data = base64_decode($base64_str);

Are you storing these products in the database?

If so always harness the power of the database to filter your data.

$products = Product::whereNotNull('category_id')->get();

When it comes to limiting the columns in your result use the database.

$products = Product::whereNotNull('category_id')`->pluck('weight');

Have you checked that your global composer.json file don't have the php-cs-fixer in it still?