Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Image #155

Closed
wesleyboar opened this issue Sep 6, 2022 · 2 comments · Fixed by #169
Closed

Default Image #155

wesleyboar opened this issue Sep 6, 2022 · 2 comments · Fixed by #169

Comments

@wesleyboar
Copy link
Contributor

wesleyboar commented Sep 6, 2022

Description

Support a default image for all the image meta tags on any page (and a post via djangocms-blog1):

  • Open Graph og:image
  • Twitter twitter:image
  • Schema.org image

Use cases

A CMS user expects that every webpage URL (of their site) that they share on Twitter will display an image, even if the page does not have an meta image uploaded.

Proposed solution

  1. CMS Admin edits a global Meta Information setting.

  2. CMS Admin uploads a "Default Image".

  3. Any page (or djangocms-blog post) missing an "Meta-information" > "Common" > "Image" uses image from step 2.
    (click to toggle detailed steps)
    1. CMS User creates page.
    2. CMS User does not upload a "Meta-information" > "Common" > "Image".
    3. CMS User publishes page.
    4. Any user previews sharing the URL of the page created (in step 3) on Twitter.2
    5. An image is rendered.

Alternatives

Require CMS user upload a default image for every CMS page.

Additional information

N/A

Footnotes

  1. The djangocms-blog repo uses djangocms-page-meta.

  2. (A) User, in the Twitter field to create a tweet, pastes a URL. (B) User, in third-party tweet previewer (example 1, example 2), pastes a URL and clicks preview button.

@protoroto
Copy link
Member

@wesleyboar Hi! We've just released 1.4.0 version with this new feature.

@wesleyboar
Copy link
Contributor Author

wesleyboar commented Sep 19, 2023

Sweet! Thanks.

I'll try out the feature after my team and I get through Django 4 upgrade.

During that though, I think we found the feature introduces a bug:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants