033 Export Import of fully mapped components

Jump to bottom Edit New page

Amigo edited this page Jul 18, 2019 · 14 revisions

EXPORT IMPORT OF FULLY MAPPED COMPONENTS

Various Linked Concepts to A component is Exported

A new feature has been added to the advanced Component Builder for Joomla which can become very useful in the future. It allows you to export a component out of JCB, and not only the component's information, but everything attached to it. 00:00:34 If the component has Admin Views linked to it, and those Admin Views have fields linked to it, and those fields have field types linked to it, and those component has site views, and Custom Admin views, and those Site Views and Custom Admin Views has templates and layouts, and dynamic gets, and all these various linked concepts to a component, is exported.

Two Ways To Export A Component - Encrypted And Non Encrypted

The way to export a component is to simply click on 'Export Components'. Select the component or components that should be exported. There are two ways how a component gets exported. One is an encrypted way, and the other is non encrypted.

Smart Export Builder

Let me show that in the code. There is a method called 'smartExportBuilder'. The 'SmartExportBuilder' gets fired at the very end of the compilation or rather the build. Where all the data has now been extracted from the database and it is now one large array of objects. This data extrusion takes place in the function called 'getSmartExport'.

Export Key

During this process an account is taken of a specific value. That value's name is 'export key'. So in this 'foreach' we are looping through the components that have been selected. If more than one have been selected, then it will check whether there is an 'export key' for that component. It is set in the user interface. When a component is opened, it has a tab called settings.00:03:00 At the bottom of the right-hand column it has a new field called 'Export Key'. Any value may be placed in here. If this value is left empty, and only this(sermonDistributor) component gets exported, then the component will not be encrypted. If a value is added to this (Export Key) field and this component is exported, it will encrypt that component's data; the database values. 00:03:32It will not encrypt attached files or folders or images that are part of this component. It will only encrypt the data from the database.

Export Key - Encrypt All Components

If multiple components are selected, and any one of them has a key, then it will encrypt all the components. It will be explained again in the code how this is done. Return to the code. It needs to be asked: Does this component have an export key? 00:04:16 If it is 'true' and it has a 'string', this key is encrypted in a database. First check if it is possible to encrypt it, and then encrypt the key. Then add it to the key array with the component's ID. An array is being build from each component's key. 00:04:41 If a component does not have a key, it simply ignores this script and it continues building its data set. Then once all the data set of all components are finished, then in the 'smartExportBuilder' it may determined if any keys had been found.

If Any Key - Implode The array

If any keys has been found, the array is going to be imploded and converted to a 'md5' string. We will then use this 'md5' string with an 'Aes' encryption cipher to lock the data. 00:05:37 There is the data(See video). Above here the whole data set has already been changed to a serialized string. There is a string in this(data) variable and here is the whole string encrypted. In this(data) variable is the encrypted value. If there are not any keys, even if that means if none of the components that was selected had any keys set, then it will default simply to do a 'base64_encode'. 00:06:09 That as well,gets written to the file that is part of the package. That is how it exports the data. 00:06:43 So it exports the data and then checks whether there is any keys. So if there is, for example: Export five components, and all five components have keys, all five keys will create a very long string, and then that whole string will be changed into an 'md5' string which is 32 characters. That 32 characters is then used to encrypt the data.

Exporting A Component - Generating A Key

This key which is used to do the encryption, will be shown in the interface after the data has been exported. Go back to the user interface and export a component. The(Learning Manager) component has a key. There are other components that has no keys at this stage.

Learning Manager is used as a demonstration. 00:07:52

Click 'export component' and as may be seen it generated a key, which can then be used to import this package into another JCB. It may be imported it into the same JCB, but it is obviously not necessary. It could also be used as a backup. It is storing the compiled package in the temporary folder at this stage. 00:08:55 Here is a exported component at the moment, if the data sets are not too large and the memory settings on PHP and so forth are allowing this kind of compilation, all components can then be selected and exported. The result will be same. Since only one component is set with a key, all of them will be encrypted with the same key. All of them will be stored in this package. All the components have been exported into this one package.

Importing Components - JCB_smartPackage.zip

To demonstrate the importing of this(JCB_smartPackage.zip) data set, a blank website is used. 00:09:49 This blank website, has no special JCB components. First, JCB has to be installed from GitHub. On GitHub the releases should be opened. 00:10:14 The link is copied to the latest release. Go back, paste that in here(Install From URL) and install it. If the installation was successful, go to Component Builder, and open the components. As may be seen 00:10:43 there is only the demo component. If all these components need to be moved to the new install, click on 'Import Components'. Browse to that package that have just been exported and upload it.

Two Features - Force Local Update - Use Key

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 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 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.

Warnings - Remapped

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 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 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

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 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 That is this new feature in action.