I’m thinking you should suggest to the client that a better webhost might be a good idea ... a host that would just randomly do a search & replace in someone’s database is NOT professional or safe.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
August 05, 2011 12:06pm
Subscribe [3]#16 / Aug 08, 2011 1:50pm
I’m thinking you should suggest to the client that a better webhost might be a good idea ... a host that would just randomly do a search & replace in someone’s database is NOT professional or safe.
#17 / Aug 08, 2011 1:53pm
Oh, that’s in the works. We just wanted to make sure they had a copy of the old database and then for me to make sure I got that before we decide to move the site.
The thing that concerned me the most is the alteration of a core EE file as a “fix.” WTF!
#18 / Aug 08, 2011 4:10pm
Lea, glad you got it all squared away.
I was a little suspicious about it being an interaction with that version of PHP, as that seems to be one people thought was stable; but then, those others did have a similar sounding problem.
We’ll probably never know what excited it - buried in the db ‘adjustments’ (they did that too???) of the host.
By the way, my cryptic comment on that Friday just meant I suspected this was one of your institutional sites.
Take care,
Clive
#19 / Aug 08, 2011 6:45pm
Lea, I’m glad you got it working.
If they did a find and replace directly on the database tables, then they likely broke the serialized arrays in the exp_sites table, which would break your installation, we saw that with some frequency before we BASE64 encoded that table in EE 2.
In any case, if anything else comes up, please don’t hesitate to let start a new thread so we can help out. =)