Incorrect Memory Allocation for subsite

OK!

Here are the updates:
1) link to site (not designed or updated by me): http://www.prenetworking.net/chapters/brandywine/
2) Moved the memory limit line up to number 2 in my wp-config. Here is the updated file:

<?php
define( 'WP_MEMORY_LIMIT', '128M' );
/**
 * The base configurations of the WordPress.
 *
 * This file has the following configurations: MySQL settings, Table Prefix,
 * Secret Keys, WordPress Language, and ABSPATH. You can find more information
 * by visiting {@link http://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', 'xxx');

/** MySQL database username */
define('DB_USER', 'xxx');

/** MySQL database password */
define('DB_PASSWORD', 'xxx');

/** MySQL hostname */
define('DB_HOST', 'xxx');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** 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_KEY',         'put your unique phrase here');
define('SECURE_AUTH_KEY',  'put your unique phrase here');
define('LOGGED_IN_KEY',    'put your unique phrase here');
define('NONCE_KEY',        'put your unique phrase here');
define('AUTH_SALT',        'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT',   'put your unique phrase here');
define('NONCE_SALT',       'put your unique phrase here');

/**#@-*/

/**
 * 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_';

/**
 * WordPress Localized Language, defaults to English.
 *
 * Change this to localize WordPress. A corresponding MO file for the chosen
 * language must be installed to wp-content/languages. For example, install
 * de_DE.mo to wp-content/languages and set WPLANG to 'de_DE' to enable German
 * language support.
 */
define('WPLANG', '');

/**
 * 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);

define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', false );
$base = '/chapters/';
define( 'DOMAIN_CURRENT_SITE', 'www.prenetworking.net' );
define( 'PATH_CURRENT_SITE', '/chapters/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );

/* 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');

3) .htaccess:

AddType x-mapp-php5 .php
RewriteEngine On
RewriteBase /chapters/
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]

4) My phpinfo.php file states 128M under Core.
5) I’m not exactly sure where/how to generate the error logs with my shared host. For this client, unfortunately they’re on 1&1. I think I can start error logging looking at a knowledge base article, but not sure if that’s what you’d like to see?
6) Just for kicks, the only thing that isn’t working right now is clicking on “Pages”, which returns a completely blank white page (with no code in the source).

I think that’s it for now — please let me know what else I can supply and what you’d like me to try with the error logging — I sincerely appreciate your assistance!

Thank you for your quick reply!

@george — it did not. The error message still states something like this:

Fatal error: Out of memory (allocated 33554432) (tried to allocate 218647 bytes) in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/wp-db.php on line 1127

Here is my pastebin (and thank you for the debugging constants to add to wp-config, that’ll be very useful in the future):

http://pastebin.com/NjdxeYWY

Not really knowing what’s up, this is what stands out to me: 1) Line 57 references the WordPress News error on the dashboard (again not using the full 128M); 2) after enabling debugging and the other items, I now get a 500 error instead of the white page (which, any message is nice, of course); 3) I’m guessing with the repetition of the ‘deprecated’ errors, maybe my client has a couple of plugins that need to be updated?

Thanks again!

Wow…thank you for the link on Smooth Gallery — I’ve been trying to prove that the client updated WordPress and it didn’t automatically update itself (it’s been updated to 4.4.1, but I installed the original back in 2012), and that might actually help me to pin some things down.

Next, sorry for bugging you all for plugin issues — but now that I’ve disabled that plugin, the Pages section has started working again! Which is fantastic. But, while I still have assistance here, the plugin that they rely upon is Visual Composer, and that is still not functioning. Here is the latest from the debug.log:

[02-Feb-2016 00:06:36 UTC] PHP Fatal error:  Out of memory (allocated 34078720) (tried to allocate 52 bytes) in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-content/plugins/essential-grid/includes/base.class.php on line 111
[02-Feb-2016 00:07:35 UTC] PHP Fatal error:  Out of memory (allocated 34078720) (tried to allocate 52 bytes) in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-content/plugins/essential-grid/includes/base.class.php on line 111
[02-Feb-2016 00:09:46 UTC] PHP Notice:  Trying to get property of non-object in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/post.php on line 1591
[02-Feb-2016 00:09:46 UTC] PHP Notice:  Trying to get property of non-object in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/post.php on line 1591
[02-Feb-2016 00:09:47 UTC] PHP Fatal error:  Out of memory (allocated 32243712) (tried to allocate 28490 bytes) in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/wp-db.php on line 1425
[02-Feb-2016 00:11:16 UTC] PHP Notice:  Trying to get property of non-object in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/post.php on line 1591
[02-Feb-2016 00:11:16 UTC] PHP Notice:  Trying to get property of non-object in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/post.php on line 1591
[02-Feb-2016 00:11:16 UTC] PHP Fatal error:  Out of memory (allocated 32243712) (tried to allocate 24990 bytes) in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/wp-db.php on line 1425
[02-Feb-2016 00:21:04 UTC] PHP Notice:  Trying to get property of non-object in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/post.php on line 1591
[02-Feb-2016 00:21:04 UTC] PHP Notice:  Trying to get property of non-object in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/post.php on line 1591
[02-Feb-2016 00:21:05 UTC] PHP Fatal error:  Out of memory (allocated 32243712) (tried to allocate 28490 bytes) in /homepages/20/d315350421/htdocs/PNW_HOST/new_site/chapters/wp-includes/wp-db.php on line 1425

Which again shows Out of Memory errors. The Visual Composer page spins a gif that looks like it’s doing something, but of course it’s not. I did add the WP_MAX_MEMORY_LIMIT for good measure as well.

What should I try next? Does uninstalling and reinstalling the plugin make sense as it was just updated in the past week? Or is there a specific memory limit that can be adjusted just for wp-db.php? I know…grasping at straws.

Thank you for your help (seriously)!

Sorry for the delay! I do not run Memory Bump, and here is the list that is listed on the subsite:

• Akismet
• Essential Grid
• flickrRSS
• Get The Image
• Hello Dolly
• NextGEN Gallery by Photocrati
• NextGEN Smooth Gallery
• Server IP & Memory Usage Display
• Simple Login Lockdown
• Slider Revolution
• TinyMCE Advanced
• U-Design Shortcode Insert Button
• WP-PageNavi
• WP125
• WPBakery Visual Composer

Should I download all of the plugin code and search for an ini_set call? Oh, and as for the php.ini looks like this:

memory_limit = 128M ; Maximum amount of memory a script may consume (128MB)

I can increase it to 256M if you’d like, but they may not be necessary?

Thanks for sticking with it/me!

EDIT: Oh, and that Server IP & Memory Usage plugin may look like the immediate sore thumb, but that useful plugin has only been installed after the issues.

Actually, this is a quite old 1&1 account (at least 2012, probably older). It’s a developer account, which was their most expensive shared hosting plan at the time, but I can’t find any information in the Control Panel on how much RAM they have allocated to the package.

I like to believe that it’s not capped at 32M as the phpinfo.php page does report 128M in the Core section, but I suppose anything is possible. I will get in contact with their support to see if there is something that isn’t quite right with the server.

I will also increase the memory to 256 to appease the recommendation from Essential Grid — I believe that is a vital piece of the Visual Composer system, and that could be something that’s holding us back. I will definitely report back on that.

Oh, and finally, I did download all of the plugin files from the active server, and did a search for ini_set( …Found 22 occurrences across 12 files. The vast majority of which were from the NGGallery which is disabled, but there was one for Essential Grid as well. Hopefully, we’re on to something.

Thanks for the continued follow ups…otherwise I’d be lost here.