[SOLVED] HTTPS: error

yes it is the profile view. i just mean that they can access the profile from it.

Please PM backend super administrator login credentials and will take a look.

i sent you the details, thank you so much for helping! i have absolutely no idea how this has happened!
if you like you can check the configuration.php file to be sure the url there is ok also. there is a component in the admin that allows you to access the ftp files named osefileman i believe in the components list

Have reviewed your install and all your CBSubs redirects had live site in them. All internal redirects should always begin with index.php. The next issue is all your redirects were SEFed. All redirects should always be non-SEF. I've fixed your CB and CBSubs redirects to begin with index.php and be non-SEF.

The next issue with HTTPS not working is due to your sites Caching. This is one of the pitfalls of using caching. It always serves out of date data and it was serving and out of date login page response. I've purged cache and it's working fine now, but you may want to consider disabling cache entirely. With caching everytime you make a backend change you need to remember to purge it or you change may not be reflected on frontend.

The final issue is that your redirects are not sending you to the HTTPS version of your site. This is due to $live_site being configured in configuration.php. I've edited it using your OSE Fileman extension, purged cache, and confirmed everything is working fine now. Please also confirm is working.

i can see that it seems to be working. let me run this by you to see if this was the problem.....earlier i edited the configuration.php file to remove the url from the $live_site, then i had to change it back just to be sure i didnt make any changes. i have never had any issues like this in the past. so could the issue have been that i needed to purge the cache the entire time which would have cleared out everything & allowed the change back to its origination of the configuration.php file?

also please check your pm for a message im sending

$live_site should always be blank unless you absolutely need it and understand its usage. It forces the live_site Joomla configuration variable to that URL. That URL is the exact URL CB will use for imports, redirects, etc.. so if it's set with HTTP then CBs usage of it will always be HTTP. Leaving it blank allows Joomla to dynamically construct it as needed.

so could the issue have been that i needed to purge the cache the entire time which would have cleared out everything

Everytime you make a parameter change in backend you need to purge your cache so the parameter can take affect. The reason for this is if the page is already cached it doesn't care about your parameter, because it's not re-parsing the page and is instead pulling a cache file which is a storage of the pages previous state. This basically causes out of date data so a purge must be done on each parameter change.