search

welaika / wordmove

Multi-stage command line deploy/mirroring and task runner for Wordpress
https://wptools.it/wordmove
MIT License
1.87k stars 167 forks source link

Error with final phase of DB Move #300

Closed wbuist closed 8 years ago

wbuist commented 8 years ago 
local | adapt dump

/Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/sql_adapter.rb:44:in `gsub!': invalid byte sequence in UTF-8 (ArgumentError)

Any ideas on what I need to do to fix this?

wbuist commented 8 years ago

Interestingly if i run the dump.sql with phpmyadmin it runs happily. The website though won't load on chrome (no data returned) but loads fine on safari.

That's odd too.

wbuist commented 8 years ago

Tried going the other way (push to staging) and still get this error

local | adapt dump /Library/Ruby/Gems/2.0.0/gems/wordmove-1.3.1/lib/wordmove/sql_adapter.rb:44:in `gsub!': invalid byte sequence in UTF-8 (ArgumentError)

Any ideas?

alessandro-fazzi commented 8 years ago

The help about these issues is in the wiki: https://github.com/welaika/wordmove/wiki/invalid-byte-sequence-in-UTF-8-while-pushing---pulling-db

With the baleful advent of utf8-mb4 those problems are arising everywhere for everyone who is using staging/production environments with mysql versions prior to 5.5.3; and the only Wordmove's fault - imho - is that it not trying to alter your encoding/collation automagically because it could leads to loss/degradation of some data.

Closing this one. Follow-ups are always welcome