WPPizza – A Restaurant Plugin for WordPress › Support › General Support › Upgrading to v3, issue cloning/migrating from developer site
- AuthorPosts
- 11 November, 2017 at 8:30 pm #32695
Hi Oliver,
I have successfully upgraded v3 from 2 on our developer site, testing etc. all works great.
I tried to clone it to our public site (using WP Clone), and am getting the following errors for our food items:
Warning: Invalid argument supplied for foreach() in /home/picassoshr1/public_html/wp-content/plugins/wppizza/classes/subpages/subpage.posts.php on line 352 and so on for all the food items. All sorts of other issues found throughout WP PizzaAll plugins have been updated on developer site before the cloning process.
OK, UPDATE: it was a bad cloning process. I did another WP Clone backup on the developer site and tried again, and the 2nd attempt worked on the public site.
Just an FYI in case it happens to someone else.
13 November, 2017 at 4:40 pm #32753i really cannot comment
clearly there’s a difference between the setup on your 2 sites/server setups; perhaps you simply ran out of memory, time limits, set errors/notices to be output instead of logged or whatnot (hence all the things to set in the “how to upgrade” instructions)14 November, 2017 at 1:35 am #32779Hi Olly,
I sent a separate message, but the clone did not work after all. At all. My ingredients look like default ones, not my work, and the site seems to have more pages that I have on the developer site.
I am looking for recent posts related to cloning, but is there anything you have used recently that seems to work? I’ve never had a problem with this before, only once I upgraded to v3.
Cheers,
14 November, 2017 at 1:37 am #32780We did follow the instructions in the upgrade documentation for the developer site, and the website has been working just fine. It only seems to be the clone that is not working
15 November, 2017 at 7:33 am #32817Hi Oliver,
If you want to delete this forum post, you are welcome to.
Something between the WP Pizza, WordPress, and WP Clone versions created a real gong show for the backup/restore from the developer site to our public site. My IT guy was able to successfully clone the site, but he did it more manually than in the past. He said something about the new site being larger in overall size than what we had before, but playing with the WP Clone settings did not seem to help with a successful cloning process.
We are working on another option that I can use myself for making site changes.
Cheers,
Rob
- AuthorPosts
- The topic ‘Upgrading to v3, issue cloning/migrating from developer site’ is closed to new replies.