WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #39811, comment 3


Ignore:
Timestamp:
02/08/2017 03:02:21 PM (5 years ago)
Author:
ivijanstefan
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #39811, comment 3

    initial v1  
    66> * The serialized data has been tampered with, e.g. by using search/replace incorrectly and breaking string lengths. The [https://interconnectit.com/products/search-and-replace-for-wordpress-databases/ Database Search and Replace] script might be helpful in that case to perform search/replace correctly.
    77
    8 Good point, I not use that plugin in this case. Generaly, database is in `utf8_general_ci` format and that can be issue.
     8Good point, I not use that tool in this case. Generaly, database is in `utf8_general_ci` format and that can be issue.
    99
    1010But question:
    1111
    12 Why you not made some "switching" function or something niversal what cover this issue and fix problems? When I ore some other developer want to made fast fix we work directly in database without plugins. Also if we want to move WP from server to other server, we just do export, find/replace path and import new in database. Also when you do some massive migrations from server to server where is 100, 200, 1000 installations, we don't want to install plugins per websites We need to export SQL and import on new server.
     12Why you not made some "switching" function or something universal what cover this issue and fix problems? When I ore some other developer want to made fast fix we work directly in database without plugins. Also if we want to move WP from server to other server, we just do export, find/replace path and import new in database. Also when you do some massive migrations from server to server where is 100, 200, 1000 installations, we don't want to install plugins per websites We need to export SQL and import on new server.
    1313
    1414Just chatting about this issue and I see a lot problems regarding this.