Finally solved. After looking through the logs, 'vat_id' was throwing an error. I removed this from validation and it resolved the issue. Thank you for your help.
As soon as I place this in the booted method of SparkServiceProvider, it throws an error on the front end when registering. Even if I leave the name field and don't change any other code.
"Something went wrong. Please try again or contact customer support."
Thank you for the quick response. This pointed me in the right direction. The cause was an outdated version of php on homestead (7.1.14). Although documentation says 7.1+ it looks like it needs to be 7.2+. With that in mind I found a similar post on here describing how to update homestead/php. Here was my solution:
After this, I had too ssh into the vagrant box and install there
Link to original post: https://laracasts.com/discuss/channels/laravel/how-upgrade-php-mysql-in-homestead
When running the command: composer require laravel/horizon
I receive the following error: Problem 1 - laravel/horizon v1.3.1 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system. - laravel/horizon v1.3.0 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system. - Installation request for laravel/horizon ^1.3 -> satisfiable by laravel/horizon[v1.3.0, v1.3.1].
Everywhere I’ve looked it says this is a windows issue. I’m running homestead on a Mac. I’ve updated composer packages and still have the same issue. Any help is greatly appreciated!
Thanks! Placing them in the model should work. I’ll have to look into Traits. Is it poor practice to have a model without a controller? And is it good practice to put CRUD logic in the model?
I am dispatching a job. Within the queue class I want to manipulate a model. The controller for this model already contains the functions I want to use (create, update, etc.). What is the best practice for accessing these functions from the queue class? Should I abandon my controller and use the queue class?