Support

I was able to get it to work but I had to delete the weird code message from the two Find/Replace boxes in the last step. THEN I just put in the old domain name on the left and the new domain on the right to do the find/replace. I deleted the weird code message. Is this OK if I delete it? What did the weird code mean?
Here it is...
<br />
<b>Warning</b>: array_keys() expects parameter 1 to be array, object given in <b>/home/vall2016/public_html/installation/platform/views/replacedata/tmpl/default.php</b> on line <b>36</b><br />
<br />

BELOW IS THE REPLACE CODE WHICH WAS IN THE RIGHT BOX

<b>Warning</b>: implode(): Invalid arguments passed in <b>/home/vall2016/public_html/installation/platform/views/replacedata/tmpl/default.php</b> on line <b>36</b><br />

Hello Davide, I will be sure to update all my Abeeba Backups to the latest version next time. Can you tell me if I was OK to just delete that weird replacement code block and just add in my before and after DOMAINs?

Thank you for the GREAT support.

I was not able to rename the installation/platform/models/wordpressreplacedata.php file to lower case because I manually deleted the whole directory after restoration because the process did not give me the normal button to auto delete it. Things were weird from the beginning with that odd replacement block of code (that I decided to just delete)
Even though I inserted the old domain and new domain in the replacement boxes respectively, the actual links in the site did NOT rename. The links were broken and I had to do a DB dump, then I used an online tool (that I trust) to do renaming and serialization. I then imported that renamed SQL into a clean DB and linked to it in wp-config file. Here's the tool if it helps anyone http://pixelentity.com/wordpress-search-replace-domain/

I'm understanding that if I would have started with the updated Akeeba backup for WP version, there would have been no issues.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.