Skip to content
This repository was archived by the owner on Feb 1, 2019. It is now read-only.

Add GUID to REST API post output for Disqus identification on sheer pages#10

Merged
kurtrwall merged 1 commit intomasterfrom
guid
Mar 31, 2016
Merged

Add GUID to REST API post output for Disqus identification on sheer pages#10
kurtrwall merged 1 commit intomasterfrom
guid

Conversation

@kurtrwall
Copy link
Copy Markdown

@Scotchester
Copy link
Copy Markdown

🚨 n00b alert

What's the difference between the GUID and the ID? And why isn't ID good enough for Disquis identification?

@kurtrwall
Copy link
Copy Markdown
Author

So the GUID is created when the post is saved to the database. If a post is created on content.cf.gov then the GUID would be something like http://content.cf.gov/?p=7234. The Disqus plugin that we have uses the post's ID and GUID to uniquely identify a post to serve that posts' comments. Since we were using that for a while (presumably for the life of Disqus integration), we need to be able to get both in elasticsearch to maintain the comments from the old blog posts on the new site.

@kurtrwall
Copy link
Copy Markdown
Author

As for why it's not good enough, it's possible that it's due to RAMP. Not entirely sure.

@Scotchester
Copy link
Copy Markdown

Yeah. RAMP doesn't maintain regular IDs from Content to Production.

@Scotchester
Copy link
Copy Markdown

👍

@kurtrwall kurtrwall merged commit 30605a6 into master Mar 31, 2016
@kurtrwall kurtrwall deleted the guid branch March 31, 2016 19:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants