Making WordPress.org

Opened 7 years ago

Closed 4 years ago

#2466 closed defect (bug) (wontfix)

WordCamp images stored with http URL

Reported by: garyj's profile GaryJ Owned by:
Milestone: Priority: low
Component: WordCamp Site & Plugins Keywords: has-screenshots needs-patch good-first-bug
Cc:

Description

When uploading images to the 2017 WordCamp London site via the normal Media page, the images are being saved with a http URL. This means that:

  • images inserted into content has the http URL.
  • images used for the sponsors shortcode output use http URL.

The wp-admin and the front-end, are both trying to display as https (good), but the images are creating mixed-content warnings.

We can workaround the first issue by adjusting the post content markup, but other instances such as sponsors shortcode markup (which, for us, appear in a widget on every single page) can not be worked around. This means that potential attendees are being asked to enter their ticket details on a page that isn't marked as secure.

Possibly related to #2348. The 2017 WordCamp London site was created in late 2016.

Slack discussion: https://wordpress.slack.com/archives/meta-wordcamp/p1486043623002014

Attachments (1)

Screenshot 2017-02-02 14.17.00.png (33.7 KB) - added by GaryJ 7 years ago.
Screenshot of media details box, showing file is stored with a http URL reference.

Download all attachments as: .zip

Change History (6)

@GaryJ
7 years ago

Screenshot of media details box, showing file is stored with a http URL reference.

#1 @iandunn
7 years ago

  • Keywords needs-patch good-first-bug added
  • Owner set to iandunn
  • Status changed from new to accepted

#2 @iandunn
6 years ago

  • Owner iandunn deleted
  • Status changed from accepted to assigned

#3 @iandunn
6 years ago

  • Priority changed from normal to low

Related #2348

This ticket was mentioned in Slack in #meta-wordcamp by ryelle. View the logs.


4 years ago

#5 @ryelle
4 years ago

  • Resolution set to wontfix
  • Status changed from assigned to closed

This is happening on the 2017 WordCamp London site because the site URL (in the database) is non-https. This should not be the case for any current sites, so closing this issue.

Note: See TracTickets for help on using tickets.