Wasn't quite sure what to name this topic. Here is my situation. I am about to install a secure server certificate. I think I have a handle on what I need to do in regards to the forum itself, but I have another issue. Our forum has been around going on 20 yrs. From the beginning we required images to be in a bridged coppermine gallery to share in posts. We do not allow offsite images (THANK GOD THINK PHOTOBUCKET) So, all images posted on our site are on our domain. The file paths are all within our domain. How can I handle this once I enable the SSL so that all these http addresses don't show up as unsecure content to the browser? .htaccess? Some other way. We are talking well over a quarter million photos.
You can do a mysql find and replace on the messages table in the body column to change the link url from http://imagepath to https://imagepath
Always backup your database first
update smf_messages set body = REPLACE(body, "http://imagepath", "https://imagepath");
cant you just enable the image proxy and let it handle it? then you don't need to modify anything.
Quote from: Illori on December 05, 2019, 01:37:48 PM
cant you just enable the image proxy and let it handle it? then you don't need to modify anything.
For the size and scale, fixing it is likely better.
Also more efficient in the long run instead of storing duplicate images and causing proxy.php to be called for the image requests
Yes, the proxy images the way I understand it seems like the forum would be taxed pretty hard, since there are probably photos is almost every topic page.
Is phpmyadmin sufficient to make a call like that for a forum with going on 2 million posts? Or is there a better way?
Should be since the query should just execute. I would put site on maintenance mode just to prevent slowdowns when you run it.
If not command line mysql
Assuming the SSL cert also covers the domain where the gallery resides.
In Coppermine, click "Config", and under general settings, change the URL of your Coppermine gallery folder to from http to https
Thank you! If okay, I'd like to keep this topic open until I get this completed? It might not happen until after the holidays.
I've started this project. I have not addressed the gallery photos as of yet as I am trying to sort out all the other non-secure content first. I am getting this in the firefox console and I cannot find the source of the conflict. any ideas on where to look? It is the last two instances I have on the board index page, on which I started.
Loading mixed (insecure) display content "https://mywebsite/board/uploaded_avatars/avatar_10176_1396655806.jpeg" on a secure pagescript.js:491:2
Loading mixed (insecure) display content "https://mywebsite/board/uploaded_avatars/avatar_10176_1396655806.jpeg" on a secure pagescript.js:491:2
that would be some user's avatar....
if the image proxy is enabled, it should handle that for you.
basically it is all the same issue, you either manually convert the URLs and enable the image proxy or you just enable the image proxy.
I enabled the image proxy with no love. This actually shows up on all pages, not just the index. Maybe something in an old template edit somewhere?
link to where it is happening?
pm sent
Another note, I just went and checked, it only occurs when logged in. If you are not logged in, the page is clear.
then we need the link provided in this topic so anyone that has time can assist you, along with a test log in so we can actually see the issue.
More testing. I logged into the test account and it doesn't do it. However, I changed the test account to an admin account, and then it occurs, but the error points to a different avatar. There should be NO avatars displayed on the page. https://www.forestryforum.com/board/index.php
I would need to provide an admin account.
I can provide an admin account but I got a warning about sending a pm unless asked to specifically to do so.
Okay, it does not have to be an admin account. I went back to the test account and added an avatar to the account. It then started throwing the content error for that login. I deleted the avatar, but the error now remains. Who can I send the test account login to?
Quote from: vbgamer45 on December 05, 2019, 01:33:38 PM
You can do a mysql find and replace on the messages table in the body column to change the link url from http://imagepath to https://imagepath
Always backup your database first
update smf_messages set body = REPLACE(body, "http://imagepath", "https://imagepath");
The problem with this approach is that, I find, many sites are still not http. If you do a change like this, the images will disappear. The image proxy is the only way to deal with these http sites at the moment (assuming your goal is the padlock...).
What would be very handy would be a utility to test for a redirect, and only if found, make that edit.
the OP said that the images are stored on their domain, so it should not be an issue.
Ah, missed that...
Is your avatar url set to https?
Yes. What I can't figure out is why there would be any reason for any avatar to be loading.
Lurkalot is a member of my forum and stopped by for a look and found it for me. It was an http call to a script for the mod autolink words. I disabled the mod and the issue went away.
Now onward to converting my gallery image calls, however I need to wait until after the holidays because we have a contest running and I can't take another chance of disrupting that.
Thank you for the help here and especially to Sir Lurkalot!
ah... yeah, that is frequently the case with mods that call external scripts.
I didn't have a chance to go to your actual site to look, but here's a little pointer:
ON a page that triggers the warning, do "view source of page"
search in the source code, do a search for "http:"
that should tell you what the actual call is and allow you to (possibly) figure out, from looking at the call or the display code around it, what area is causing the problem.
Then you get to have the fun of tracking down the section of code that the mod modified... sometimes that is simple, sometimes not.
most mods that add javascript drop it into index.template.php or add it in their own file, via hooks
Quote from: Kindred on December 13, 2019, 10:01:08 AM
ah... yeah, that is frequently the case with mods that call external scripts.
I didn't have a chance to go to your actual site to look, but here's a little pointer:
ON a page that triggers the warning, do "view source of page"
search in the source code, do a search for "http:"
that should tell you what the actual call is and allow you to (possibly) figure out, from looking at the call or the display code around it, what area is causing the problem.
Then you get to have the fun of tracking down the section of code that the mod modified... sometimes that is simple, sometimes not.
most mods that add javascript drop it into index.template.php or add it in their own file, via hooks
Yep, that's how I found it. Plus error console was warning me about the insecure call for that script, and other helpful info which I passed on to Jeff by PM on his site. ;)