Different Behavior In Laravel Homestead & Laravel Forge
I had a simple mistake in my PHP Code:
$string += 'something' . $Car->id . ',';
Which resulted in different behavior in Homestead and Forge:
Homestead Result of $string:
0
Forge Result:
Error: A non-numeric value encountered
Does Anybody know why? And how can I change the Homestead behavior to the same like the forge one? It's absolutely better..
Update
I'm sorry I wasn't totally clear in my question. The question wasn't about the mistake itself += instead of .=, I was aware of that.
The question is why in one environment the error appears and in the other one not.
Both environments are configured the same way (php.ini):
error_reporting = E_ALL
display_errors = On
And it was not just a notice, it's an error.
Answer
The PHP Version of Laravel Homestead was 7.0.8 and the PHP Version of Laravel Forge 7.1.0-3.
I updated Laravel Homestead to the newest which uses PHP 7.1.0-2, and now Homestead shows up the right error:
Error: A non-numeric value encountered
I'm not shure if it's just the PHP Version or if it's an other change in Homestead with the new version. Thats just what I've found out.
Related Questions
- → "failed to open stream" error when executing "migrate:make"
- → October CMS Plugin Routes.php not registering
- → OctoberCMS Migrate Table
- → OctoberCMS Rain User plugin not working or redirecting
- → October CMS Custom Mail Layout
- → October CMS - How to correctly route
- → October CMS - Conditionally Load a Different Page
- → Make a Laravel collection into angular array (octobercms)
- → In OctoberCMS how do you find the hint path?
- → How to register middlewares in OctoberCMS plugin?
- → Validating fileupload(image Dimensions) in Backend Octobercms
- → OctoberCMS Fileupload completely destroys my backend
- → How do I call the value from another backed page form and use it on a component in OctoberCms