Front-end demo site "Daily Recipe" (SAP CDC/Gigya)

[timoreinsch]

Hi everyone,

I'm new to SAP Customer Data Cloud (Gigya) and wanted to use the CDC demo site "Daily Recipe" offered by SAP to learn how CDC works (https://developers.gigya.com/display/GD/Demo+Site).
I get this demo front-end started in my browser via localhost. But unfortunately the demo doesn't interact with my CDC site I created in the CDC Console (back-end) like opening my registration screen. I simply followed the instruction for installation and added my API and Secret Key to the respective file. The screen-set collection name should be correct as I didn't change it.

Debugger shows following errors:

Anybody ever used the demo website successfully and can help?

[spu230479]

Hey timoreinsch it's looks like the debugger error hasn't been attached to your question. One of the things you can do to test to see if your site and screen sets are configured correctly is to manually call API to display the screen set from the developers console in your browser https://developers.gigya.com/display/GD/accounts.showScreenSet+JS. If this doesn't work you will get an error in the network tab of the developers console. If it does work then this may point at a configuration issue of your site, at this point I'd recommend double checking the configuration settings instructions in the readme file.

Thanks

Stephen

[timoreinsch]

Hi spu230479,
thanks for the info - I just edited an error screenshot to my question.
As you suggested, I manually called my API and it works. My API and screen-sets also work with another simple front-end a colleague just built.
Even after checking my configuration settings with a developer/colleague, we couldn't find an error except for the ones from the debugger.

[spu230479]

Hi timoreinsch what i would recommend doing next is using the developers console to debug your site. If you click on the login with the network tab open you can see the API call to get the screen set. You can check the payload to ensure the correct screen is being called and the API key is configured correctly. You can also click on the response tab to ensure that you aren't receiving an error.