Hey Ptpublic,
Run through the installer first, then before you save your permalinks or navigate to the wp-admin ftp all your files over…
Cheers~
Thanks for the quick reply! This is a good method for those of us whose host will not allow us to create a large package because of timeout problems.
So it looks like I had a pretty successful copy – except I have a lot of serialization errors like this one:
SELECT meta_value FROM wp_postmeta WHERE meta_id = “12”;
What does this mean? What is serialization? Is this related or should I post this as a separate question?
Serialization is somewhat technical. But not too difficult if you study it a bit basically you will need to run the query and look at the data. If the string value isn’t the right length you have to adjust the string length to meet the replacement value. If it looks too difficult you can ignore it, pending your not experiencing any issues on your site…
Cheers~
Yeah, a little technical for me. Can you explain why this can be ignored? Things seem to be working, but the “problem” is that they are working to well!
The reason I created this copy is to debug a site that has become terribly slow. I have done a lot of optimization tricks already but that’s another story for another time. The thing is the copy I just made is much faster than the original and I am wondering if this serialization thing is a factor in that. The database is about 6MB and I had just under 300 serialization errors, all in the wp_postmeta section, which is one of the largest sections of the original database.
So if I log into phpmyadmin can you give me an example of what I need to do? When you say “run the query” what exactly are the steps?
Thanks,
PT
It could be ignored if the value that was stored in the postmeta field and was falsely flagged as a serializable string. If you what to run say two of the queries that that you saw and paste the data here I can take a look at it. Just make sure that any of the data you post doesn’t contain any sensitive data like a password.
OK, I see what is happening. I ran some of those queries and they are all looking for my podcast files in the wrong place. I think if I were to replace “http://dev.mysite.com/podcast/” with “http://mysite.com/podcast/” for each of these entries it would do the trick. What’s the magic formula for batch processing that?
I really appreciate all your help.
PT
If the value looks something like this:
{s:30:”http://dev.mysite.com/podcast/”;}
This it would need to change to this:
{s:26:”http://mysite.com/podcast/”;}
Where s:n is the length of the string. This is one of the processes the plugin is suppose to run for you, but for some reason it had errors with your data. You might try this tool its based on the same logic as the Duplicator.
