Ben

Results 32 comments of Ben

If you look inside the public folder is the storage symlink linked correctly? Otherwises create it manually eig `ln -s /home/cpanel_username/project_name/storage/app/public /home/cpanel_sername/project_name/public/storage` But it's more of a Laravel setup issue...

Wouldn't of thought this was a Voyager issue. But you can easily change the CLI php version and switch it back after: `sudo update-alternatives --set php /usr/bin/php7.3`

Can only see part of the backtrace. How are you uploading the photo? Bread or media manager. Also check folder write permissions: /storage/app/public

Yes I wanted the validation of the file to be optional. E.g if there's no file passed it will be null and json coding not needed.

It would be amazing to have this I've just had to do it manually to save the clases getting stripped.

I have tested on IE8 on windows XP and also using browserstack using IE8 both work fine when clicking on the image

Just remove these 2 lines from the plugin because they are not used.

@Log1x I've pushed a couple of commits you can review. Adding `$wire.set` to manually push the changes fixed the issue you were having.

I can't reproduce the flickering but I think the hidden input can be removed now it's manually being set from `$wire.set`

Already [fixed in pull request](https://github.com/abrigham1/laravel-email-exceptions/pull/16) just needs tagging as a new version for packagist. For now you can edit composer.json manually: `"abrigham/laravel-email-exceptions" : "dev-master"` Ensure you have: `"minimum-stability": "dev",`