Avada Forums Community Forum Need Code Snippet to Change Avada’s Default 404 Error Message

Tagged: , , , ,

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Jetxpert-Envato
    Blocked
    Post count: 339

    We like Avada’s default 404 Error Page. However, it would be great if someone can provide the following:

    (1) A code snippet that will allow us to change the text: “Oops, This Page Could Not Be Found!” to something else.

    (2) A procedure that will allow us to change the default fontawesome icon “fa-angle-right” shown in the 404 Error Page checklist with another one – or a custom icon.

    Note: We can accomplish the above by changing Avada’s 404.php file, but those changes — as you know — will be wiped out when the next Avada revision is released.

    Thank you!

    Metro
    Participant
    Post count: 116

    You can easily build your own 404 page using the layouts builder.

    Jetxpert-Envato
    Blocked
    Post count: 339

    @metro,

    Thanks for your suggestion.

    Yes, we already thought of that. There’s a lot of work involved just to change the default message. We like Avada’s default 404 Error Page.

    A code snippet is the easiest, fastest solution.

    Cheers!

    marklchaves
    Participant
    Post count: 873

    Hey @jetxpert-envato,

    If you’ve got a child theme, have you tried the standard copying over the parent 404.php and tweaking that?

    You can make changes like this in minutes (not that you’d want this look lol).

    https://jumpshare.com/v/ETl8QG7FTKhuIBQRJqep

    As a fallback, you can always try to good ole the_content filter on your 404. But that’s a performance and code debt hit (double whammy).

    Thanks!

    Jetxpert-Envato
    Blocked
    Post count: 339

    Hey @marklchaves,

    Nice to hear back from ya. Thanks for the suggestions.

    We’re staying away from using Avada’s Child theme. Used it once, and created more issues for us than what it solved.

    Yeah, that 404 Page looks fabulous. Ha!

    Avada Support was unable to help us. They suggested using Loco’s translator plugin to modify the built-in .mo/.po language (i.e., text) files. No dice.

    So, the simplest approach is to modify Avada’s 404.php file directly, save it, then upload it when Avada is updated. It only takes seconds to do that without penalizing our website’s performance.

    Again, thank you.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.