#33459 closed defect (bug) (invalid)
An option on the Tools to export Customizer data
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Customize | Keywords: | reporter-feedback close |
| Focuses: | Cc: |
Description
While changing between hosts, when we copy the database and files to the new host, the customizer data behave oddly. Nothing shows up on customizer section, while the site does have the data stored in database.
Change History (7)
#1
@
10 years ago
- Keywords reporter-feedback added
- Type changed from feature request to defect (bug)
#2
@
10 years ago
I am not doing it for customizer yet. But if an in-built tool was available, it could be of ease?
#3
@
10 years ago
@utsavsinghrathour But what is the underlying mechanism you are using for moving the database between hosts? Are you changing the home URL in the process?
My assumption is that your database is getting corrupted in the migration, specifically that the serialized data is breaking.
#4
@
10 years ago
What I am doing, is changing the URL and regenerating the serialized array and updating the databse. But would love if it would be inbuilt. I could submit a patch for this.
#5
@
10 years ago
- Keywords close added
@utsavsinghrathour I think the process you are using is causing the problem, and that there is not a bug in Core here. I often copy the database from one environment to another and do wp search-replace using WP-CLI to update the hostnames, and I never see the data in the Customizer being dropped on the destination environment.
Thanks for the report. How are you copying the data to the new host? Are you doing host name replacements in the process? If so, are you accounting for replacements made inside of serialize strings?