Conversation
supportRan just the URL and it seemed to be fine. Ran on text (whole database) and it nuked my site Using Beaver Builder Going to need to do a site restore.
Thank you for sharing your experience, we genuinely appreciate you taking the time to do so. It’s important to clarify how this type of tool works so others can use it safely and effectively. The plugin is a powerful database-level search and replace utility . When run against the entire database, it will replace every matching instance it finds, including content generated by page builders like Beaver Builder , which often store layouts and settings in structured or serialized formats. Running a global replacement without fully reviewing what is being changed can unintentionally affect page builder data, which may lead to broken layouts or missing content. This isn’t a bug in the plugin, but rather the nature of database-wide operations. That’s why we strongly recommend: Always running a dry run / preview first Limiting replacements to specific tables or columns when possible Creating a full backup before executing bulk changes Avoiding blind global replacements when page builders or serialized data are involved Used correctly, the plugin is extremely effective and trusted by thousands of sites but like any advanced tool, it requires a clear understanding of what is being changed and where. We’re glad you were able to restore your site, and we hope this helps others approach bulk replacements more confidently and safely in the future. If anyone needs guidance on best practices or safe usage scenarios, we’re always happy to help.
Thank you for sharing your experience, we genuinely appreciate you taking the time to do so. It’s important to clarify how this type of tool works so others can use it safely and effectively. The plugin is a powerful database-level search and replace utility . When run against the entire database, it will replace every matching instance it finds, including content generated by page builders like Beaver Builder , which often store layouts and settings in structured or serialized formats. Running a global replacement without fully reviewing what is being changed can unintentionally affect page builder data, which may lead to broken layouts or missing content. This isn’t a bug in the plugin, but rather the nature of database-wide operations. That’s why we strongly recommend: Always running a dry run / preview first Limiting replacements to specific tables or columns when possible Creating a full backup before executing bulk changes Avoiding blind global replacements when page builders or serialized data are involved Used correctly, the plugin is extremely effective and trusted by thousands of sites but like any advanced tool, it requires a clear understanding of what is being changed and where. We’re glad you were able to restore your site, and we hope this helps others approach bulk replacements more confidently and safely in the future. If anyone needs guidance on best practices or safe usage scenarios, we’re always happy to help.