From 055113a743223ee1c00b1886eb40358987f2d370 Mon Sep 17 00:00:00 2001 From: Amigo <49749100+aamigo@users.noreply.github.com> Date: Thu, 18 Jul 2019 12:02:32 +0200 Subject: [PATCH] Updated 033 Export Import of fully mapped components (markdown) --- 033-Export-Import-of-fully-mapped-components.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/033-Export-Import-of-fully-mapped-components.md b/033-Export-Import-of-fully-mapped-components.md index 31bfe1f..2a480dc 100644 --- a/033-Export-Import-of-fully-mapped-components.md +++ b/033-Export-Import-of-fully-mapped-components.md @@ -57,16 +57,16 @@ To demonstrate the importing of this(JCB_smartPackage.zip) data set, a blank web [00:11:13](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m13s) -There are two features. This 'Force Local Update' may be explained as follow. If under normal circumstances an import is done, the import function looks at the data that are currently in this JCB install. For example: Field types, Fields, Admin views and Site views is involved. [00:11:42](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m42s) If it finds a site view that is being installed, that is already in the current database, it looks at the last modified date, and then by that determines whether the current installed version is the most recent. If it is the latest version, it will by default ignore the new data and not install it. Sometimes you may get a package, which make it necessary to force it to update the current data even though it may include all the data. This is the function of the 'Force Local Update' switch. Click 'yes' to force the update. [00:12:20](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m20s) As there is a key for this package, the switch should remain 'yes'. Copy that key from Joomla Components. This key will then always be necessary if this package is imported. Click continue. This is quite a huge dataset and may take a while. You could just patiently wait. It will indicate that the install had been successful. +There are two features. This 'Force Local Update' may be explained as follow. If under normal circumstances an import is done, the import function looks at the data that are currently in this JCB install. For example: Field types, Fields, Admin views and Site views is involved. [00:11:42](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m42s) If it finds a site view that is being installed, that is already in the current database, it looks at the last modified date, and then by that determines whether the current installed version is the most recent. If it is the latest version, it will by default ignore the new data and not install it. Sometimes you may get a package, which make it necessary to force it to update the current data even though it may include all the data. This is the function of the 'Force Local Update' switch. Click 'yes' to force the update. [00:12:20](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h12m20s) As there is a key for this package, the switch should remain 'yes'. Copy that key from Joomla Components. This key will then always be necessary if this package is imported. Click 'continue'. This is quite a huge dataset and may take a while. It will indicate that the install had been successful. ### Warnings - Remapped [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. +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 is used 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 can not be remapped. 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 previous 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 it is because that specific field is no longer published or for some reason is no longer available . So this is just 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. This has been a demonstration of this new feature. ### Mapped Components [00:14:55](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h14m55s) -It moves all the customer files, custom folders, as well as all the Images per Admin View, Site View etc., to the new install, it moves it into its right place. If that is true it should be possible 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 component's image(See video), When compile is clicked it should be able to compile that component after compilation. Install the component. If this component had previously been mapped correctly , on going to that component, it will be clear that everything works well. [00:15:51](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m51s) That is this new feature in action. +To show that it work properly: It moves all the customer files, custom folders, as well as all the Images per Admin View, Site View etc., to the new install, it moves it into its right place. If that is true it should be possible 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 component's image(See video), When compile is clicked it should be able to compile that component after compilation. Install the component. If this component had previously been mapped correctly , on going to that component, it will be clear that everything works well. [00:15:51](https://www.youtube.com/watch?v=lkE0ZiSWufg&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h15m51s) That is this new feature in action.