Title: Add Media problem
Last modified: September 1, 2016

---

# Add Media problem

 *  Resolved [silsbyc](https://wordpress.org/support/users/silsbyc/)
 * (@silsbyc)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/add-media-problem-2/)
 * On Firefox, the Add Media button doesn’t pop up the Add Media dialogue.
 * On Chrome, I can get to the Add Media dialogue, but ends in an HTTP failure.
 * Is this an XSS conflict between the front-end (HTTP) and the upload dialogue (
   HTTPS)?
 * [https://wordpress.org/plugins/commentpress-core/](https://wordpress.org/plugins/commentpress-core/)

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Author [Christian Wach](https://wordpress.org/support/users/needle/)
 * (@needle)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486806)
 * Can you describe your WordPress install in a bit more detail for me?
 * Cheers, Christian
 *  Thread Starter [silsbyc](https://wordpress.org/support/users/silsbyc/)
 * (@silsbyc)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486839)
 * We are running WordPress 4.5.2 multisite with CommentPress Core 3.8.9 activated
   on a per site basis.
 * The front end is over HTTP, and the admin panel is over HTTPS. (So I am thinking
   it might have something to do with calling Add Media from HTTP, but it is handled
   over HTTPS)
 * Not sure when Add Media stopped working, as we only usually launch new CommentPress
   sites at the semester and this is the first time a class has reported this problem.
 * Thanks for any insight.
 *  Plugin Author [Christian Wach](https://wordpress.org/support/users/needle/)
 * (@needle)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486849)
 * > The front end is over HTTP, and the admin panel is over HTTPS. (So I am thinking
   > it might have something to do with calling Add Media from HTTP, but it is handled
   > over HTTPS)
 * That sounds likely to be the cause of the issue. I’m not aware of a straightforward
   solution, other than making the front-end HTTPS as well. Not very helpful, I 
   know.
 * Does the plugin that enforces HTTPS wp-admin allow contextual overrides (if that’s
   how it’s being done)?
 *  Plugin Author [Christian Wach](https://wordpress.org/support/users/needle/)
 * (@needle)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486904)
 * Hmm, thinking about this a little more – I can’t quite figure out why there’d
   be an issue with https content embedded in a http context. Have you checked your
   console for any error messages?
 *  Thread Starter [silsbyc](https://wordpress.org/support/users/silsbyc/)
 * (@silsbyc)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486980)
 * The HTTP/HTTPS switch is being done through Rewrite Rules on the webserver, not
   by a plugin. So no contextual overrides.
 * I’ve set up a test server to run fully through HTTPS for troubleshooting. And
   now the “Add Media” button works! (Might also be something to do with upgrading
   to WP 4.5.3 while doing this)
 * Discovered some more data points.
 * If accessing HTTPS front-end, then annotators need to be Editors in order to 
   upload media to the annotation. I think this is new behavior, as previous semesters
   have had Authors leaving image annotations.
 *  Plugin Author [Christian Wach](https://wordpress.org/support/users/needle/)
 * (@needle)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486985)
 * > I’ve set up a test server to run fully through HTTPS for troubleshooting. And
   > now the “Add Media” button works!
 * Good news!
 * > If accessing HTTPS front-end, then annotators need to be Editors in order to
   > upload media to the annotation. I think this is new behavior, as previous semesters
   > have had Authors leaving image annotations.
 * It _ought_ to be available to users with ‘author’ role. Wouldn’t make much sense
   in a WordPress publishing context otherwise. I’ll check against bleeding-edge
   installs and see if I can tease out what’s going on.
 * BTW, thanks for the rating!
 * Cheers, Christian
 *  Plugin Author [Christian Wach](https://wordpress.org/support/users/needle/)
 * (@needle)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486998)
 * > If accessing HTTPS front-end, then annotators need to be Editors in order to
   > upload media to the annotation. I think this is new behavior, as previous semesters
   > have had Authors leaving image annotations.
 * I’ve tried to replicate this on a number of installs, both single and multisite
   and cannot do so. Do you perhaps have another plugin active which modifies the
   author role? You can check by installing one of the many plugins that reveal 
   the capabilities of each role.
 * BTW, thank you! The attempt to replicate the problem did reveal that another 
   plugin of mine – [BP Group Sites](https://wordpress.org/plugins/bp-group-sites/)–
   was incorrectly overriding the media buttons and quicktags editor on the main
   site of a BuddyPress multisite install. If you’re not running BP Group Sites,
   then (obviously) it can be discounted as the cause.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Add Media problem’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/commentpress-core_9b6041.svg)
 * [CommentPress Core](https://wordpress.org/plugins/commentpress-core/)
 * [Support Threads](https://wordpress.org/support/plugin/commentpress-core/)
 * [Active Topics](https://wordpress.org/support/plugin/commentpress-core/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/commentpress-core/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/commentpress-core/reviews/)

 * 7 replies
 * 2 participants
 * Last reply from: [Christian Wach](https://wordpress.org/support/users/needle/)
 * Last activity: [9 years, 10 months ago](https://wordpress.org/support/topic/add-media-problem-2/#post-7486998)
 * Status: resolved