Page Not Found Error for SMT Landing Pages

In the Mont Blanc release of SuiteCommerce Advanced (SCA), landing pages created using the Site Management Tools (SMT) may generate 404 Page Not Found Errors. This issue has been fixed in the 2018.2 and later releases of SuiteCommerce Advanced. If you experience this issue and cannot migrate to the latest release, you can fix this issue as described in the following procedure.

To implement this patch, create a custom module to override the Application.js file, which is part of the SspLibraries module.

If you are not familiar with implementing patches for SCA, refer to the following:

Before you get started, familiarize yourself with Best Practices for Customizing SCA.
For step by step instructions, refer to Patch Using Override Mode.

Step 1: Create the Override File

Following the instructions and recommendations in the Patch Using Override Mode procedure, create a new directory and file: .../Modules/extensions/SspLibrariesExtension@1.0.0/SuiteScript/Application.js. Then replace code in the new file as described in the following steps.

Find the following line of code in the getEnvironment method:

                SC.Configuration.useCMS = !isSecure && SC.Configuration.useCMS && context.getSetting('FEATURE', 'ADVANCEDSITEMANAGEMENT') === 'T';

And replace it with the following code:

                SC.Configuration.useCMS = SC.Configuration.useCMS && context.getSetting('FEATURE', 'ADVANCEDSITEMANAGEMENT') === 'T';

Step 2: Prepare the Developer Tools For Your Patch

When preparing the Developer Tools for your patch as described in the Patch Using Override Mode procedure, you should:

Paste the following sample code into the new ns.package.json file that you create in the Modules directory: .../Modules/extensions/SspLibrariesExtension@1.0.0/ns.package.json

                {
   "gulp": {
      "ssp-libraries": [
         "SuiteScript/*.js"
      ]
   },
   "overrides": {
      "suitecommerce/SspLibraries@2.2.0/SuiteScript/Application.js" : "SuiteScript/Application.js"
   }
}

Open the distro.json file and then add your custom module to the modules object as described in the Patch Using Override Mode procedure. The distro.json file resides in the top-level directory.

The following sample shows the value to add to the list of existing values that follow the "modules" key.
```
                "modules": {
    "extensions/SspLibrariesExtension": "1.0.0",
    . . . 

              
```

Step 3: Test and Deploy Your Patch

Follow the instructions provided in the Patch Using Override Mode procedure to test and deploy your patch.

Step 1: Create the Override File

Step 2: Prepare the Developer Tools For Your Patch

Step 3: Test and Deploy Your Patch

Related Topics