Smart Custom 404 error page [404page]

Descrizione

Portare visitatori nel tuo sito web richiede tempo e impegno. Ogni visitatore è importante. La pagina di errore 404 predefinita nella maggior parte dei temi non fornisce alcuna informazione su come trovare le informazioni nel tuo sito. Un nuovo visitatore, che non ti conosce, finisce così in un vicolo cieco e abbandona il tuo sito web. Imposta una pagina di errore 404 personalizzata per tenerlo nel tuo sito web.

Questo utile plugin ti permette di creare la tua pagina di errore 404 personalizzata senza alcuno sforzo e lavora con quasi tutti i temi.

Retired Plugin

Development, maintenance and support of this plugin has been retired in october 2023. You can use this plugin as long as is works for you.

There will be no more updates and I won’t answer any support questions. Thanks for your understanding.

Feel free to fork this plugin.

Thanks

Many thanks to the more than 100,000 users of this plugin. You have made this plugin a huge success. It was a pleasure and an honor, but I am retiring from plugin development.

Best regards,
Peter

Utilizzo

Crea la tua pagina di errore 404 personalizzata come qualsiasi altra pagina utilizzando l’editor di pagine di WordPress. Quindi vai in ‘Aspetto’ -> ‘Pagina di errore 404’ e seleziona la pagina creata come pagina di errore 404 personalizzata. Fatto!

Perché utilizzare questo plugin?

A differenza di altri plugin simili, 404page non crea reindirizzamenti. È molto importante perché viene correttamente inviato un codice 404 e questo comunica ai motori di ricerca che la pagina non esiste e deve essere rimossa dall’indice.

A differenza di altri plugin simili, 404page non crea richieste server aggiuntive.

Requisiti

L’unico prerequisito per questo plugin è cambiare la struttura dei Permalink, da ‘Impostazioni’ -> ‘Permalink’, in una delle opzioni disponibili tranne ‘Semplice’. Così si attiva anche la gestione dell’errore 404 di WordPress.

Block & Shortcode

Block

