On https://docs.spatie.be/laravel-medialibrary/v5/introduction

Hi, thank you for creating nice documentation

upgraded from version 6.0.0

There is no Spatie\MediaLibrary\HasMedia\Interfaces
use Spatie\MediaLibrary\HasMedia\Interfaces\HasMedia;

See #241

Proposal: use another larger test image.
I don't think this is the best example since the difference between sizes 188 - 158 - 132 - 110 is too small.

"PHP " : "7.2.8",
"laravel/framework": "5.8.*",

composer require spatie/laravel-server-monitor:^1.0
./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
- Conclusion: remove symfony/console v4.2.5
- Conclusion: don't install symfony/console v4.2.5
- symfony/process 3.2.x-dev conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.0 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.0-BETA1 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.0-RC1 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.0-RC2 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.1 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.10 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.11 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.12 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.13 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.14 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.2 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.3 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.4 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.5 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.6 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.7 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.8 conflicts with symfony/console[v4.2.5].
- symfony/process v3.2.9 conflicts with symfony/console[v4.2.5].
- Installation request for symfony/console (locked at v4.2.5) -> satisfiable by symfony/console[v4.2.5].
- Installation request for spatie/laravel-server-monitor 1.0 -> satisfiable by spatie/laravel-server-monitor[1.0.0].
- Conclusion: don't install symfony/process v4.2.5|install symfony/process 3.2.x-dev|install symfony/process v3.2.0|install symfony/process v3.2.0-BETA1|install symfony/process v3.2.0-RC1|install symfony/process v3.2.0-RC2|install symfony/process v3.2.1|install symfony/process v3.2.10|install symfony/process v3.2.11|install symfony/process v3.2.12|install symfony/process v3.2.13|install symfony/process v3.2.14|install symfony/process v3.2.2|install symfony/process v3.2.3|install symfony/process v3.2.4|install symfony/process v3.2.5|install symfony/process v3.2.6|install symfony/process v3.2.7|install symfony/process v3.2.8|install symfony/process v3.2.9
- Conclusion: remove symfony/process v4.2.5|install symfony/process 3.2.x-dev|install symfony/process v3.2.0|install symfony/process v3.2.0-BETA1|install symfony/process v3.2.0-RC1|install symfony/process v3.2.0-RC2|install symfony/process v3.2.1|install symfony/process v3.2.10|install symfony/process v3.2.11|install symfony/process v3.2.12|install symfony/process v3.2.13|install symfony/process v3.2.14|install symfony/process v3.2.2|install symfony/process v3.2.3|install symfony/process v3.2.4|install symfony/process v3.2.5|install symfony/process v3.2.6|install symfony/process v3.2.7|install symfony/process v3.2.8|install symfony/process v3.2.9
- spatie/laravel-server-monitor 1.0.0 requires symfony/process ^3.2 -> satisfiable by symfony/process[3.2.x-dev, 3.3.x-dev, 3.4.x-dev, v3.2.0, v3.2.0-BETA1, v3.2.0-RC1, v3.2.0-RC2, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.0-BETA1, v3.3.0-RC1, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.17, v3.3.18, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v3.4.1, v3.4.10, v3.4.11, v3.4.12, v3.4.13, v3.4.14, v3.4.15, v3.4.16, v3.4.17, v3.4.18, v3.4.19, v3.4.2, v3.4.20, v3.4.21, v3.4.22, v3.4.23, v3.4.24, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- Can only install one of: symfony/process[3.3.x-dev, v4.2.5].
- Can only install one of: symfony/process[3.4.x-dev, v4.2.5].
- Can only install one of: symfony/process[v3.3.0, v4.2.5].
- Can only install one of: symfony/process[v3.3.0-BETA1, v4.2.5].
- Can only install one of: symfony/process[v3.3.0-RC1, v4.2.5].
- Can only install one of: symfony/process[v3.3.1, v4.2.5].
- Can only install one of: symfony/process[v3.3.10, v4.2.5].
- Can only install one of: symfony/process[v3.3.11, v4.2.5].
- Can only install one of: symfony/process[v3.3.12, v4.2.5].
- Can only install one of: symfony/process[v3.3.13, v4.2.5].
- Can only install one of: symfony/process[v3.3.14, v4.2.5].
- Can only install one of: symfony/process[v3.3.15, v4.2.5].
- Can only install one of: symfony/process[v3.3.16, v4.2.5].
- Can only install one of: symfony/process[v3.3.17, v4.2.5].
- Can only install one of: symfony/process[v3.3.18, v4.2.5].
- Can only install one of: symfony/process[v3.3.2, v4.2.5].
- Can only install one of: symfony/process[v3.3.3, v4.2.5].
- Can only install one of: symfony/process[v3.3.4, v4.2.5].
- Can only install one of: symfony/process[v3.3.5, v4.2.5].
- Can only install one of: symfony/process[v3.3.6, v4.2.5].
- Can only install one of: symfony/process[v3.3.7, v4.2.5].
- Can only install one of: symfony/process[v3.3.8, v4.2.5].
- Can only install one of: symfony/process[v3.3.9, v4.2.5].
- Can only install one of: symfony/process[v3.4.0, v4.2.5].
- Can only install one of: symfony/process[v3.4.0-BETA1, v4.2.5].
- Can only install one of: symfony/process[v3.4.0-BETA2, v4.2.5].
- Can only install one of: symfony/process[v3.4.0-BETA3, v4.2.5].
- Can only install one of: symfony/process[v3.4.0-BETA4, v4.2.5].
- Can only install one of: symfony/process[v3.4.0-RC1, v4.2.5].
- Can only install one of: symfony/process[v3.4.0-RC2, v4.2.5].
- Can only install one of: symfony/process[v3.4.1, v4.2.5].
- Can only install one of: symfony/process[v3.4.10, v4.2.5].
- Can only install one of: symfony/process[v3.4.11, v4.2.5].
- Can only install one of: symfony/process[v3.4.12, v4.2.5].
- Can only install one of: symfony/process[v3.4.13, v4.2.5].
- Can only install one of: symfony/process[v3.4.14, v4.2.5].
- Can only install one of: symfony/process[v3.4.15, v4.2.5].
- Can only install one of: symfony/process[v3.4.16, v4.2.5].
- Can only install one of: symfony/process[v3.4.17, v4.2.5].
- Can only install one of: symfony/process[v3.4.18, v4.2.5].
- Can only install one of: symfony/process[v3.4.19, v4.2.5].
- Can only install one of: symfony/process[v3.4.2, v4.2.5].
- Can only install one of: symfony/process[v3.4.20, v4.2.5].
- Can only install one of: symfony/process[v3.4.21, v4.2.5].
- Can only install one of: symfony/process[v3.4.22, v4.2.5].
- Can only install one of: symfony/process[v3.4.23, v4.2.5].
- Can only install one of: symfony/process[v3.4.24, v4.2.5].
- Can only install one of: symfony/process[v3.4.3, v4.2.5].
- Can only install one of: symfony/process[v3.4.4, v4.2.5].
- Can only install one of: symfony/process[v3.4.5, v4.2.5].
- Can only install one of: symfony/process[v3.4.6, v4.2.5].
- Can only install one of: symfony/process[v3.4.7, v4.2.5].
- Can only install one of: symfony/process[v3.4.8, v4.2.5].
- Can only install one of: symfony/process[v3.4.9, v4.2.5].
- Installation request for symfony/process (locked at v4.2.5) -> satisfiable by symfony/process[v4.2.5].

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

solved removing version ^1.0 from composer require string

Hey Freek,

Awesome package.

I followed through the Writing your first Projector example. And consistently got the error:

"Return value of App\Account::createWithAttributes() must be an instance of App\Account, null returned"

whilst trying to create a new Account record.

Tracking the issue I could see that:

• stored_events was being populated OK
• projector_statuses was set as has_received_all_events = 0 (false)
• no account was being created

The event was firing fine but something was causing a null return in the projector.

However, at the same time I downloaded the example project and that worked fine. So I went through and compared line by line.

As soon as I added

   public function streamEventsBy()
    {
       return 'accountUuid';
    } 

to my projector, the example worked and I could create accounts as per the example.

I am not sure if I missed something in the example, in how the package can work without streamEventsby(). I read the Using event streams page and it seemed to suggest this was something additional rather than required?

Anyway, posting here in case anybody else has the same issue whilst following the example.

Luke

Browsing the documentation I noticed that you have two different interfaces available to apply, but there is no place pointing out the difference.

Without conversions

use Spatie\MediaLibrary\HasMedia\HasMediaTrait;
use Spatie\MediaLibrary\HasMedia\Interfaces\HasMedia;

class NewsItem extends Model implements HasMedia
{
    use HasMediaTrait;

Using conversions

use Spatie\MediaLibrary\HasMedia\HasMediaTrait;
use Spatie\MediaLibrary\HasMedia\Interfaces\HasMediaConversions;

class NewsItem extends Model implements HasMediaConversions
{
    use HasMediaTrait;

    public function registerMediaConversions()
    {
        $this->addMediaConversion('thumb')
             ->setManipulations(['w' => 368, 'h' => 232])
             ->performOnCollections('images');
    }

Maybe even in the preparing-your-model section, just point out that if you plan on using conversions, that you should read the alternate page at converting-images/defining-conversions.

IP 46.101.151.54 (docs.spatie.be) blocked in Russia.
Therefore, the documentation in Russia is not available.

I am sure this is an accident. Just decided to let you know that there is such a problem.

You can check here: https://isitblockedinrussia.com/?host=https://docs.spatie.be

I'm not sure if the code sample for multiple file downloads is correct or not, would you give it a look please: https://github.com/spatie/docs.spatie.be/blob/master/resources/views/laravel-medialibrary/v7/downloading-media/downloading-multiple-files.md

$mediaItem / $media / $yourModel / $allMedia

Thanks for the great package 👍

Go here: https://docs.spatie.be/image/v1/image-manipulations/overview

Scroll down to Watermarks and click any link; results in 'Docs not found'

https://docs.spatie.be/image/v1/image-manipulations/watermark

hi spatie-team,

thaaaaaaaaank you for all of your great work (postcard is in progress).

https://docs.spatie.be/laravel-medialibrary/v5/advanced-usage/overriding-default-filesystem-behaviour

The link above is a dead link but it is linked in the right navigation.

greetings Marv =)

Could use a pretty 404 page!

With this in place only a projector will save state. The BrokeReactor will only send out a mail when an account goes broke. No mails will be sent if the account was already broke. When the account goes above zero and goes broke again a new mail will be sent. When replaying all events, no mail will get sent, but all account state will be correct.

Is this correct when you rebuild the account? When deleting an account and replaying all events that end up with a negative balance the broke_mail_sent bool will be false, assuming that's the default value. Reactors aren't called after all and thus the the bool value will never be set to true.

I needed to add custom propeties after the media has been saved, and i find that the method $media->getMedia() from the example does not exists instead i used $media->media.

Alsoe to persiste the properties to DB after calling $media->setCustomPropery() i needed to do $media->save()

I think it's nice to point to this in the doc.

Hello guys, please take a look when you have a time

I'm also wondering, is there any possibility to resize/crop a particular file on the fly before/after adding to a media collection?

Something like

$media = $model->addMedia($request->file('form_files.0'))
    ->crop($request->left, $request->top, $request->width, $request->height)
    ->toMediaCollection('avatars', 'avatar')
;

(Sorry I should have to ask it separately probably)

On the menu example page on the introduction document, there is a sample showing ->add(Link::to(x, y)) syntax as an alternative to ->link(x, y). When I try to use the former in a blade PHP template (within {{ }}), I get an error that the Link class is not found (I am using a "laravel new app" application and did require spatie/menu and spatie/laravel-menu. If I explicitly call it with ->add(Spatie\Menu\Link::to(x, y)), then it works.

Am I doing something wrong that this namespace isn't present automatically? Is this expected? Or outdated doc?

A new package called laravel-activitylog will be released soon. The extensive docs will be published on this site. I've already set up one page based on the medialib layout.

Could you make a new colorscheme for the docs of this package?