Fatal error on line 791

Comments

• corbandusk

  August 2015

  Oh, I also just updated my theme to 9.2 but no change there either.
  
  Maybe I've messed up a setting or something?
  
• Albert

  August 2015

  Hi,
  
  please take a look at http://forum.muffingroup.com/betheme/discussion/7758/fatal-error-allowed-memory-size-exhausted where we explained what to do in such situation because this error is not related with theme at all.
  
  Thanks!
  

  Learn more: Video Tutorials | How To | FAQ Vote on what comes next
• corbandusk

  August 2015 edited August 2015

  Hi,
  
  Thanks for the reply.
  
  I've checked the different things I can do there and opted for changing the wp-config.php.
  
  I've tried placing it (there's 2 possible codes) in different places to no avail.
  
  Which one do I place where? Thanks.
  
  <?php
  /**
  * The base configurations of the WordPress.
  *
  * This file has the following configurations: MySQL settings, Table Prefix,
  * Secret Keys, and ABSPATH. You can find more information by visiting
  * {@link https://codex.wordpress.org/Editing_wp-config.php Editing wp-config.php}
  * Codex page. You can get the MySQL settings from your web host.
  *
  * This file is used by the wp-config.php creation script during the
  * installation. You don't have to use the web site, you can just copy this file
  * to "wp-config.php" and fill in the values.
  *
  * @package WordPress
  */
  
  // ** MySQL settings - You can get this info from your web host ** //
  /** The name of the database for WordPress */
  define('DB_NAME', '_');
  
  /** MySQL database username */
  define('DB_USER', '_');
  
  /** MySQL database password */
  define('DB_PASSWORD', ');
  
  /** MySQL hostname */
  define('DB_HOST', '');
  
  /** Database Charset to use in creating database tables. */
  define('DB_CHARSET', '');
  
  /** The Database Collate type. Don't change this if in doubt. */
  define('DB_COLLATE', '');
  
  /**#@+
  * Authentication Unique Keys and Salts.
  *
  * Change these to different unique phrases!
  * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
  * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
  *
  * @since 2.6.0
  */
  define('AUTH');
  define('SECURE_AUTH_KEY', '');
  define('LOGGED_IN_KEY', '');
  define('NONCE_KEY', '');
  define('AUTH_SALT', '');
  define('SECURE_AUTH_SALT', '');
  define('LOGGED_IN_SALT', '');
  define('NONCE_SALT', '');
  
  /**#@-*/
  
  /**
  * WordPress Database Table prefix.
  *
  * You can have multiple installations in one database if you give each a unique
  * prefix. Only numbers, letters, and underscores please!
  */
  $table_prefix = 'wp_';
  
  /**
  * For developers: WordPress debugging mode.
  *
  * Change this to true to enable the display of notices during development.
  * It is strongly recommended that plugin and theme developers use WP_DEBUG
  * in their development environments.
  */
  define('WP_DEBUG', false);
  
  /* 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');
• corbandusk

  August 2015

  define(‘WP_MEMORY_LIMIT’, ‘128M’);
  
  Or
  
  ini_set(‘memory_limit’,’128M’);
• Albert

  August 2015

  If none of them works, then you must contact with server administrator because your server is definitely limited and only admin will be able to increase those limits.
  

  Learn more: Video Tutorials | How To | FAQ Vote on what comes next
• corbandusk

  August 2015

  Grand, thanks for the help.
  
  I deleted a couple of add-ons and it's back to working fine now.
  
• Albert

  August 2015

  You're welcome
  

  Learn more: Video Tutorials | How To | FAQ Vote on what comes next