Annoying, REALLY annoying.
Everytime we enter a tracker url we have to delete the http:// to replace it with https://
People might think this is NOT a bug, I think it is. This is 2020, letsencrypt have been fighting to SSLize the Internet for years and still the default is http://.
100% of all the trackers we create are HTTPS.
Everytime we enter a tracker url we have to delete the http:// to replace it with https://
When creating a tracker the url field SHOULD either be empty or pre-filled with "https://"
When creating a tracker the url field is pre-filled with "http://"
It's low of course, but still annoying and you should be at the forefront to do the right thing.
Can you please post the exact values of your site_url and host_name values from config.php? Also, please check if they are redefined in config_override.php or not.
Not changed in config_override.php, below is a copy&paste
'site_url' => 'https://piquet.barrett.com.au/BCG-SugarCRM',
'host_name' => 'piquet.barrett.com.au',
You will not get access to it, I only allow AUS/NZ but allow the rest of the world for query string "entryPoint=acceptDecline".
Also, one day I will change the reference to Sugar ;-)
I think site:url should begin with https://
That makes no sense.
My site_url starts with https://, has always been that way ...
Ah sorry, it's just that I didn't notice that GitHub linkified your text, and the https isn't showing.
Have you tried changing it here?
https://github.com/salesagility/SuiteCRM/blob/master/modules/CampaignTrackers/vardefs.php#L70
I'm not sure if that's enough. Remember to QR&R, hard-refresh etc
That gets overwritten on update ... all files in the dir have the same (very recent) time.
So not sure but I suppose you need to change the default, perhaps?
Or make it a config_override.php entry?
What I am saying is that, if this simple change fixes the problem for you, we probably should just go ahead and make the PR and put into core. I think in 2021 https is more of a default than http.
That's ok for me, but please make https the default.
Still a problem in Version 7.11.18.
Still a problem in Version 7.11.18.
Well then it needs a PR :-) ... Is the change in the code mentioned above working well for you?