Hi Everyone, We have Themes and extensions that ru...
# suitecommercec
Charan
12/30/2019, 2:27 PMHi Everyone, We have Themes and extensions that runs on 2019.1.2 version. we have upgraded the source to 2019.2.2 version. After that, In local environment we are seeing below errors. But in the live site It's working fine. Does anyone encounters the same Issue before?
k
kkennedydesign
12/30/2019, 4:09 PMare your running theme or extension local? Be sure to fetch so you have all the files needed.
c
Charan
12/30/2019, 4:33 PM@kkennedydesign we are running source modules
k
kkennedydesign
12/30/2019, 6:31 PMProbably there are new templates in the latest theme you are missing. Does local render at all? I wouldn't think you would have to update your theme, but perhaps you do to have all the latest templates
c
Charan
12/31/2019, 11:06 AM@kkennedydesign May I know Is SCA source 2019.2 core modules are compatible with 2019.1 themes and extension version?
k
Keith Fetterman
12/31/2019, 4:18 PM@Charan, this was a bug in the SCEM 2019.1 developertools and it looks like they haven’t fixed it in 2019.2. I have seen this when a theme from a previous version is used with a later version of SCA/SCS. The dependency loading is looking for the compiled template javascript files when it loads the new view javascript files that didn’t exist in the previous versions. This is only a problem when developing in local development mode.
Keith Fetterman
12/31/2019, 4:19 PMBTW, if you are developing with a later version of SCA in local mode, you can also see this problem.
Keith Fetterman
12/31/2019, 4:23 PMTo work around the problem in a later version of SCA, I create empty compiled template javascript files in the LocalDistribution folder for each error I see in the console. For example “SCA_ROOT/LocalDistribution/paymentinstrument_creditcard.tpl.js”
Keith Fetterman
12/31/2019, 4:23 PMThis only works for SCA development.
Keith Fetterman
12/31/2019, 4:24 PMFor theme/extensions development, you might be able to do the same but I haven’t tried.
Keith Fetterman
12/31/2019, 4:24 PMYou can also create empty template files in your theme and deploy/activate the theme.
c
Charan
12/31/2019, 4:31 PM@Keith Fetterman Thanks for the valuable information. Also, I have a question - Does SCA supports backward compatibility with source ? Suppose Is it possible to use SCA 2019.2 source modules with Theme and extension tools version with 2019.1 version? I have bit of confusion with compatibility. Do you have any idea on this?
k
Keith Fetterman
12/31/2019, 4:32 PMFlo said it is suppose to. This is also a problem with SCS, which is automatically upgraded every 6 months. SCS and SCA are the same code base, except one is locked.
Keith Fetterman
12/31/2019, 4:35 PMI reported two problems with local development of themes/extensions/SCA source when working with older versions themes and extensions and newer versions of SCA/SCS. The problem that you are experiencing with missing compiled template javascript files, and you can get out of order dependency loading. We experienced this second problem with some of the SuiteSuccess B2B extensions.
Keith Fetterman
12/31/2019, 4:39 PMI am working with 2019.1.6 SCA and 2019.1.1 SCEM that’s running a 2018.1 theme. To get around the problem that you are experiencing, I obtained a copy of the index-local.ssp file from a 2018.2.1 SCA zip file, added it to 2019.1.6 SCA code, made some changes to it and modified a gulp file so it would compile it correctly. With that, I don’t have to add the blank compiled javascript files to LocalDistribution folder. It works for theme/extension local development.
Keith Fetterman
12/31/2019, 4:40 PMBTW, these problems didn’t exist in 2018.2.1
28 Views