Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-08-09 Thread Adam Cox
Hi Joel, I see this is still an issue, and we haven't heard anything more on the open layers repo. I think your best option would be to use a later release of open layers 3. You can test this out by looking in base.htm and replacing the references to local ol.js and ol.css files with references to

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-11 Thread Joel Aldor
Hi Vincent/Adam, Thanks for the fixes. I lodged an issue on OpenLayers Github and they mentioned that OpenLayers 3.1.1 on Arches v3 does not support HTTPS conversion yet. However they provided a code that may be put on base-layers.js. How do

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-11 Thread Vincent Meijer
Hey Joel, Instead of changing all URLs to https://, you can also use // E.g. change href="http: //cdnjs.cloudflare.com/ajax/libs/select2/3.5.0/select2-bootstrap.min.css to href=" //cdnjs.cloudflare.com/ajax/libs/select2/3.5.0/select2-bootstrap.min.css" This causes the web server to decide which

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Adam Cox
Just looking around a bit, it seems like it's an issue that people have had with Bing and open layers in the past. As it seems to be outstanding, reporting it would be a good thing to do if that hasn't happened already. On Fri, Jul 7, 2017 at 6:21 PM, Joel Aldor wrote: > I need all our pages to

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Joel Aldor
I need all our pages to load on HTTPS. Is it better to report this to Bing Maps or OpenLayers so they can fix it? On Saturday, July 8, 2017 at 1:53:19 AM UTC+8, Adam Cox wrote: > > Here's a related stack exchange question. > https://gis.stackexchange.com/questions/139666/changing-bing-maps-attri

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Adam Cox
Here's a related stack exchange question. https://gis.stackexchange.com/questions/139666/changing-bing-maps-attribution It may be better to just live with the http load error than try to interpret Bing's terms of use. Up to you. On Fri, Jul 7, 2017 at 12:49 PM, Adam Cox wrote: > I think that ima

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Adam Cox
I think that image comes with the attribution property that Open Layers adds to their Bing layers by default. In media/js/map/base-layers.js you'll see that the Bing layers are created without any attribution property. I think to solve this issue (though it may be worth googling it as well) you wil

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Joel Aldor
Where can I find the offending file from here? I seem to can't trace it. This is the only one left that needs to be fixed, I believe. On Friday, July 7, 20

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Joel Aldor
Nevermind, I found them already. :) Yeah it's in the base.htm file, and I just added 's' on the "http://..."; links. Most of the pages are now fully served on HTTPS, save for a few more, so I'm in the process of editing them too. Thanks for the help, Adam! Joel On Friday, July 7, 2017 at 11:0

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Joel Aldor
Tried to check on Google Developer Tools Console and I'm at loss with where to find the files I need to modify. Anyone who knows which files need to be edited? On Friday, July 7, 2017 at 9:09:14 PM UTC+8, Adam Cox wrote: > > Hi Joel, > > We recently did this at Legion GIS for our test Arches 4

Re: [Arches] Re: Arches on apache2 cannot run on HTTPS using LetsEncrypt

2017-07-07 Thread Adam Cox
Hi Joel, We recently did this at Legion GIS for our test Arches 4 installation https://arches4.legiongis.com and had a similar issue. The problem you're encountering is that once the SSL is in place, it will not allow you to load css or js libraries from non-https locations. I believe that pretty