Come risolvere questo errore Errore fatale: chiamata a una funzione non definita ...?

wp() è unafunzione abbastanzaessenziale.Risiedenelfile functions.php (non confondere con functions.phpneltema,cosa diversa)e nonpenso chetupossa caricare WP senzapassare require direttivaper quelfile ad un certopunto.

Quindi latuainstallazione sembramolto difettosa: oilfile functions.phpnel core è danneggiato o qualcos'altro èguastoe fa saltareil caricamento di quelfile.

wp() is quite essential function. It resides in functions.php file (don't confuse with functions.php in theme, different thing) and I don't think you can load WP without passing require directive for that file at some point.

So your install seems very broken - either functions.php file in core is damaged or something else is broken and makes it skip loading that file.

Iltuofile wp-config.phppotrebbeessere vuotoper qualchemotivo.

Your wp-config.php file might be empty for some reason.

Quando sonomigrato a Siteground,non soperché Siteground abbia cambiatoilfile diinclusionenell'ultima riga delfile wp-config.phpin una directory sbagliata.

Ilpercorso corretto dovrebbeessereinvece questo:

 /* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) )
    define( 'ABSPATH', dirname( __FILE__ ) . '/' );

/** Sets up WordPress vars and included files. */
require_once( ABSPATH . 'wp-settings.php' );
 

When I migrated to Siteground, I don't know why Siteground changed the include file in the last line of wp-config.php file to a wrong directory.

The correct path should be this one instead:

/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) )
    define( 'ABSPATH', dirname( __FILE__ ) . '/' );

/** Sets up WordPress vars and included files. */
require_once( ABSPATH . 'wp-settings.php' );

Questoproblemapuòessere causato dall'utilizzo dell'aggiornamento automatico quandonon si dispone di spazio su disco sufficiente.Intal caso,libera spazio sultuo server,quindi aggiorna Wordpressmanualmente all'ultima versione.

This problem can be caused by using the automatic update when you don't have enough disk space. If that is the case, free up some space on your server, then upgrade Wordpress to the latest version manually.

Sembra cheilproblema sia statoil risultato di wp-config.php danneggiato Ho aggiornato la versione locale con le credenziali del databasee l'ho caricatatramiteftp e hafunzionato.

It seems the issue was a result of corrupted wp-config.php I updated the local version with the database credentials and uploaded via ftp and it worked.

Ha avuto lo stessoproblema.Trova una soluzionepiù semplice:

1. Apri wp-settings.php
2. Commenta le seguenti righe (cerca "health":

     // if ( ! class_exists( 'WP_Site_Health' ) ) {
    //    require_once ABSPATH . 'wp-admin/includes/class-wp-site-health.php';
    // }
    // WP_Site_Health::get_instance();
 

3. Aggiornatuttii tuoiplug-in
4. Ripristina wp-settings.php allo statoprecedente

Had the same issue. Have an easier solution:

1. Open wp-settings.php
2. Comment out the following lines (search for "health":

    // if ( ! class_exists( 'WP_Site_Health' ) ) {
    //    require_once ABSPATH . 'wp-admin/includes/class-wp-site-health.php';
    // }
    // WP_Site_Health::get_instance();

3. Update all your plugins
4. Restore wp-settings.php to the previous state

fantastico ... se hai unerrorefatale o chiami a unafunzioneindefinita,vai allatuaemaile su quell'emailpotresti avere unmessaggioinviato daltuoindirizzo di hosting ...basta reinstallare o da quellapaginaemailin cui accedi...ilproblema verrà risolto ..

amazing...if you have fatal error or call to undefined funcction jus go to your email and on that email you may have a sent message from your hosting adress...just reinstall or from that email page you log in...problem will be fixed..