Title: Plugin Better Search Replace
Last modified: August 21, 2025

---

# Plugin Better Search Replace

 *  [nina2002](https://wordpress.org/support/users/nina2002/)
 * (@nina2002)
 * [9 months, 4 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/)
 * Hi,
 * I’m trying the change our website from http to https.
   1.) Installed a SSL certificate.
   2.) Changed the URL adress inwordpress to https.3.) Made a 301 redirect in the.
   htaccess file of wordpress.4.) Tried to update all links with your better search
   and replace plugin.
 * Unfortunately it won’t update the post table (141 MB), on the rest of the database
   it runs perfectly. I’ve reduced the number of sides as requested in the error
   message.
 *     ```wp-block-code
       Begin System Info-- WordPress ConfigurationSite URL: https://new.perivet.comHome URL: https://new.perivet.comMultisite: NoVersion: 6.8.2Language: pl_PLTable Prefix: Length: 5WP_DEBUG: DisabledMemory Limit: 40M-- Better Search Replace ConfigurationPlugin Version: 1.4.10Max Page Size: 9000-- Server ConfigurationOperating System: LinuxPHP Version: 8.4.7MySQL Version: 8.0.25Server Software: Apache-- PHP ConfigurationMemory Limit: 256MPost Max Size: 64MUpload Max Filesize: 64MTime Limit: 30Max Input Vars: 1000Display Errors: On (1)-- WordPress Active PluginsAntispam Bee: 2.11.8Better Search Replace: 1.4.10Converter for Media: 6.2.2Cookie Notice & Compliance for GDPR / CCPA: 2.5.7Essential Blocks: 5.6.2Forminator: 1.46.2Limit Login Attempts Reloaded: 2.26.21Loco Translate: 2.8.0Master Slider: 3.11.0Phoenix Media Rename: 3.12.11Spectra: 2.19.11SVG Support: 2.5.14WP Super Cache: 3.0.1-- WordPress Inactive PluginsRank Math SEO: 1.0.251.1 End System Info
       ```
   
 * Can you please help me?
 * Thank you and best regards,
 * Nina

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Support [Delicious Brains Support](https://wordpress.org/support/users/dbisupport/)
 * (@dbisupport)
 * [9 months, 3 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/#post-18613582)
 * Hi [@nina2002](https://wordpress.org/support/users/nina2002/),
 * Better Search Replace Support Team here. Thanks for reaching out with your query!
   We would be happy to assist.
 * Could you kindly share the complete error message you were seeing? Please also
   try editing your wp-config.php file and replace this line –
 * define( ‘WP_DEBUG’, false );
 * With these lines –
 * define(‘WP_DEBUG’, true);
   define(‘WP_DEBUG_LOG’, true);define(‘WP_DEBUG_DISPLAY’,
   false);
 * This means that any errors are logged to /wp-content/debug.log, because some 
   errors are not visible on screen. More details about that at [https://wordpress.org/support/article/editing-wp-config-php/#wp_debug](https://wordpress.org/support/article/editing-wp-config-php/#wp_debug)
 * Can you try the process again and then share the contents of the debug.log file
   in your next response? Feel free to redact any sensitive info.
 * Once we have finished troubleshooting, you should revert that config change and
   delete the debug.log file.
 *  Thread Starter [nina2002](https://wordpress.org/support/users/nina2002/)
 * (@nina2002)
 * [9 months, 3 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/#post-18616299)
 * Hi,
 * the error message is:
   An error has occured. Try either reducing the “Max. Page
   count” or contact our support.
 * I’ve also tried to edit the wp-config.php. in Filezilla.
   I have two wp-config.
   php. One is located in the directory of my subdomain in the subfolder public_html(
   xxxxxxx.com >public_html > wp-config.php).The other is located in the directory
   of my subdomain in the subfolder wp-content (xxxxxxx.com >public_html > wp-content
   >wp-config.php).I’ve tried to edit one after another, but there’s no debug.log
   file visible.
 * Do I have to edit both together?
 * Regards, Nina
 *  Thread Starter [nina2002](https://wordpress.org/support/users/nina2002/)
 * (@nina2002)
 * [9 months, 3 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/#post-18616373)
 * I have to apologize.
 * I have tried it again and have the debug.log file now:
 *     ```wp-block-code
       [27-Aug-2025 17:16:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:03:36 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:03:51 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:48 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:55 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:57 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:58 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:04:59 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:00 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:01 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:02 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:03 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:04 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:05 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:06 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:07 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:08 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:09 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:10 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:10 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the master-slider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/functions.php on line 6121[27-Aug-2025 18:05:11 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 114688 bytes) in /home/users/perivet01/public_html/domains/new.perivet.com/public_html/wp-includes/class-wpdb.php on line 2351[27-Aug-2025 18:05:11 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM ytf3_options WHERE option_name = 'action_scheduler_lock_async-request-runner' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_Lock->is_locked, ActionScheduler_OptionLock->get_expiration, ActionScheduler_OptionLock->get_existing_lock[27-Aug-2025 18:05:11 UTC] WordPress database error Commands out of sync; you can't run this command now for query SELECT option_value FROM ytf3_options WHERE option_name = 'action_scheduler_lock_async-request-runner' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set, ActionScheduler_OptionLock->get_existing_lock[27-Aug-2025 18:05:11 UTC] WordPress database error Commands out of sync; you can't run this command now for query SHOW FULL COLUMNS FROM ytf3_options made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set
       ```
   
 *  Plugin Support [Delicious Brains Support](https://wordpress.org/support/users/dbisupport/)
 * (@dbisupport)
 * [9 months, 3 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/#post-18616943)
 * Hi [@nina2002](https://wordpress.org/support/users/nina2002/),
 * Thanks for your response. Could you please try setting the plugin’s Max Page 
   Size to “1000”, and try again?
 * It also looks like you’re running out of memory. Increasing your [WP memory limit](https://deliciousbrains.com/wp-migrate-db-pro/doc/memory-issues/#wordpress-memory-limit)
   to a larger amount can help.
 * Please let us know how it goes for you.
 *  Thread Starter [nina2002](https://wordpress.org/support/users/nina2002/)
 * (@nina2002)
 * [9 months, 3 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/#post-18618091)
 * Hi,
 * The PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried 
   to allocate 53248 bytes) in xxxxx is gone.
 * TEST RUN was sucsessfully completed this time: 26 tables were scanned, 0 table
   cells were found that needed updating, and 0 changes were made. So it seems nothing
   has to be replaced.
 * Thank you very much for your support and best regards,
 * Nina

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Plugin Better Search Replace’ is closed to new replies.

 * ![](https://ps.w.org/better-search-replace/assets/icon-256x256.png?rev=2706527)
 * [Better Search Replace](https://wordpress.org/plugins/better-search-replace/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-search-replace/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-search-replace/)
 * [Active Topics](https://wordpress.org/support/plugin/better-search-replace/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-search-replace/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-search-replace/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [nina2002](https://wordpress.org/support/users/nina2002/)
 * Last activity: [9 months, 3 weeks ago](https://wordpress.org/support/topic/plugin-better-search-replace/#post-18618091)
 * Status: not resolved