Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Umb7.12.3 CMSImport V3.7.5
On an upgraded staging site:-
I had to import data from the older live site which then gave me:-
I moved the new Home and children to the Content root and renamed the old Home as Home-Old:-
Now I have a problem that the new Home node's URL in it's "Info" tab is "/home/" and the Home Old node's URL in it's "info" tab is "/home-old".
In a browser, if I go to "/" I get to /Home/home and see a 404 page, but if I go to /home-old I see the old properly formatted home page.
I'm not sure what I need to do to fix this as ultimately I want the new home page to be the proper home page on "/" and delete the site based on the home-old page.
I suspect I need to fiddle with a couple of Id's in the DB but would appreciate some advice.
Not sure what you mean? Can't you just move the nodes up one level? Or did you have some sort of urlalias on the old home node that makes sure the url is correct?
No, there was nothing special about the original home page. It was just a single tenanted installation. The home page was accessible with "/" as normal. CMSImport imported the new site under the original Home page so I just wanted to make it the current home page so "moved" the newly imported site to be under the "Content" node which seems to have messed up both the URLs.
This forum post seems to be a similar issue (https://our.umbraco.com/forum/umbraco-7/using-umbraco-7/66696-how-to-set-the-root-url-when-2-pages-on-root-level) but without a resolution. I seem to remember coming across this before using CMSImport because, as I understand it, it can't import over the root of an existing site to update it. So you have to allow it to import under an existing root, creating a new tree structure. I'm quite happy to admit it's only the second time I've used it and I might have misunderstood. I managed to import several thousand nodes with the right structure though so I was very pleased with that :)
Indeed CMSImport needs a root but can't you just move the child nodes one level up in that case? Or do you need to update regular?
It's just a one-off update to get over some upgrade issues.
What I wasn't sure about though is if CMSImport would create copies of existing nodes or just update existing ones. Also the UI seemed to lead me to select a Home node which is why it ended up as it did, i.e. the full site under a new home node under the original home node. I thought it would be easy just to move the new home node to the root so didn't question it really.
How would you advise it be done?
I reverted the site to how it was before the import and re-ran the import from the second level so avoid creating a new home page. It was to see whether CMSImport would create duplicate pages or update existing ones. Found it skipped all 2,600 pages.
This is a typical line from the log:-
CMSImport:Record skipped during content import, Primary key '@id', primary key value '1246'
Hopefully the graphic below shows enough config detail.
Sorry for delay. This was propably because the selected rootnode was missing. and if you deleted the old imported documents the relation was gone also.
I would just import everything under Home and then after import Move Home to the root.
Hope this helps.
The root node was still there but it just didn't pick anything up. Anyway, I did what you suggested in the end and it's all fine now.
Great to hear it's working now Craig.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted