In accordance with the new rules on the internet I took the free offer from my host (Bluehost) to change my sites to https. However, the consequence is that different calamities appear here and there.
Sequence Timer, Target Show/hide Layer, Scripty Lightbox3, Spawn New Window, etc. either have stopped working completely or behaving somewhat odd.
FYI, I have .htaccess files on the sites, mainly to redirect www. Now I see that the host has added a lot of other stuff, too. If that has any significance.
Before I post an example are there some general guidelines I initially can pursue?
Any suggestions out there to get me in the right direction?
Jon
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Apply the HTTPS CDN Helper - ActionsForge to the page that has ScriptyLightbox3. I’m not certain that this Action will fix any of the older Actions like Sequence Timer, but it may help.
Walter
On Jul 16, 2018, at 5:55 AM, Jon H email@hidden wrote:
In accordance with the new rules on the internet I took the free offer from my host (Bluehost) to change my sites to https. However, the consequence is that different calamities appear here and there.
Sequence Timer, Target Show/hide Layer, Scripty Lightbox3, Spawn New Window, etc. either have stopped working completely or behaving somewhat odd.
FYI, I have .htaccess files on the sites, mainly to redirect www. Now I see that the host has added a lot of other stuff, too. If that has any significance.
Before I post an example are there some general guidelines I initially can pursue?
Any suggestions out there to get me in the right direction?
Your action fixed all the problems, Walter. Thank you very much.
It would be interesting to know the basics of how it works. I mean, I apply this action and everything is back on track, just like that. Very good, but I don’t know why and what is happening underneath. Care to elaborate? Just a little?
Jon
freewaytalk mailing list
email@hidden
Update your subscriptions at:
This Action rewrites all of the requests to the Google Ajax CDN (content delivery network) from http:// protocol to https:// (secure) protocol. That’s all it does. When you load a secure page, by design, any links within that page which are not to a secure protocol URL will not load. That means that if you had two images (or in this case, JavaScripts) linked to that page, the secure one would appear in the page, and the non-secure one would be missing.
Browsers do this so that a secure page (which shows the lock icon, and is trusted) cannot include non-verified contents. Either it is all secure, or none of it is.
Walter
On Jul 17, 2018, at 10:31 AM, Jon H email@hidden wrote:
Your action fixed all the problems, Walter. Thank you very much.
It would be interesting to know the basics of how it works. I mean, I apply this action and everything is back on track, just like that. Very good, but I don’t know why and what is happening underneath. Care to elaborate? Just a little?
Hi all and Walter… I also have been having problems with a site that is now https… but once I found this HTTPS CDN helper action one of the pages that had a table started working fine, but the page with responsive videos does not load the videos… even though in the action the vimeo link is set to https, and upon checking the Responsive Video action code there is a line of code that states:
//is the site using a https connection
//if so replace the http: for https:
I applied the CDN action on this video page but it does fix the loading issue… anyone know a fix? thanks all
freewaytalk mailing list
email@hidden
Update your subscriptions at:
To add more info to this, when I view the source code on site page and use inspect element to change the video from http to https the video appears… its strange because each applied vimeo video is https but the action does not carry this thru
freewaytalk mailing list
email@hidden
Update your subscriptions at:
I would not expect the HTTPS CDN Helper to help out in this case. All it does is fix the CDN links to the Prototype and Scriptaculous libraries, as well as anything hosted by the FreewayPro CDN.
The problem with the Responsive Video Action is that it presumes that all the services are hosted at http:// URLs. Lines 8, 9, and 10 of that Action are the culprits. If you open the Action in a text editor, you could change these to https and the site should work fine.
This Action is written by Tim Plumb, and I’ve written him a note off-list to see if he can update the Action. You can easily update the Action yourself with a programmer’s text editor (BBEdit, TextMate, Sublime Text, etc.) if you want to give that a try.
Walter
On Oct 9, 2018, at 9:20 PM, Carla email@hidden wrote:
Hi all and Walter… I also have been having problems with a site that is now https… but once I found this HTTPS CDN helper action one of the pages that had a table started working fine, but the page with responsive videos does not load the videos… even though in the action the vimeo link is set to https, and upon checking the Responsive Video action code there is a line of code that states:
//is the site using a https connection
//if so replace the http: for https:
I applied the CDN action on this video page but it does fix the loading issue… anyone know a fix? thanks all
Hang on, I read further into the Action, and there is a checkbox that should allow you to use HTTPS URLs in the interface. So forget what I said (as long as you have the latest version 1.6.1) and undo any changes to the code, and just check the “Secure connection (https)?” checkbox in the Action interface.
Walter
On Oct 9, 2018, at 11:15 PM, Carla email@hidden wrote:
Hi Walter
I changed the 8,9 10 links to https and the videos boxes show up now but a Big OOPS the embed code for this video is not valid…
hmm
Also, you should not put the entire URL in the interface, only the video id code itself.
Walter
On Oct 9, 2018, at 11:19 PM, Walter Lee Davis email@hidden wrote:
Hang on, I read further into the Action, and there is a checkbox that should allow you to use HTTPS URLs in the interface. So forget what I said (as long as you have the latest version 1.6.1) and undo any changes to the code, and just check the “Secure connection (https)?” checkbox in the Action interface.
Walter
On Oct 9, 2018, at 11:15 PM, Carla email@hidden wrote:
Hi Walter
I changed the 8,9 10 links to https and the videos boxes show up now but a Big OOPS the embed code for this video is not valid…
hmm
Sorry, I was reading the Action code, not looking at an example. The Secure Connection control is a picker (Yes/No) rather than a checkbox. Try these steps:
Insert / Action Item / Responsive Video.
Drag out the dimensions of the resulting 100px square item to something video-shaped.
In the Actions palette, leave the video code at the default. Set the Secure Connection picker to yes.
You should see a video of a 2012 Audi R8 in your page.
Now try this again:
In the Actions palette, replace the default video code with 154672714.
Set the provider to Vimeo.
Leave everything else the same.
You should see a video of a monk making a sand mandala.
Walter
On Oct 9, 2018, at 11:24 PM, Carla email@hidden wrote:
what does this mean?
just check the “Secure connection (https)?” checkbox in the Action interface.
I do have the 1.6.1
so now change all the videos back to just the video # and not the full any longer?
Walter just as an aside ,… one can leave the full url for the video for it to work fine… I had not seen the new Secure connection picker as it was a new fix… so as you said just check that to YES
freewaytalk mailing list
email@hidden
Update your subscriptions at: