One of my clients has a site with more than 100 blog articles containing many images. He has wb 2.10 and php 7.1. Now this customer has requested an SSL certificate. In the WYSIWYG editor, each image shows the full path of the image
<p style = "text-align: center;">
<img alt = "" src = "http://www.example.com/media/luiseren.jpg" width = "80%" /> </ p>
<p> & nbsp; </ p>
My question is whether they should all be edited manually to HTTPS: // ??
Thank you
maybe you can do this in output filter , to replace each http:// with https://
In WebsiteBaker 2.11.0 all absolute Url will be replaced with a placeholder stored in the database
So it's no problem to change Domain.
In my view it were be usefull to have a tool who search all abs url and replace them with the placeholder.
I will be going to think about it
In Moment you have to call all wysiwyg, news sections, load the content and save.
Dietmar
You can use a special header in Apache webservers to force the browser to use https for http sources.
Unfortunatly it is not supported by all browsers yet :-( https://caniuse.com/#feat=upgradeinsecurerequests
Unsupported browsers will just do the same as always.
To use it, put the next line in your .htaccess
Header set Content-Security-Policy "upgrade-insecure-requests;"
Note that when external images are used, the external webserver must also allow https, otherwise the image is not shown (no mixed content warnings though)
Ps.. using a droplet rewriting src="http://" to src="https://" would be a good trick too :-)
pls take a look into the database in the wysiwyg table. do you found there any links in your content with {SYSVAR:AppUrl.MediaDir} (in WB 2.10 + WB 2.11) or {SYSVAR:MEDIA_REL} (in WB 2.8.3 SP6 + SP7)
these are the placeholders (like the answer from Luisehahne)
since WB 2.10.0 there is a included function in the manual upgrade, that replace all WB_URL's from the database mod_wysiwyg-table into these Placeholders (go to addons -> modules -> advanced -> manual upgrade -> choose wysiwyg and run)
with these placeholders inside the database you have to change only the WB_URL in config php
the news module use also this placeholders since WB 2.8.3 SP7, but has not this function to replace old hardcoded URL's in the database
Quote from: johnbroeckaert on January 12, 2018, 07:59:47 PM
My question is whether they should all be edited manually to HTTPS: // ??
When I needed to do this for a website, I exported the site's database. Then opened it in notepad++ and search and replaced all:
src = "http://with
src = "https://... or whatever string works best with your links. Then I saved and imported back into the database.
I think that for the time being I will choose the Skyrider solution. Seems to me the most logical and safe. I understand that there are no more problems in 2.11 but then we will at least have to wait until this is no RC anymore.
Ruud's solution also seems interesting to me, but it is not entirely clear how that should be done with a droplet.
Thank you for your reations (Y)
see my posting..... the URL was replaced automatically in the save-process since WB 2.8.3 SP6 in the wysiwyg module to {SYSVAR:AppUrl.MediaDir} (in WB 2.10 + WB 2.11) or {SYSVAR:MEDIA_REL} (in WB 2.8.3 SP6 + SP7) and replaced back to the WB_URL (by output-filter), when in use (visible in back- or frontend) but only, if this URL in the Picture link is the same like the WB_URL.
Be carefull, if you use also URL's from foreign web adresses in your content, not every page use https, but a (global) search&replace replace everything and then, you have the risk for a dead-link
if you ask me....
Step 1:
start a manuel upgrade of the wysiwyg module
Step 2:
look into the database, table mod_wysiwyg, where do you have a usage from your WB_URL, remember there page_id && section_id and open this page in the wb-backend, save it and go to the next page
Hi Uwe,
Your solution is working just fine. I over looked it at you forlast post but it is simple and quick (Y) (Y)
THANK YOU