Conversation
supportHi there! I am in the midst of migrating a site running Cooked (with Cookiteer theme) to a completely new install. I used wordpress’ export function, but after importing, the recipes did show up, but instructions and ingredients are completely lost. Do you have a recommended way of migrating the recipes to a new Cooked install?
Hello @alukacshu , The default WordPress export and import feature should work. But I just tested it right now and there is a bug with it that is causing the issue you are describing. The post meta data is getting corrupted and failing the import process. I am working on a fix right now, once I have it ready I will release a patch version that includes the fix.
I was able to track the issue down to this core WordPress issue: https://core.trac.wordpress.org/ticket/23275
@alukacshu I have published v1.11.1 which should contain the fix that correctly saves the recipe data so that the export and import does not fail. Unfortunately I am still working on a process that will automatically do this for all existing recipes. Currently, for it to work, you would need to re-save all your recipes. But there is a tricky part with this itself. When you open and save a recipe and you don’t change anything, the data does not actually save. Only when you make a change and hit Save, then only its updated.
Hello, Is there any update for this? I have a website right now that needs to migrate 200 recipes. We can manually resave them but it will be a very time consuming task.
Hello @368durham , I already have a solution in place for this and will be coming out in the next version which is being tested. There were a couple of small regression issues found during testing that is holding it up, but it should be ready soon. If you want to reach out to me via email at support [at] cooked.pro I can send you an early release that you can use for doing your migration. Let me know if you are ok with this.
That is fantastic! I’ll reach out shortly.
Hey @alukacshu , version 1.11.2 was just released that includes the fix that will automatically repair any bad data with recipes. Allowing you to export and import them.
Hello @alukacshu , The default WordPress export and import feature should work. But I just tested it right now and there is a bug with it that is causing the issue you are describing. The post meta data is getting corrupted and failing the import process. I am working on a fix right now, once I have it ready I will release a patch version that includes the fix.
I was able to track the issue down to this core WordPress issue: https://core.trac.wordpress.org/ticket/23275
@alukacshu I have published v1.11.1 which should contain the fix that correctly saves the recipe data so that the export and import does not fail. Unfortunately I am still working on a process that will automatically do this for all existing recipes. Currently, for it to work, you would need to re-save all your recipes. But there is a tricky part with this itself. When you open and save a recipe and you don’t change anything, the data does not actually save. Only when you make a change and hit Save, then only its updated.
Hello, Is there any update for this? I have a website right now that needs to migrate 200 recipes. We can manually resave them but it will be a very time consuming task.
Hello @368durham , I already have a solution in place for this and will be coming out in the next version which is being tested. There were a couple of small regression issues found during testing that is holding it up, but it should be ready soon. If you want to reach out to me via email at support [at] cooked.pro I can send you an early release that you can use for doing your migration. Let me know if you are ok with this.
That is fantastic! I’ll reach out shortly.
Hey @alukacshu , version 1.11.2 was just released that includes the fix that will automatically repair any bad data with recipes. Allowing you to export and import them.