Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
It always outputs whatever Joomla provides as the live_site
Please Log in or Create an account to join the conversation.
We didn't change anything. Most likely you changed a Joomla setting. Whether it's globally forcing HTTPS or setting your live_site URL in configuration.php. Could also be a change in a Joomla release. The code for CB to return live_site has been untouched for probably over a year now as there's no reason to touch it. It's possible something else installed could be modifying JURI::base() (CB does not).We did not have this problem until last week and use this substitution all over the website.
So this has to be with a change that you introduced in latest builds somewhere.
Faster to just do a simple str_replace instead of building an entire URI object for it.Hope it's ok ?
No, it is and always will be whatever Joomla has JURI::base() set to.Cannot you make the live site defaults to http ? and then use a string replace to https ?
It uses whatever scheme you're viewing the site as unless you've configured Joomla to globally force HTTPS or it uses whatever URL you specified as live_site in configuration.php.Because 'm not sure that the JURI::base() always keeps the same protocol...
Please Log in or Create an account to join the conversation.
Faster to just do a simple str_replace instead of building an entire URI object for it.
Most likely you changed a Joomla setting. Whether it's globally forcing HTTPS or setting your live_site URL in configuration.php. Could also be a change in a Joomla release.
Please Log in or Create an account to join the conversation.