gtapsupport
Forum Replies Created
-
Still an issue. Since it Always fails on wp_options, can’t exactly temporarily remove it either.
This is actually quite a wide-spread issue. I’ve had this happen on 4-5 different projects while migrating from dev to live in the past few months. It could be server-related, because when I dump and replace manually, I can run the migrate process in the new server normally (to run the replacements that wouldn’t work with find&replace).
There are no conflicts with plugins (tried disables) and there’s nothing visibly strange going on with wp_options.
The logs suggest a memory issue,
[fcgid:warn] mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1601536 bytes) in .../plugins/wp-migrate-db/class/wpmdb-replace.php on line 283, referer: .../wp-admin/tools.php?page=wp-migrate-db&wpmdb-profile=1Looks to me that there’s a process that eats up all available memory before crashing.
if (!is_wp_error($zemanta_response)) { $response = json_decode($zemanta_response['body']); if (isset($response->status)) { $status = $response->status; } }Previous solution tries checking for
$responsebefore it’s defined, I split checks into separate parts and set the response before checking it.Forum: Plugins
In reply to: [Post Duplicator] ACF Field ExclusionHiya!
As a workaround, you could clear the necessary field after duplicate using the ‘mtphr_post_duplicator_created’ action.
function mtphr_after_duplicate($original_id, $duplicate_id, $settings) { //delete post meta or clear contents of acf } add_action( 'mtphr_post_duplicator_created', 'mtphr_after_duplicate', 10, 2);