Summary: | Adding item description to Twitter Summary | ||
---|---|---|---|
Product: | Koha | Reporter: | Caitlin Goodger <caitlingoodger.student> |
Component: | OPAC | Assignee: | Caitlin Goodger <caitlingoodger.student> |
Status: | In Discussion --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dcook, mtompset |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9855 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: |
Bug 17937 Adding item description to Twitter Summary
Bug 17937 Adding item description to Twitter Summary Bug 17937 deleting space around TwitterSummary in OPAC details template Bug 17937 deleting space around TwitterSummary in OPAC details template and add twitter image in metatag |
Description
Caitlin Goodger
2017-01-18 22:59:02 UTC
Created attachment 59192 [details] [review] Bug 17937 Adding item description to Twitter Summary Test Plan to be revised Created attachment 59200 [details] [review] Bug 17937 Adding item description to Twitter Summary Test Plan 1: Apply Patch 2: Enable Twitter Summary and enter a Twitter account 3: To test you can go to this site. https://cards-dev.twitter.com/validator 4: When you tweet about the book it should show the description of the book Created attachment 59816 [details] [review] Bug 17937 deleting space around TwitterSummary in OPAC details template Created attachment 59817 [details] [review] Bug 17937 deleting space around TwitterSummary in OPAC details template and add twitter image in metatag Generates the meta data, but can't figure out how to test. This looks like it's working, although it's hard to test from a development environment which isn't open to the internet. I think this would be a useful improvement, but shouldn't we use Open Graph data instead? Facebook will parse that, and Twitter allows it as a fallback for their own proprietary markup. (In reply to Owen Leonard from comment #6) > This looks like it's working, although it's hard to test from a development > environment which isn't open to the internet. > > I think this would be a useful improvement, but shouldn't we use Open Graph > data instead? Facebook will parse that, and Twitter allows it as a fallback > for their own proprietary markup. I like the sound of that. Bug 9855 makes it look quite simple. |