Cytotoxic

Cytotoxic

Member Since 2 Weeks Ago

Experience Points 160
Experience Level 1

4,840 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed 0
Lessons
Completed
Best Reply Awards 0
Best Reply
Awards
  • Start Your Engines Achievement

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • First Thousand Achievement

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • One Year Member Achievement

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • Two Year Member Achievement

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • Three Year Member Achievement

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • Four Year Member Achievement

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • Five Year Member Achievement

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • School In Session Achievement

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • Welcome To The Community Achievement

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • Full Time Learner Achievement

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • Pay It Forward Achievement

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • Subscriber Achievement

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • Lifer Achievement

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • Laracasts Evangelist Achievement

    Laracasts Evangelist

    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.

  • Chatty Cathy Achievement

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • Laracasts Veteran Achievement

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • Ten Thousand Strong Achievement

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • Laracasts Master Achievement

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • Laracasts Tutor Achievement

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • Laracasts Sensei Achievement

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • Top 50 Achievement

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

16 May
1 week ago

Cytotoxic left a reply on 404 Page Instead Of {METHOD} Not Supported For This Route

@TRAY2 - Actually I just ran into the issue again but with POST. The fallback does not work with methods other then GET. When I post to an invalid route (I forgot to update a url and found this out by accident) I ended up getting "The POST method is not supported for this route. Supported methods: GET, HEAD, PATCH." But since it was an invalid route altogether it should have been caught with the standard 404 but it wasn't.

Cytotoxic left a reply on 404 Page Instead Of {METHOD} Not Supported For This Route

@MTHOMAS - I was just running tests to see what would happen if someone tried to access the url they see in javascript. I am not wanting to access it via GET I just wanted to know what happens if someone else tries to access it. I really don't want to have to manually add invalid routes just to show 404 errors I just wanted the system to treat all routes "not defined by me" the same way. But it seems it treats routes differently if you have at least one route that's similar vs one that doesn't match anything.

15 May
1 week ago

Cytotoxic left a reply on 404 Page Instead Of {METHOD} Not Supported For This Route

@MTHOMAS - I removed all routes except this one and it still gives the same {METHOD} not supported for this route error instead of a 404.

Route::post('/admin/user/list/ajax', '[email protected]');

If I access this via /browser/GET

Cytotoxic left a reply on 404 Page Instead Of {METHOD} Not Supported For This Route

Thanks for the link. But why does it work this way as far as the code goes since I specially state a path and method if it doesn't exists in my route definitions it shouldn't treat going to a path with the wrong method different then going to a route that doesn't exists at all with any methods. At least that's my opinion, what is the reasoning behind doing different error handling for this situation by default?

Cytotoxic started a new conversation 404 Page Instead Of {METHOD} Not Supported For This Route

How can I get the routes to send the user to the standard 404 page if they access a path that is not a defined route. I am getting "{METHOD} not supported for this route" while in debug mode and without debug mode it just says "Whoops, looks like something went wrong."

For instance accessing a POST only route via the browser GET I want to send to a 404 page vs this error message.

Thanks

08 May
2 weeks ago

Cytotoxic left a reply on Override Sections With Defaults

@MVD - Thanks that is way better I didn't know you could load a view file within the default param.

Cytotoxic started a new conversation Override Sections With Defaults

Is this a good way of setting up the ability to override a section with a default if nothing overrides it or is there a better way of doing this?

// This is in a template file the view I am calling extends
@hasSection('default_header')
    @yield('default_header')
@else
    @include('default_header')
@endif

Then if I want to load a different header file or manual code I could just do this in the view I am calling from the controller:

// load a different header file for this view
@section('default_header')
    @include('default_header2')
@endsection

Thanks.