Since the latest update from v2 I get this errors:

Internention\Image\Exception\NotSupportedException · GET /img/photos/_270_2101912-Foobarjpg_5735a2cb3519a
Driver () could not be instantiated.

Hi, first of all thanks for your package.

I published the config and modified it to adjust to my project, but when I inspect the HTML I see the glide is generating the URL pointing to img, also it can't process a load('folder/img.jpg'), it transforms to folder%2Fimg.jpg.

Do you know how can I solve those problems?

Thanks!

Hi I Just Downloaded This package and It's not woking I thing many files are missing:

I did all this : composer require spatie/laravel-glide And configuration also,

but in the vendor I can't see where is the route config even the laravel-glide.php is empty just the driver gd

I can't see al that config when published. What IM doing wrong ?

So I followed all the steps and the image is loaded but with original dimensions.

All my images are in the public folder and from what I can see using a debugger in the GlideServiceProvider, the router is not working. Maybe because my images are not in the storage folder?

Hey @freekmurze, thanks so much for putting this library together. I just wanted to let you know that I just released Glide version 0.3.0. I'll be honest, this release has many breaking changes from version 0.2.x. I apologize for that, but I did want to make all significant changes prior to an eventual 1.0 release. You can find the changelog here.

I will note that I designed version 0.3.0 with Laravel 5 in mind. In fact, Taylor was even kind enough to accept a tweak to the new filesystem adapter in Laravel 5 to to allow access to underlying Flysystem driver. This allows you to use the already configured Flysystem instance with Glide. Here is a rough example:

$this->app->singleton('League\Glide\Server', function ($app) {

    $filesystem = $this->app->make('Illuminate\Contracts\Filesystem\Filesystem');

    return League\Glide\ServerFactory::create([
        'source' => $filesystem->getDriver(),
        'cache' => $filesystem->getDriver(),
        'source_path_prefix' => 'path/to/source/images',
        'cache_path_prefix' => 'path/to/image/cache',
    ]);
});

Laravel 5 was also a big reason why I added the new source_path_prefix and cache_path_prefix options. Normally you would just set this when create your Flysystem objects, but since you only have one instance available in Laravel 5 you need a way to set the source and cache paths at the Server level.

You'll also notice that I rearranged the folder structure significantly in this version as well, so there are a bunch of new class names and namespaces. This was a bit painful, but I think it was a good move thinking long term.

Just thought I'd touch base and bring you up to speed on all this! :)

Hello again! You've mentioned in a readme, that were planning at some point to add other disk drivers support, would +1 an S3 please. We have common "file uploads" going to/serving from s3, but images that require Glide cropping and so on are still on local disk, ideally would like to move all the uploads to Amazon. Not sure though about the best practices regarding cache for example. Have seen a few stackoverflow questions/discussions on having originals on s3, cache on local or disabling cache completely and just serving from s3...

Immediatly after install I get the following error when testing in my routes.

FatalErrorException in Facade.php line 218:
Call to undefined method Spatie\Glide\GlideImage::create()

I followed the installation instructions, any idea what I might be doing wrong?

Hi,

In v2 I did things like:

return GlideImage::load($this->avatar, 
         ['w' => 100, 'h' => 100, 'fit' => 'crop'])->getURL();

But I wanna upgrade to v3, but how to achieve the same? I found out that I had to add the storage_path to the load, but the getURL returns Fatal error: Call to undefined method Spatie\Glide\GlideImage::getURL()

return GlideImage::create(storage_path('app/images/'.$this->avatar), 
     ['w' => 100, 'h' => 100, 'fit' => 'crop'])->getURL();

As far I could see it wasn't possible to use load() anymore, but the docs still shows it: https://www.dropbox.com/s/3vbc6d1fd8lch2n/Schermafdruk%202016-02-12%2020.25.12.png?dl=0

I am trying to add a watermark to my image:

$this->addMediaConversion('large')
    ->setManipulations(['fm' => 'jpg', 'mark' => 'watermark.png', 'markw' => '40', 'markh' => '40', 'markpad' => '15', 'markpos' => 'top-left'])
    ->performOnCollections('images');

Following the Glide doc (http://glide.thephpleague.com/1.0/api/watermarks/) I added a new filesystem for watermarks, in the laravel's config/filesystems.php file.

However, my generated thumb doesnt have any watermark on it. And there is no log error report.

Where should I place my watermark.png file ? I tried in storage/images and storage/watermarks and even modifying 'mark' => storage_path('images/watermark.png') but I can't get it working.

Packagists show ~14k installs for this package. I'm with a small web-app firm (4 people), and we simply have too much old sites running to port everything to php 7. We'll get there in about 1 year I guess, we have 120 sites running (low traffic).

Our new system is built upon Laravel 5.1, and we like to keep up with new development now. However, getting our vps to php 7 is simply not an option in the nearby future.

We really like this package, and would like to continue using it. I've read tons on the cool new stuff in 7, but for a big package breaking with many people seems like a bad plan!

There is the option of maintaining two branches at the same time. With the Python 2/3 problems, lots of big libraries have tried really hard to be compatible with 2.X and 3.X , none of the big ones did complete dropping of 2.X

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 8.x.

Before merging, you need to:

• Checkout the l8-compatibility branch
• Review all comments for additional changes
• Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.