Releases: interconnectit/Search-Replace-DB
Releases · interconnectit/Search-Replace-DB
Search-Replace-DB v4.1.2
Changelog
- Now you can suppress the checks for PHP and be able to run this tool in an old setup
Search-Replace-DB v4.1.1
Changelog
- Autoload class in composer.json
Search-Replace-DB v4.1
Changelog
- Ability to connect using SSL, command line only feature
Search-Replace-DB v4.0
What's New
- Support for continuous integration through Travis CI
- Ability to do multiple search-replaces
- Ability to exclude tables
- Remove specific loaders for WP
- No longer automatically populate DB fields, this was causing security issues for users leaving the script on their site
- Script now checks whether the correct version of PHP is used
- Script checks if necessary modules are installed
- Script checks if the connection is secure and gives a warning otherwise
- Bug fixes
- UI Tweaks
- Password is not mandatory in CLI
3.1: Merge pull request #139 from interconnectit/revert-138-master
This version has the following changes.
- Safety checks to prevent deletion when installed incorrectly. However, you should still take care when dealing with files on your server.
- JavaScript popup confirmation on 'Delete Me'.
- Port number option in both the GUI and CLI. Use --port nnn to set a non-default MySQL port.
- Fixed Drupal bootstrap behaviour. Start up of script uses Drupal data as guide, no longer relies on a full successful Drupal initialisation before script will allow you to proceed.
- Driver selection improved so that PDO will be attempted first if PDO+mysql is available, with mysqli being used as a fallback. This fixes 'driver not found' errors.
- Removed mysql_ functions and replaced with mysqli_.
- Improved JS preview overlay for dry runs. This means that the right pane will always show the most accurate data possible. If serialised strings are present, highlights are not displayed.
3.0.0
The first stable release of the safe search replace tool for PHP. The CLI script is much more feature complete in this version with better support for different character sets. There are still problems with UTF-16 and UTF-32 which we hope to try and address in future releases.
Use php srdb.cli.php --help
for the list of options.