Verification and debugging

At a certain point while provisioning and configuring a new Optimizely {user["product-name"]} environment, {user["product-name"]} creates a link between the cloud application and the Github repository that houses your server-side extensions and themes. This link is called a Theme Source and can be viewed in the Admin Console. To view your theme sources in the Admin Console, go to Themes & Content > Theme Library > Theme Sources. When the {user["product-name"]} application is configured with a theme source, it will periodically check for changes in the Github repository and pull in new themes and existing theme changes and load them into the {user["product-name"]} database.

The theme source detail page contains information about the source, including information about when the linked Github repository was last polled for changes and whether or not any new changes were pulled in and consumed by {user["product-name"]}. This information can be useful for debugging the link between {user["product-name"]} and your theme source.

When debugging the link made by a theme source, the Last Checked For Changes Status field can be especially helpful. This field will either indicate a success or failed status. If the status is failed, you can check the Application Logs in the Admin Console for further diagnostic information, located at Administration > System > Application Logs.

If your themes have been pulled into {user["product-name"]} successfully, you can verify by heading over to Themes & Content > Theme Library > Themes and checking that your theme exists and the related theme resources are up to date. The theme resource detail page includes a finger tab that displays the current code for that resource.