Issue: An error message “Sorry, We Couldn’t Find Any Products.” is displayed on the facet of the webstore. The problem is due to how the searchApi.ssp handles the encoding of the double-quotation marks in facets when the Require Login for Pricing feature is enabled with SuiteCommerce Advanced Elbrus Bundle. Solution: Prerequisites: Require Login for Pricing must… Continue reading Resolve “Sorry, We Couldn’t Find Any Products.” Error Message when using Facets with Double Quotation Marks
Tag: elbrus
Resolve the Internal Error on Attempt to Visit a Newly Created Commerce Category in SuiteCommerce Advanced Elbrus
In an Elbrus implementation, The categories for the website is configured using Commerce Categories. The default setup for this record reside in the Facets.Translator.js file, which is located in the Facets module. This section explains how to fix the internal error shown when visiting a newly created Commerce Category on SuiteCommerce Advanced Elbrus. Solution 1.… Continue reading Resolve the Internal Error on Attempt to Visit a Newly Created Commerce Category in SuiteCommerce Advanced Elbrus
How to download the elbrus version tool kit and run local steps.
To download the elbrus version tool kitNavigate to commerce>Hosting>ssp application.Then check the currently used elbrus version view the file open the application folder Link, open the backup folder.Download the latest backup by checking the last time of manifest file and download the first 3 files as given in the screenshot and save the 3 files… Continue reading How to download the elbrus version tool kit and run local steps.
How to resolve error: Could not install from “ns_npm_repository” as it does not contain package.json file
This error will come during npm install or npm i outh1 suitetalk 2 Possiblities:
How to resolve Syntax error: Unexpected token while running Gulp local
To resolved Issue II, follow the instructions below: Steps: Ensure that the node 4.9.1, gulp 3.9.1 and npm 4.6.1 are being used in the development environment. These versions are supported by Elbrus Release of SuiteCommerce Advanced. To verify that Node, Gulp and npm are installed correctly, follow these checklist: To check node, run node -v in the command line window To run multiple Node versions, see article 49023… Continue reading How to resolve Syntax error: Unexpected token while running Gulp local
How to run Elbrus Version in Local System
Before running it we need to ensure that the Node Version and Gulp version are exactly the same as needed in the SuiteCommerce Elbrus version. Ensure that node 4.9.1, gulp 3.9.1, and npm 4.6.1 are being used in the development environment. These versions are supported by Elbrus Release of SuiteCommerce Advanced. o verify that Node, Gulp, and npm is installed correctly, follow this checklist:… Continue reading How to run Elbrus Version in Local System
Error Loading Shopping Page Due to Uncaught TypeError
In some implementations of Elbrus, the shopping page returns a blank page and the following error is returned in the log for the page: Uncaught TypeError: Cannot read property ‘indexOf’ of undefined This error can occur because the URL includes the percent sign (%) and SuiteCommerce does not correctly handle the symbol. This patch overrides… Continue reading Error Loading Shopping Page Due to Uncaught TypeError
SyntaxError: Unexpected token While running gulp local in SuiteCommerce Advanced Elbrus
Ensure that the node 4.9.1, gulp 3.9.1 and npm 4.6.1 are being used in the development environment. These versions are supported by Elbrus Release of SuiteCommerce Advanced.To verify that Node, Gulp and npm are installed correctly, follow these checklist: To check node, run node -v in the command line window To run multiple Node versions, see article 49023 Use Multiple Node.js Versions for SuiteCommerce Advanced Deployment To check… Continue reading SyntaxError: Unexpected token While running gulp local in SuiteCommerce Advanced Elbrus
Invalid left-hand side in assignment: SuiteCommerce Advanced Elbrus
For resolving this open package.json and make sure that the following dependencies are added “dependencies”: {………“xmlbuilder”: “11.0.0”,“xml2js”: “0.4.5”,“yargs”: “1.3.1”,“credentials-inquirer”: “file:./ns_npm_repository/credentials-inquirer”,“suitetalk”: “file:./ns_npm_repository/suitetalk4node”,“preconditions”: “file:./ns_npm_repository/preconditions”}, Delete the node_modules and LocalDistribution folders and run npm install again
Working with SMT Landing Pages in a Sandbox Account
When working with Site Management Tools in a sandbox account, It is needed to configure the URL for landing pages to reflect the domain of the sandbox environment. If you fail to set this configuration property, you receive a Page Not Found error when attempting to access an SMT landing page in the sandbox environment. Configure Properties… Continue reading Working with SMT Landing Pages in a Sandbox Account