The Plugin offers a block “URL causing 404 error” for the block-based editor to show the URL that caused the error. The block offers three display options:

  • “Page” to show the page including path ( e.g. does/not/exist )
  • “Domain Path” to show the URL without protocol and parameters ( e.g. example.com/does/not/exist )
  • “Domain Path” to show the URL without protocol and parameters ( e.g. example.com/does/not/exist )
  • “Full” to show the complete URL ( e.g. https://example.com/does/not/exist?p=1 )

Shortcode

The Plugin offers a shortcode “pp_404_url” for the classic editor to show the URL that caused the error. There are three possible options:

  • [pp_404_url page] to show the page including path ( e.g. does/not/exist )
  • [pp_404_url domainpath] to show the URL without protocol and parameters ( e.g. example.com/does/not/exist )
  • [pp_404_url] or [pp_404_url full] to show the complete URL ( e.g. https://example.com/does/not/exist?p=1 )

Informazioni sulla privacy del plugin

  • Questo plugin non imposta cookie
  • Questo plugin non colleziona o archivia dati
  • Questo plugin non invia dati a server esterni

Per sviluppatori

Action Hook

Il plugin aggiunge un action hook 404page_after_404 che puoi utilizzare per aggiungere funzionalità extra. La posizione esatta dell’azione, che si verifica dopo che un errore 404 è rilevato, dipende dall’Operating Method. La tua funzione non deve generare output. Non ci sono parametri.

Costante

Se il plugin 404page è installato e attivato crea una costante PHP PP_404. Verifica la sua esistenza per rilevare la presenza del plugin 404page.

Funzioni

Il plugin fornisce le seguenti funzioni:

  • pp_404_is_active() per verificare se c’è una pagina 404 personalizzata selezionata e se questa esiste
  • pp_404_get_page_id() per avere l’ID della pagina 404
  • pp_404_get_all_page_ids() per avere un array degli ID di pagina in tutte le lingue
  • pp_404_get_the_url( $type ) to get the URL that caused the 404 error
    • Parameter $type string Optional
    • “page” to get the page including path ( e.g. does/not/exist )
    • “domainpath” to get the URL without protocol and parameters ( e.g. example.com/does/not/exist )
    • “full” (default) to get the complete URL ( e.g. https://example.com/does/not/exist?p=1 )

Modalità nativa

If you are a theme developer you can add native support for the 404page plugin to your theme for full control.

Blocchi

Questo plugin fornisce 1 blocco.

  • URL causing 404 error

Recensioni

26 Gennaio 2024
This plugin does exactly what I need to create an effective 404 error page
5 Ottobre 2023
Hello Peter, I want to thank you for the use of this lovely, simple plugin. Am sad that you are retiring from supporting it, it will be hard to replace, but I understand life changes. Just wanted to wish you the best in your life and future endeavors! With Appreciation Alannah
Leggi tutte le recensioni di 1.183

Contributi e sviluppo

“Smart Custom 404 error page [404page]” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito.

Collaboratori

“Smart Custom 404 error page [404page]” è stato tradotto in 18 lingue. Grazie ai traduttori per i loro contributi.

Traduci “Smart Custom 404 error page [404page]” nella tua lingua.

Ti interessa lo sviluppo?

Esplora il codice segui il repository SVN, segui il log delle modifiche tramite RSS.

Changelog (registro delle modifiche)

11.4.6 (2024-04-17) URGENT BUGFIX

  • Bugfix after Cleanup

11.4.5 (2024-04-16) CLEANUP

  • Cleanup

11.4.4 (2022-10-05) FINAL VERSION

  • removed all links to webiste
  • removed request for rating
  • removed manual

11.4.3 (2022-11-05)

  • bugfix for WP 6.1

11.4.2 (2022-11-01)

  • also add class error404 to body tag if page is called directly
  • plugin renamed

11.4.1 (2022-10-16)

  • bugfix: load Javascript for Block only when needed

11.4.0 (2022-10-13)

  • Block added
  • Shortcode added
  • Function pp_404_get_the_url() added

11.3.1 (2022-04-05)

  • just cosmetics
  • Plugin Foundation updated to PPF08

11.3.0 (2021-01-06)

  • new option to always send an 410 instead of an 404
  • Plugin Foundation updated to PPF07

11.2.6 (2020-08-23)

  • Plugin Foundation updated to PPF06

11.2.5 (2020-08-22)

  • minor UI adjustments

11.2.4 (2020-08-16)

  • bug fix for Flamingo (see topic) plus potentially other plugins (thanks to garfiedo for supporting me to find the reason)

11.2.3 (2020-07-05)

11.2.2 (2020-03-28)

  • changes to the notification for hopefully better compatibility
  • Plugin Foundation swtiched to PPF04

11.2.1 (2020-01-04)

  • if W3 Total Cache is installed and caching is active URLs that result in an 404 error are automatically excluded from caching

11.2.0 (2020-01-01)

  • if WP Super Cache is installed and caching is active URLs that result in an 404 error are automatically excluded from caching

11.1.4 (2019-12-29)

  • urgent bug fix for PPF03

11.1.3 (2019-12-29)

  • Plugin Foundation updated to PPF03, no functional changes

11.1.2 (2019-11-19)

  • exclude 404 page from XML sitemap generated by Jetpack

11.1.1 (2019-11-16)

  • from now on it is not only detected if Yoast SEO Plugin is active, but also if the sitemap feature is activated

11.1.0 (2019-11-10)

  • now uses Plugin Foundation PPF02 for plugin compatibility
  • introduces two new functions for developers pp_404_get_page_id() and pp_404_get_all_page_ids()

11.0.5 (2019-10-22)

  • bugfix for Yoast SEO XML Sitemap (see topic)
  • added a note to settings page if Yoast SEO is active

11.0.4 (2019-10-06)

  • bugfix for WPML

11.0.3 (2019-09-01)

  • bugfix for REST API call (see here)

11.0.2 (2019-08-30)

11.0.1 (2019-08-13)

  • fix for PHP 7.1 – __construct() access level in subclass – this is an PHP error that was fixed in PHP 7.2, but I’ve changed my code to also work with PHP 7.1

11.0.0 (2019-08-13)

  • mostly rewritten based on my own newly created Plugin Foundation

10.5 (2019-04-01)

  • some more security improvements

10.4 (2019-03-31)

  • security vulnerability in AJAX call fixed (thanks to Julio Potier for pointing me to this)

10.3 (2019-02-21)

  • fix for compatibility with iThemes Sync (ticket)

10.2 (2019-02-19)

  • just another small change to prevent from potential problems with version 10

10.1 (2019-02-14)

10 (2019-02-14)

  • workaround for WordPress Permalink bug #46000
  • code improvement
  • performance tuning

9 (2019-01-24)

  • Gutenberg note added

8 (2019-01-11)

  • fixed compatibility issue with latest WPML version
  • code improvement
  • UI improvements

7 (2018-07-16)

  • corrected wrong image path
  • added video links to admin page
  • code improvements

6 (2018-06-18)

  • exclude 404 page from XML sitemap generated by Yoast SEO
  • further UI-improvements

5 (2018-03-05)

  • show an indicator if the currently edited page is a 404 error page
  • minor code- & UI-improvements

4 (2018-03-05)

3.3 (2017-11-16)

  • support for right-to-left-languages added
  • faulty display in WP 4.9 fixed

3.2 (2017-10-05)

  • new feature to send an HTTP 410 error for deleted objects

3.1 (2017-07-24)

  • bugfix for Polylang (see topic)
  • bugfix for CLI (see topic)
  • add debug class to body tag
  • also add body classes for Customizr theme
  • do not add error404 class if already exists
  • further redesign admin interface

3.0 (2017-07-05)

  • new feature to force 404 error after loading page
  • new feature to disable URL autocorrection guessing
  • finally removed Polylang stuff disabled in 2.4
  • redesigned admin interface
  • code improvement

2.5 (2017-05-19)

  • hide 404 page from search results on front end (if WPML is active, all languages are hidden)
  • do not fire a 404 in Compatibility Mode if the DW Question & Answer plugin by DesignWall is active and a question has no answers

2.4 (2017-03-08)

  • ensure that all core files are loaded properly (see topic)
  • Polylang plugin does no longer require Compatibility Mode (see topic)
  • hide all translations if WPML is installed and “Hide 404 page” is active (thanks to the WPML guys for pointing me at this)
  • post status fix (see topic)
  • Enfold theme issue fix (thanks to the guys at Kriesi.at for supporting me)

2.3 (2016-11-21)

  • a few minor bugfixes solve some problems with page templates in certain combinations

2.2 (2016-09-26)

  • automatic switch to Compatibility Mode for several plugins removed
  • enhanced support for WPML and Polylang
  • remove the 404 page from search results (for all languages if WPML or Polylang is used)
  • remove the 404 page from sitemap or other page lists (for all languages if WPML or Polylang is used)
  • bugfix for author archives
  • confusing admin message removed

2.1 (2016-04-22)

  • introduction of selectable Operating Methods
  • several changes to Compatibility Mode for improved WPML and bbPress compatibility plus compatibility with Page Builder by SiteOrigin
  • Polylang compatibility
  • automatic switch to Compatibility Mode if WPML, bbPress, Polylang or Page Builder by SiteOrigin is detected
  • completely new Customizr Compatibility Mode (automatically enabled if Customizr is detected)
  • firing an 404 error in case of directly accessing the 404 error page can now be deactivated
  • WP Super Cache support
  • option to hide the 404 error page from the Pages list
  • 404 error test
  • plugin expandable by action
  • delete all settings on uninstall

2.0 (2016-03-08)

  • WPML compatibility
  • bbPress compatibility
  • Customizr compatibility
  • directly accessing the 404 error page now throws an 404 error
  • class error404 added to the classes that are assigned to the body HTML element
  • the settings menu was moved from ‘Settings’ to ‘Appearance’
  • translation files removed, using GlotPress exclusively

1.4 (2015-08-07)

  • edit the 404 page directly from settings page
  • Portuguese translation

1.3 (2015-01-12)

  • technical improvement (rewritten as class)
  • cosmetics

1.2 (2014-07-28)

  • Spanish translation
  • Serbo-Croatian translation

1.1 (2014-06-03)

  • Multilingual support added
  • German translation

1.0 (2013-09-30)

  • Initial Release