From 3c3acd9f7996f2958ed8883f812088740a6ec5c0 Mon Sep 17 00:00:00 2001 From: Amigo <49749100+aamigo@users.noreply.github.com> Date: Thu, 18 Jul 2019 10:02:11 +0200 Subject: [PATCH] Updated 033 Export Import of fully mapped components (markdown) --- 033-Export-Import-of-fully-mapped-components.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/033-Export-Import-of-fully-mapped-components.md b/033-Export-Import-of-fully-mapped-components.md index 6a2edf8..74c0590 100644 --- a/033-Export-Import-of-fully-mapped-components.md +++ b/033-Export-Import-of-fully-mapped-components.md @@ -63,8 +63,12 @@ There is two features. This 'Force Local Update' may be explained as follow. If ### Warnings - Remapped -You might get these warnings. Now what these warnings is really telling you, [00:13:01](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m01s) is that during the install you realize that lots of ids will change. We are working with a database that creates ids as the new item is added. Since these are the ids is used to link into the various components, views and places, all these ids must be remapped. We have been able to [00:13:30](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m30s) find a very well formulated algorithm to resolve this problem. So it remaps all the ids. Sometimes there are certain ids that wasn't possible to remap. We are telling you about them. You could see that the target field in the admin views has a mismatch in the field with id.244. You can go back to the old install, and try and find out what happened there. [00:14:04](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m04s) Most of the time when I have reviewed this, usually it is because that specific field is no longer published or is no longer available for some reason. So this is just giving you a heads up of any changes that may have occurred. You can go to these various places and manually fix them. Most of the time these warnings will not show and everything will just say all is right. If there is warnings and errors just simply read the messages slowly and closely. I'm sure you'll be able to resolve it [00:14:43](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m43s) quite easily. +[00:12:55](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m55s) + +You might get these warnings. What does this warnings indicate? It is that during the install that you are going to realize that lots of IDs will change. This database creates IDs as the new item is added. Since these are the IDs that is used to link the various components, views and places, all these IDs must be remapped. A very well formulated algorithm has been found to resolve this problem. [00:13:30](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h13m30s) So it remaps all the IDs. Sometimes there are certain IDs which was not possible to remap. It can be seen that the target field in the Admin Views has a mismatch in the field with id.244. Go back to the old install, and try to find out what happened there. [00:14:04](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m04s) Most of the time when I have reviewed this, usually it is because that specific field is no longer published or is no longer available for some reason. So this is just giving you a heads up of any changes that may have occurred. It is possible to go to these various places and fix them manually . Most of the time these warnings will not show and everything will indicate that it is right. If there is warnings and errors read the messages attentively. ### Mapped Components +[00:14:49](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m49s)<<<<<<<<<<<<<<<<<<<<<<<< + Now just to show you that it actually does work, I didn't mention before but it actually moves all the customer files, custom folders, as well as all the images per admin view, site view and wherever to the new install, so it moves it into its right place. So if that is true we should be able to go to the compiler, select any of the components. [00:15:19](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m19s) It should load that components image here, I should be able to just click compile. It should be able to simply compile that component after compilation. I could click installing the component. If this component was correctly mapped previously, and I were to go to that component, I would see that everything about the component is right and it works well. [00:15:51](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m51s) That is this new feature in action. I really hope that it will be as useful to you as it's going to be to me, and that you will have fun with it. I must tell you I suppose that at some point we could even start looking at selling mapped components. I have a number of components that was made for specific purposes, but could be easily adapted for others. [00:16:22](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h16m22s) I'm starting to look at the idea of selling mapped components. It's a little difficult because it's basically selling the rights to it in a way that you could resell it. So I'm not sure what would be the price tag of that.