Hi Folks, I am running into an issue deploying a new theme based on the SuiteCommerce Base Theme 2020.1. We are creating a brand new SCA 2020.1 website. I have fetched the base theme. I then deployed a new theme based on the base theme via the command “gulp theme:deploy --create”. When I activate the new theme, the Fontawesome fonts are corrupted. I squares in Chrome, and I see the following errors in Chrome console: OTS parsing error: Failed to convert WOFF 2.0 font to SFNT OTS parsing error: incorrect file size in WOFF header OTS parsing error: incorrect entrySelector for table directory Failed to decode downloaded font: https://some.domain.com/sca/extensions/Vendor/MyTheme/1.0.0/fontawesome/fontawesome-webfont.ttf?v=4.7.0 I did a search in Google and it said the build process was corrupting the Fontawesome files, but this post was not related to SuiteCommerce. Anyone run into this and know now to fix?

Hey Keith, I am experiencing the same issue. I'm using the 20.1.0 Theme Development Tools to create a modified version of the SuiteCommerce Base Theme 2020.1. At first I thought it could have been my .gitattributes file corrupting the font files, but I removed it all together and am still having the same problem. It appears to me that it is the build corrupting the font files. If I go directly to the location of the files in the file cabinet and overwrite them with a fresh copy of the font files provided with the Base theme, the fonts will load successfully. However, once you re-deploy the theme, they will be corrupted once again.

Thanks. I tested your idea of overwriting the woff2 file and it worked. It looks like there is a defect in the ThemeDeveloperTools for 2020.1.

Could one or both of you please raise a case for this

I plan to once I have access to the client’s NetSuite Support

Hi @Keith Fetterman, Ran into the exact same issue here with 4 of our themes being deployed in 2020 tools. We found that deploying with the 19.2 tools to the domain still worked for now but obviously not a fix for the ongoing issue. Did you manage to raise a case for this? Cheers Benjamin

Hi Benjamin, thanks for the information. I will be filing the support case later this week.

There has been an update to the extension developer tools and it looks like it should now correct the problem associated with font files. Could you update your tools and try again and see if it fixes the problem please? (It looks like you can get away by just updating \gulp\ns-deploy\fs.js.)

Thanks. I just checked and the Extension Management Bundle has not been updated yet in our client’s account. I’ll check back periodically to see if NetSuite upgraded the bundle. I submitted the support case this morning.

To be clear: upgrade the bundle, then get the new tools in the bundle

Yep. thanks. I just need to wait for NetSuite to upgrade the bundle so I can download the new tools zip file.