framework/views/error/not_found.blade.php

@extends('flarum.forum::layouts.basic')

@section('content')
  <p>
    {{ $message }}
  </p>
  <p>
    <a href="{{ $app->url() }}">
      {{ $translator->trans('core.views.error.not_found_return_link', ['{forum}' => $settings->get('forum_title')]) }}
    </a>
  </p>
@endsection
Add a "return home" link to 404 errors 2017-11-29 13:23:25 +10:30			`@extends('flarum.forum::layouts.basic')`

			`@section('content')`
			`<p>`
Move view logic into middleware 2017-11-29 22:25:57 +10:30			`{{ $message }}`
Add a "return home" link to 404 errors 2017-11-29 13:23:25 +10:30			`</p>`
			`<p>`
			`<a href="{{ $app->url() }}">`
Determine error view and message based on type ...not based on status code. To simplify this logic, we now use the same error "type" both when routes are not found and specific models are not found. One exception is ours, one is from Laravel, but for the purposes of error handling they should be treated the same. Fixes flarum/core#1641. 2019-08-14 19:43:36 +02:00			`{{ $translator->trans('core.views.error.not_found_return_link', ['{forum}' => $settings->get('forum_title')]) }}`
Add a "return home" link to 404 errors 2017-11-29 13:23:25 +10:30			`</a>`
			`</p>`
			`@endsection`