brechtryckaert

I think the easiest way to get this done would be to use https://srd.www.ads-software.com/plugins/velvet-blues-update-urls/. This way all url-references in the database will get updated correctly.

This error actually tells us that your PHP_memory_limit on the server is set to 128 MB, but that your site is trying to use more. Because of this, the action is aborted, resulting in the fatal error.
I’d suggest contacting your hosting provider to set the PHP_memory_limit to a higher value (for example 196 MB) or you could try reducing plugins.
I’d also remove the define( ‘WP_MEMORY_LIMIT’, ’96M’ ); from the wp-config.php.

To be honest, page size isn’t everything. Another major factor would be the number of elements that need to be loaded. I usually use the “Net”-tab in the plugin “Firebug” for Mozilla Firefox to analyze the independent elements and find out which ones are slowing down the loading speed.

If you like, I can look into this for you. Can you indicate which site this concerns?

This site might be what you’re looking for https://web-capture.net/

I would start by setting wp_debug to true in your wp-config.php-file.

In this file you’ll see following line:
define( ‘WP_DEBUG’, false );

Change this to:
define( ‘WP_DEBUG’, true );

Normally, the blank page will then be replaced by the error that is causing it.

This can also be resolved on the server level, by altering your PHP configuration. Try to enable output_buffering (or ask your hosting company to do it). This should also allow you to resolve it.

This error occurs because multiple scripts are generating “header”-code, while the server only expects to get it once. By setting output_buffering active, all of the “header”-code will be collected in a buffer and treated in one run.

SOLVED:
I was missing a “=” in my readme.txt. This broke the entire parsing of the file into the plugin repo.

Just a small update:
I’ve completely deleted the entire contents of the svn repository and redeployed. No changes.

Any help would be welcomed!