Troubleshooting Guide
Siddharth Palaniswami edited this page Mar 24, 2016
·
3 revisions
We have put together a list of potential issues you might run into with recommendations on how you can identify the problem or workaround it. This list will hopefully shrink with time ;)
- Use the edit link to open the edit wizard of the site on Author
- Check there is a different theme
- Save to exit the wizard
- Publish the site and wait for the confirmation
- Open the publish side site
- If the theme is still missing, we might have to do a hard refresh. (
ctrl + r
for chrome) - Or open the same link in a different browser of incognito
- Publish the site a gain
- Wait for the green dialog
- This could be a latency issue, and we have no other choice but to wait
- Edit the site again
- Click the save button
- In case of error there will be a red dialog with error details (could be config issues or missing fields)
- If not able to resolve the issue, edit the existing sample or a different site
mongod status
- Open cygwin and paste the commands
curl http://localhost:8983/solr/communities/update -H "Content-type: text/xml" --data-binary '<delete><query>*:*</query></delete>'
curl http://localhost:8983/solr/communities/update -H "Content-type: text/xml" --data-binary '<commit />'
- Open cygwin and type
curl -s -u admin:admin -d 'batchSize=10000&path=/content/usergenerated/asi/mongo/' http://localhost:4503/services/social/datastore/mongo/reindex
- Open
crx/de
on author - Navigate to
/etc/designs/social/console/jcr:content/basepage/content
- The node should have a "components" property of type String []
- One of the components should be
/libs/social/reporting/analytics/components/hbs/communityactivitylist
- If it's not there, add it and save
- Refresh page with sidekick
- Community Activity List should appear after page reload
- Open javascript console in browser
- Check for any errors
- If none and spinner is still showing after more than 60 seconds, refresh the page and regenerate report
- Open
crx/de
on author - Navigate to
/content/sites/communities/en/jcr:content
- The node should have a
"cq:cloudserviceconfigs"
property of typeString[]
- One of the components should begin with
/etc/cloudservices/sitecatalyst/
- If not, we need to re-enable the site for Analytics through the communities sites console.
- If yes, we need to repeat steps 1-4 on publish to make sure the same exists on publish.
- If not, we need to re-replicate the site.