V
V
Volodymyr2022-04-04 23:37:19
Laravel
Volodymyr, 2022-04-04 23:37:19

Logs are not cleared, the old log is constantly coming out, why?

Hello!
There is Laravel 8. I
tested one variable in the template without specifying it, I got an error:

[2022-04-04 16:25:17] production.ERROR: Trying to get property 'login' of non-object (View: /resources/views/index.blade.php) {"view":{"view":"/resources/views/index.blade.php","data":{"errors":"<pre class=sf-dump id=sf-dump-671976160 data-indent-pad=\"  \"><span class=sf-dump-note>Illuminate\\Support\\ViewErrorBag</span> {<a class=sf-dump-ref>#316</a><samp data-depth=1 class=sf-dump-expanded>
  #<span class=sf-dump-protected title=\"Protected property\">bags</span>: []
</samp>}

After that, I began to constantly receive only this error in laravel.log. And there is no index.blade.php file and the cache is cleared, and with any error, the old error still comes out.
Tell me how to clean it so that the actual ones appear again?

I tried clearing the cache like this:
php artisan config:cache
php artisan route:cache
php artisan view:clear
php artisan cache:clear

Does not help.

If you write in the env config:
APP_ENV=local
APP_DEBUG=true

then on the output page the errors become relevant, and in the laravel.log logs the old one is again, which I don’t understand.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
V
Volodymyr, 2022-04-05
@volodyalesha86

When opening the laravel.log file, the old file was always opened in priority, saved on the PC, overwriting the actual log file.

L
lil_koi, 2022-04-05
@lil_koi

delete the log file, catch the error - it will be new and clean

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question