Resolved Wordpress Customize not saving after migration

[NicolasP.]

Hello.

I am facing a strange Wordpress issue after migration. Wordpress customize does not save settings after migration.

I have about 15 Wordpress Domains and all worked in previous server.

If i install a new Wordpress with Wordpress Toolkit, it works.

CentOS Linux 7.3.1611 (Core)‬
Plesk Onyx Version 17.5.3 Update #19

 

[Aleksey Filatev]

Hello! Could you please clarify, how do you perform a migration?

 

[NicolasP.]

Hello @Aleksey Filatev,

With Pkesk Migration Tool, if that helps you

 

[Aleksey Filatev]

Do you migrate whole subscription, or just sigle site using site importing feature?

 

[NicolasP.]

I migrate the whole server, all the subscriptions. Everything....

I think it might be file permission issue or database issue.

 

[Aleksey Filatev]

So, after migration you see an empty list of WordPress instances in WordPress toolkit, right?

 

[NicolasP.]

No. Everything works fine. Except Wordpress Customize. It cannot save settings.



When I press Save&Publish, it doesn't save the settings

 

[NicolasP.]

I did this now:
I used "All-in-One WP Migration" Plugin to backup my site.
I install it on localhost on my computer and it works.

 

[Aleksey Filatev]

Looks like an issue with permissions on uploads directory inside of wp-content. Could you please check it? Such issues could occurs, for example, if PHP works as mod_php on the source server before migration.

 

[NicolasP.]

I set all folders under upload to 755 and files to 644 but nothing happened

 

[Aleksey Filatev]

All files normally should be owned by system user of subscription, is it right?

 

[NicolasP.]

Yes. User is set up correctly and group is psacln

 

[NicolasP.]

As I said before I install it in localhost and it worked.
After I took a backup from localhost, I create new wordpress installation in my server and import backup with All-in-One WP Migration" Plugin.

But it cannot save again.

 

[NicolasP.]

Now I am setting up Centos 7 and Plesk Onyx on Virtual Box to see if it will work there and I will let you know the results

 

[NicolasP.]

Everything works fine at Virtual Box. I run migration and select only one subscription that had the problem and it worked.