Hello friends. Has anyone had an experience where ...
# suitecommercea
ANHE
07/21/2021, 4:52 PMHello friends. Has anyone had an experience where the "backup" file zip(s) result in an incomplete collection of the source code for compiling legacy SCA v.Elbrus? I've downloaded a customer's backup from the last command line deploy, but it will not compile on the command line.
Three problems with it:
1. The distro.json file is intact and references a few custom modules, including one for an integration with a third party CRM service. When I run gulp local, it says the module does not exist. Looking at the module, the ns.package.json file is missing, which explains why gulp does not find it when the distro.json has it as a module, and includes in shopping.ssp. I added an ns.package.json and then it worked. The same thing recurred with 5 other custom modules.
ANHE
07/21/2021, 4:55 PM2. Some of the custom modules are just for template overrides, and although the ns.package.json file is in the module so that it does compile, the JSON is just {overrides: object }. What's weird is there is no gulp object in the JSON to direct compilation of the templates, javascript, configuration, etc. I can understand maybe this isn't needed if it's just overrides but in some cases new .JS files were added, so of course they were not being found without the gulp declaration. Adding that gulp object to all those files missing it fixed that problem.
ANHE
07/21/2021, 4:57 PM3. Finally hit a complete roadblock where a custom template file could not be found. Since it's custom, and we're inheriting this work from a third party developer, we don't have any way of knowing what is custom in the template because it doesn't exist anywhere in the backup.
Requested the complete backup from the previous developer, and their backup is the same as the one in the file cabinet, as #1, #2, and #3 above. Things are missing, incomplete, and it won't compile or run local.
ANHE
07/21/2021, 5:00 PMSince the work is originally third party, and since the customer is live on SCA, we can't possibly do any fixes, changes, or new work without risk to losing existing work that we just don't know about.
My next strategy is to pull down previous backups to see if I can frankenstein a few together, but I'm not confident with the risks. Without a working backup of the current site, there's no way to restore it if deploying a new version 'loses' anything from its current state.
c
Christopher Dembek
07/21/2021, 10:06 PMDid the original developer use Bitbucket or Github? Just wondering if they could provide access?
a
ANHE
07/22/2021, 12:46 AM@Christopher Dembek They sent me the backup they had committed to their repository, based on what they downloaded from file cabinet to commit to the repository. Sounds like the developer did not keep the uncompiled non-backup Modules source actually used for local development before deployed to environment. Only the backup from the file cabinet after that. I don't think I have many options.
2 Views