I can’t repeat the problem myself but I see that the code on your page has
a slightly different format, which might suggest differing versions. You
might just need to update Exhibeo if you’re not already on the latest
version and then install the latest version of the Freeway Action from the
Help menu in Exhibeo.
If you did need to update Exhibeo, you might need to export your gallery
again as well. If not, just install the latest version of the Action and
you shouldn’t need to export again.
Simon
On Sun, Apr 14, 2019 at 12:32 PM madcomposter email@hidden wrote:
Huge thanks, Simon. Adding slideshow_ to the filenames worked - this must
be an Exhibeo bug because that is the program that is attaching the exibid_
prefix to the original filename. The problem remains that every time I
upload, I’ll have to change all of these filenames. Do you know of a
workaround? Your help is greatly appreciated.
I used Exhibeo 2 and the latest action. Republishing just creates another set of slideshow files with the incorrect exibid_ prefix, so as long as there is a set with the full prefix in the Resources folder, the slideshow works. Can’ thank you enough for spotting the issue.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
It’s a bit of a strange one, in that case. Exhibeo prefixes the image names
with the gallery ID and an underscore, “exibid_” by default, and it doesn’t
allow underscores in that ID. The Freeway Action then takes those filenames
directly, so I’m not really sure where the “slideshow_” prefix is coming
from.
I can see that the item in Freeway is called slideshow, so I think it’s
the Action adding that prefix to the code but I’m not sure why or why it’s
not also renaming the files.
You could also try nudging the Exhibeo Action item right, then back again
(just select the item, then press the right arrow key, then left arrow key)
so that Freeway thinks it has changed and republishes it. Sometimes Freeway
can cache Action information and doesn’t republish properly until it thinks
the item itself has changed.
Simon
On Sun, Apr 14, 2019 at 1:50 PM madcomposter email@hidden wrote:
I used Exhibeo 2 and the latest action. Republishing just creates another
set of slideshow files with the incorrect exibid_ prefix, so as long as
there is a set with the full prefix in the Resources folder, the slideshow
works. Can’ thank you enough for spotting the issue.
I did as you suggested but it’s still uploading the slideshow image files with the exibid_ prefix. I’ll figure it out someday … for now it’s working with the manually edited image filenames.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Hi What I mean is once I have set up a secure hosting package, can I then just upload a brand new site to that space in the same way as I have non-secure sites in the past. Or do I need to use the code above anyway?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Make sure your host provider offers the ability for you to use HTTPS for free. Some charge for it, even though Let’s Encrypt is free. But most should offer it free of charge. Once you confirm that, yes, you will still need code in your .htaccess file, and that was mentioned earlier in this thread. Don’t just copy and paste that code though because it was slightly modified for Barry and his hoffkids website. Even if you can’t understand code, you can read through it and spot that site. You would need to change it for your site.
–James W.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
In case it’s of interest, the hoffkids rewrite conditions and rules in James’ earlier code can be made domain agnostic like this:
# Turn RewriteEngine on, only do this once
RewriteEngine On
# If HTTPS & www, redirect to non-www
RewriteCond %{HTTPS} on
RewriteCond %{HTTP_HOST} ^www.(.*)$ [NC]
RewriteRule ^(.*)$ https://%1/$1 [R=301]
# If not HTTPS, whether www or not, redirect to HTTPS non-www
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_HOST} ^(www.)?(.*)$ [NC]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://%2/$1 [R=301]
Simon
freewaytalk mailing list
email@hidden
Update your subscriptions at:
And if you have used any of the Effects Actions (built into Freeway) or any of my “Scripty” Actions, you will need to either install the HTTPS Helper Action on each page that also uses those Actions, or update to the latest version of my Actions (which use HTTPS by default). Otherwise, your site will appear correctly (and securely) in people’s browsers, but none of the JavaScript will work.
Walter
On May 13, 2019, at 6:26 AM, Simon Manning email@hidden wrote:
In case it’s of interest, the hoffkids rewrite conditions and rules in James’ earlier code can be made domain agnostic like this:
# Turn RewriteEngine on, only do this once
> RewriteEngine On
>
> # If HTTPS & www, redirect to non-www
> RewriteCond %{HTTPS} on
> RewriteCond %{HTTP_HOST} ^www.(.*)$ [NC]
> RewriteRule ^(.*)$ https://%1/$1 [R=301]
>
> # If not HTTPS, whether www or not, redirect to HTTPS non-www
> RewriteCond %{HTTPS} !=on
> RewriteCond %{HTTP_HOST} ^(www.)?(.*)$ [NC]
> RewriteCond %{SERVER_PORT} 80
> RewriteRule ^(.*)$ https://%2/$1 [R=301]
I have a site that I am going to move to https and wanted to get insights into Actions that may break. If you look at the site, you’ll see plenty of them - http://www.halfmanhalfmovie.com Any help at all would be appreciated.
I moved a http site to https and here’s what I learned, some of which I believe is mentioned above:
You need to write a 301 permanent redirect for every page that was http and will now be https.
Any pages you no longer want to keep need a 410 redirect.
After you have finished, go to Google Webmastertools and make sure it has:
The HalfManHalfMovie site has a lot of Actions and I wanted to know what people’s experience was with the move on Freeway Pro and how it affected Actions
Without having a list of all the Freeway Actions you currently use, it’s not possible to make specific comments. Indeed, I can only comment on the Actions I currently use in Freeway Pro 7 with my HTTPS websites:
PAGE ACTIONS
Protaculous 2
Site Mapper File Location
Site Mapper Page Options
Timed Redirect
HTTPS CDN Helper
ESS-Use External Style Sheet
Better Meta
Relative Page Layout
ITEM ACTIONS
YouTube
CSS3 Shadow
Layer Positioning
Target Show/Hide Layer
Random Image
Extra Resources
Rollover
CSS3 Corners
Text Rollover
Make Item Into Page Footer
CSS Menus
Graphic Link to PDF
Add Selector
Link to PDF
ScriptyLightbox3
Attention FX
Transition FX
Target Show/Hide Layer
SVG Image
CSS3 Gradient Backgrounds
Carousel 2 Button
Carousel 2 Pane
Carousel 2
I’m sure I’ve missed some, but that’s pretty much what I use without problem, and I of course cannot comment on Actions I don’t use.
Hope this helps.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
The move to HTTPS is done on your server. In my case, I started off with Let’s Encrypt because it’s free. I had to do a lot of manual labor until the day my web host (Superior Host in the USA) made it available as a free plugin, so now HTTPS certificate renewals are automatic. But you will still need to setup your .htaccess file (on your web server) similar to how I did it. Below is an example of code I use right now in my .htaccess file, but I substituted your domain for mine below to make it easy for you to copy/paste. Keep in mind the code below gets rid of the WWW which I personally don’t want because it’s not needed. If you like WWW, just delete that “remove ‘www’” part in the code below. Basically the code below ensures that anyone who tries to visit your HTTP site will be presented with your HTTPS site. If you do not include the code below, then most likely your server would present visitors your HTTP site, even if you have HTTPS properly setup. But at the end of the day, if you have further questions, you really would need to consult with your web host provider. They may require you to do something different. The code below works fine on my web host though.
# STRONG HTACCESS PROTECTION
<FilesMatch "^.*.([Hh][Tt][Aa])">
Order allow,deny
Deny from all
Satisfy all
</FilesMatch>
# Do not allow directory listing in browser
Options -Indexes
# Enable Rewrite feature:
RewriteEngine On
################[ HTTPS, remove "www" ]################
# Ensure the connection is NOT already HTTPS:
RewriteCond %{HTTPS} on
# Rewrite only on this domain:
RewriteCond %{HTTP_HOST} ^www.halfmanhalfmovie.com [NC]
# Redirect users from their original location to the same location but using HTTPS.
# EXAMPLE: http://www.example.com/foo/ redirects to https://www.example.com/foo/
RewriteRule ^(.*)$ https://halfmanhalfmovie.com/$1 [R=301]
##################################################
################[ HTTP -> HTTPS ]################
# Ensure the connection is NOT already HTTPS:
RewriteCond %{HTTPS} !=on
# Rewrite only on this domain:
RewriteCond %{HTTP_HOST} ^(www.)?halfmanhalfmovie.com [NC]
# Restrict HTTP-to-HTTPS rewrites on port 80 (which is used for HTTP):
RewriteCond %{SERVER_PORT} 80
# Redirect users from their original location to the same location but using HTTPS, sans WWW.
# EXAMPLE: http://www.halfmanhalfmovie.com/foo/ redirects to https://halfmanhalfmovie.com/foo/
RewriteRule ^(.*)$ https://halfmanhalfmovie.com/$1 [R=301]
##################################################
freewaytalk mailing list
email@hidden
Update your subscriptions at: