Earned once you have completed the Laravel Path.
Click to learn more.
Earned once your experience points ranks in the top 10 of all Laracasts users.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points passes 1 million.
Earned once your "Best Reply" award count is 100 or more.
Earned once 1000 Laracasts lessons have been completed.
Earned once your experience points hits 10,000.
Earned once your experience points passes 100,000.
Earned once you have achieved 500 forum replies. (Current: 2)
Rewarded for being a Laracasts account holder for 1 year. Wow!
Earned after your first post on the Laracasts forum.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned if you have a lifetime subscription to Laracasts.
Earned if you are a paying Laracasts subscriber.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you have completed your first Laracasts lesson.
Earned when at least one Laracasts series has been fully completed.
Earned once you have earned your first 1000 experience points.
megaezz wrote a reply+100 XP
2w ago
So, the only way I found to avoid this problem is to render string by Blade::compileString + ob_start(), extract(), ob_get_clean().
Had the same issue now. It happened on production because of race condition. When 2 processes handle one view at the same time, then first process delete rendered view (because of deleteCachedView option) and another process still needs it.
