Hi @andreacris! It's a little bit hard to say with absolute certainty whether the problem is in your code or on the shared hosting, but with an error like "Trying to get property of non-object," my first idea would be that it is an error somewhere in the code.
The most common reasons that I see that error in my own applications are:
-
You've encountered an edge-case that you didn't anticipate while you were writing the code (don't worry, it happens to everyone!)
-
Somewhere, somehow, the data in your application has become "dirty". By that, I mean that the data you're expecting to exist in your system has been changed or removed to not meet the assumptions of the other bits of data in your system. For example, maybe one of the records in your database got removed and another piece of data in your database was relying on that deleted record and is now breaking because it assumes that the deleted record will still be there. Or maybe there is a part of your application that is accidentally morphing the data of a record in your database to something that your application isn't set up to handle!
Either way, like I said, it's a bit tricky to give you a definite answer without knowing your code and how you've set everything up.
In my opinion, the best place to take a look is in your Laravel logs ({project_root}/storage/logs) and see if you can take a look at the full stack trace of the error. If you can get a stack trace, you can often figure out what line of code threw the error, and from there it's a bit of working backwards until you find the answer.
Hopefully that helps and can get you set on the right track!
Best of luck!