Question about Refinery Logo and Link on Edit Pages

[frank]

I have a fairly unique situation, it seems. I have several Refinery
sites that are actually served up using https in a secured
environment. The problem I have is that the Refinery icon on the edit
page causes browsers to display a mixed content warning on the page
because the link to the icon is "http://refinerycms.com/images/
refinery/logo-site-bar.png". I have been looking around to see if I
can find where this page part is generated. So far I have been
unsuccessful in doing this. It looks like my best option is to move
the icon local to my server because the Refinery CMS server doesn't
support https. So having a refernce to the logo like this "https://
refinerycms.com/images/refinery/logo-site-bar.png" creates an error.

Does anyone know if I can override the location of the logo, so that I
can serve it up from my secured server and get rid of the browser
errors? This is driving me and my customer crazy and they require me
to serve it up using https.

[Dennis Monsewicz]

If you create the folder structure that the image is referencing inside
of images (images/refinery) and place your new logo-site-bar.png inside
that refinery folder then it will use that instead of pulling from the
RefineryCMS gem.

Folder Structure
name_of_app/public/images/refinery/logo-site-bar.png

Or if you want to modify the view you could do the following:
rake refinery:override view=site_bar

Or if you want all of the shared views do this
rake refinery:override view=shared/*

[Philip Arndt]

Override the site bar as Dennis says and force it to use a local
version. Sorry, this is a hassle with SSL..

I'll see if we can get SSL for refinerycms.com but I don't think it'll happen.

[frank]

That is what I needed. Thanks to both of you for the quick response.
Philip, I think the https issue would be taken care if if Refinery
just included the header logo as part of the gem installation rather
than having it point to the RefineryCMS.com site. Everything else
appears to be working just fine because it is using relative paths to
the items. I don't know the gem code very well, but that seems like
it would be a pretty easy change.