[#5271] CommunityBuilder 2.0.8 (and older) use wrong URLs for component

CommunityBuilder 2.0.8 (and older) use wrong url's for profile picture:

right url: /images/comprofiler/tn62_49d27b2514daf.jpg
wrong url: http://site.ru/images/comprofiler/tn62_49d27b2514daf.jpg

i see wrong url's for profile pictrue in JComments (i'm send message to developer), in Kunena forum (you can see it on joomlapolis.com/forum too), and on JFBConnect component on my site.

Google recommended use urls without http or https!

i'm also see code, what my browseer see on my site:

i mean, this is be a problem for site, who use HTTPs - and browser can say - this is no security, because use http for some elements on site (images, etc)

===========================

i see problem with URLs on this forum too,

i see right code here:
and i see after wrong code here:
all urls need use without http or https!

please shortly time release update with right urls!

=======================

and also Google recommended for external urls use this code (right url):
wrong url:
=======================
Mozilla Firefox and Google Chrome coming this year move to HTTPs for use sites.

Read more:
Mozilla Firefox: Deprecating Non-Secure HTTP
Google Chrome: Marking HTTP As Non-Secure

p.s. i'm use Joomla 2.5.28 and CB 2.0.8

The URLs are not wrong. You have live_site specified in configuration.php is wrong. CB will use this, because that's what Joomla gives CB when we're grabbing live_site. Edit your configuration.php and specify it with // if you want dynamic schema, force it to https if you want https, or the better option is to leave it empty and Joomla will dynamically change it to http or https depending how you're viewing the site.

krileon wrote: The URLs are not wrong. You have live_site specified in configuration.php is wrong. CB will use this, because that's what Joomla gives CB when we're grabbing live_site. Edit your configuration.php and specify it with // if you want dynamic schema, force it to https if you want https, or the better option is to leave it empty and Joomla will dynamically change it to http or https depending how you're viewing the site.

ok, i set in "configuration.php":
and i'm still see this code:
i'm still see in code full path to scripts:
right way, when i can see this:
without "http or https" and without domain name "site.ru"

CommunityBuilder component use no right schema for URLs. Why component Kunena Forum no have this problem with URLs? You can see it on this forum.

Right way:
delete "http or https" and delete "domain name - like site.com" from URL!

JUST READ THIS:
support.Google.com: Secure your site with HTTPS

and you can understand, what i mean.

Use relative URLs for resources that reside on the same secure domain.
For example, use <a href="/about/ourCompany.php"> to refer to a page on your site example.com, rather than <a href="https://example. com/about/ourCompany.php">. Doing so ensures your links and resources always use HTTPS. It also has the side benefit of making local development less error prone because images, pages, and other resources are loaded from your local development environment instead of the production environment.

Use protocol relative URLs for all other domains (e.g. //petstore.example.com/dogs/biscuits.php), or update your site links to link directly to the HTTPS resource.

from support.google.com/webmasters/answer/6073543?hl=en

Relative pathing has nothing to do with HTTPS. As long as live_site is left empty it will adjust the domain as needed depending on how you're viewing the site. This means if you're viewing it as HTTPS you will get HTTPS. I've explained this already in my previous reply. Using relative pathing does not automatically give you HTTPS. Your server needs to have the proper SSL cert and be setup for HTTPS then you need to visit your site with HTTPS.

We do not use relative pathing in our headers, never have. The reason for this is live_site can be adjusted and with relative pathing it would be ignored. This causes a lot of problems for sites that need to point to a different domain for their headers.

A case of where this could be a big issue is using live_site to force HTTPS. With relative pathing this does not work. So you'd need a htaccess domain rewrite or redirect to force people to HTTPS, but what if you want HTTP for some stuff and HTTPS for paths? Now you can't with relative pathing. What if you've multiple domains pointing to the same install, but need the pathing to be linked to your main domain? Now you can't with relative pathing. There are many more use cases for adding live_site directly to the path.

Protocol relative is easily done using live_site as well as I've explained in my previous reply. With your example you'd have live_site set to '//site.ru' if you want to force HTTPS you'd use ' site.ru '. If you want Joomla to decide you'd leave it empty.

This is very bad news.

Many Joomla components with registration - like Kunena, JFBConnect, etc - use normal way for URLs. Only CB not have option for nomarl URLs.

You can add option use "normal URLs", like in other components? (without use "live_site" for URLs)

Because, Google does not agree with you.