Timeline for Upgrade from DXA 1.7(.Net) to SDL DXA 1.8 (.Net) for SDL Web 8.5 system
Current License: CC BY-SA 4.0
15 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 30, 2020 at 17:44 | history | edited | Rick Pannekoek |
edited tags
|
|
Jan 23, 2020 at 6:56 | vote | accept | Naveen Anand | ||
Jan 22, 2020 at 13:47 | answer | added | Jaime Santos Alcón | timeline score: 2 | |
Jan 22, 2020 at 6:20 | history | edited | Naveen Anand | CC BY-SA 4.0 |
added 42 characters in body
|
Jan 22, 2020 at 5:46 | comment | added | Naveen Anand | Thank you for your reply @HaraldHoffelinck. Please see the error message when i ran the command :- cms-import.ps1 -importType "master-only" -rootPublication "X_000_Empty" -masterPublication "X_100_Global_Functional_Master" | |
Jan 22, 2020 at 5:45 | history | edited | Naveen Anand | CC BY-SA 4.0 |
added 279 characters in body
|
Jan 21, 2020 at 8:54 | comment | added | Harald Hoffelinck | In that case, your solution to specify the rootpublication and masterpublication names should solve this - this way, the install script will update the tbbs it finds in there. One caveat - if you also renamed the folders where the core DXA items are located, then you might have a problem, as then the installer will create new items in these default folders, instead of updating the existing ones | |
Jan 21, 2020 at 5:15 | comment | added | Naveen Anand | Hi @HaraldHoffelinck, Thank you for your reply. I have already upgraded the web application and now i need to upgrade DXA to CMS side. Once, I ran the above mentioned ps script and it was created default publication :- 000 Empty, 100 Master, 110 DXASite Type, 200 Example Content, and 400 Example Site, which I don't want, by the way i have rolled back the changes which occurred by the PS script. My intention to upgrade my existing publication "X_000_Empty and X_100_Global_Functional_Master". | |
Jan 20, 2020 at 15:26 | comment | added | Harald Hoffelinck | The upgrade import will not empty the existing publications, it will overwrite any of the core DXA templates and tbb's. This will make sure that whatever you publish will make use of the DXA 1.8 codebase. Next to that, you should also upgrade your web application (I believe this is the biggest part of the upgrade). | |
Jan 20, 2020 at 8:39 | history | edited | Naveen Anand | CC BY-SA 4.0 |
added 283 characters in body
|
Jan 18, 2020 at 11:37 | history | edited | Naveen Anand | CC BY-SA 4.0 |
deleted 21 characters in body
|
Jan 18, 2020 at 6:18 | comment | added | Naveen Anand | Thank you for the reply! I want to upgrade them and I meant should not change the root and master publication and also should not change the blue printing. | |
Jan 17, 2020 at 14:10 | comment | added | Jaime Santos Alcón | Do you want to upgrade or create a new publication with 1.8? Cause when you say "without disturbing these publications", that implies that you don't want to upgrade them? It would help if you share the error you get from running the script. | |
Jan 17, 2020 at 10:02 | history | edited | Atila Sos | CC BY-SA 4.0 |
edited body; edited tags; edited title
|
Jan 17, 2020 at 9:47 | history | asked | Naveen Anand | CC BY-SA 4.0 |