Updated 064 How to install jcb packages (markdown)

Amigo 2019-09-26 06:35:46 +02:00
parent 78e6d1c9ac
commit de020444e3

@ -35,7 +35,14 @@ Then there's also See All Import Information. If it is the first time that you'r
[00:07:04](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m04s) [00:07:04](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m04s)
Then there is also the Component that is Being Imported should show, the same as the one you saw before we have the package. Those of you that have used this area multiple times, you will know that you're able to add multiple components into one package. It's just because we at VDM are distributing one component at a time. That's why there's only one component in the package. In a greater perspective [00:07:32](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m32s) you can import a backup package. That would be then everything that you have done. In my case all the components I've build are zipped in a backup patch package. I can import all of those into JCB at once. At the moment I've tested it up to at least 20 components, which takes a while but it gets there. Then there is also the Component that is Being Imported should show, the same as the one you saw before we have the package. Those of you that have used this area multiple times, you will know that you're able to add multiple components into one package. It's just because we at VDM are distributing one component at a time. That's why there's only one component in the package. In a greater perspective [00:07:32](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m32s) you can import a backup package. That would be then everything that you have done. In my case all the components I've build are zipped in a backup patch package. I can import all of those into JCB at once. At the moment I've tested it up to at least 20 components, which takes a while but it gets there. At this point everything looks fine and you can click continue.
????? ### Takes Awhile To Update - Updating IDs, Views, Fields
Ok so at this point [00:07:59](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h07m59s) Everything looks fine And you can click continue This depending on the size of the component All the size of package Might take longer and shorter And I would just suggest that you wait it out Take a sip Coffee or something It it does take a while because literally at this point It is updating the IDs [00:08:21](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m21s) Everyone One at a time So with every field the IDs are being updated with Every view and everywhere that ID in any other ID is being used anywhere across the component Everything is dynamically being updated During this process And So as you can expect it is a lot of Compilation Lot of algorithm [00:08:41](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m41s) Lot of things happening under the hood And therefore does take a little bit longer than You might expect Because the ID is changed And the way we in export the package Is literally Just taking a photocopy of the package as it is in the JCB where it was Develop Or when it resides And when you imported we now recreate and remap every ID [00:09:05](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m05s) To ensure that it remains functional although basically all it's identifiers have changed Ok so just wait and in the moment it will show you that it's been successful But it does take a while Once it's done You get this Longest especially if it was JCB Which you've imported I mean it's a long list It has over 1000 field so [00:09:32](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m32s) You can anticipate a long scroll I'm gonna grab this thing here and drag it And it goes and goes and goes And it's Huge But they're very much at the bottom you start seeing different things Like the files every little file that has been Imported [00:09:50](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m50s) And that's really helpful If you are importing a package From a developer which you do not No or You're not absolutely sure you can Trust The now you must check Every one of these Fields that they are legitimately related to this component And that it is actually what you anticipated [00:10:09](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m09s) Or expected And you can also Therefore go look at these folders They are all related The custom folder At the moment as we scroll and now here Are some Folders that are related to the administrator VDM compiler Yes This is in the compiler so there's a lot of files for the [00:10:31](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m31s) compiler Joomla 3 Then for the helper this This little thing here is just like a Spacer really By which we sort of Create the string And so there you get all the files that have been moved into place and low and behold There is component builder the fully mapped Package [00:10:51](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m51s) In your system And that's really as simple as it is to get The component that You need Fully mapped Into your system And as you can see All it's Views are correctly mapped in here And if you open any of those views [00:11:07](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m07s) you'll again see that all it's fields Are also Correctly Mapped And You do realize that every one of these Fields their IDs have changed And even The fields They again Have field types [00:11:23](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m23s) And even those Might have changed The field types Itself And so Down to the very Smallest detail we've tried To make sure that every little thing All across the board is remapped [00:11:37](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m37s) And You know Fixed so that your component is again Fully Active and stable ready for further development Ok so that is the quick tutorial on how to import a JCB package into JCB. Ok thanks for watching.
[00:08:04](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m04s)
This depending on the size of the component or the size of package might take longer and shorter. I would suggest that you wait, take a sip of Coffee or something. It it does take a while because at this point it is updating the IDs, [00:08:21](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m21s) everyone one of them one at a time. With every field the IDs are being updated, with every view. Everywhere that ID, and any other ID that is being used anywhere across the component, everything is dynamically being updated during this process. You can expect it is a lot of compilation, a lot of algorithm, [00:08:41](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h08m41s) a lot of things happening under the hood. Therefore it does take a little bit longer than you might expect. Because the ID is changed and the way we export the package, is taking a photocopy of the package as it is in the JCB where it was develop or when it resides. When you import it, we recreate and remap every ID [00:09:05](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m05s) to ensure that it remains functional although all its identifiers have changed. Wait and in a moment it will show you that it's been successful.
Once it's done you get this long list, especially if it was JCB which you've imported. It has over 1000 fields. [00:09:32](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m32s) You can anticipate a long scroll. At the bottom you start seeing different things, the files every little file that has been Imported [00:09:50](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h09m50s) That's really helpful if you are importing a package from a developer which you do not know or you're not absolutely sure you can trust. You must check every one of these fields that they are legitimately related to this component and that it is what you anticipated [00:10:09](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m09s) or expected. Therefore go and look at these folders. They are all related to the custom folder. At the moment as we scroll and there are some folders that are related to the administrator vdm compiler. This is in the compiler so there's a lot of files for the [00:10:31](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m31s) compiler, Joomla 3, for the helper.
This little thing (_v_d_m _) is a spacer which we create the string and there you have all the files that have been moved into place. There is Component Builder the fully mapped package [00:10:51](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h10m51s) in your system. That's as simple as it is to get the component that you will need, fully mapped into your system. All it's views are correctly mapped in here. If you open any of those views, [00:11:07](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m07s) you'll again see that all its fields are also correctly mapped. You would realize that every one of these fields with their IDs have changed. Even the fields, they again have field types. [00:11:23](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m23s) Even those might have changed, the field types itself. Down to the very smallest detail we've tried to make sure that every little thing, all across the board, is remapped [00:11:37](https://www.youtube.com/watch?v=PGmEoliopv8&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h11m37s) and fixed that your component is again fully active and stable ready for further development. That was a quick tutorial on how to import a JCB package into JCB.