solved Profile Domains - Profile Skin - Bug

serveion
@serveion
8 years ago
223 posts
Hello

well i have been playing around with the profile domain everything works with the default skin.
but if i go to customize and choose a different solo skin the page don't show the new selected skin.
this is with custom domain


you can see the page at
tarikmainbrain.com
with solo pro selected

I left the skin enable for you guys to see the problem.
updated by @serveion: 05/05/17 04:11:22AM
michael
@michael
8 years ago
7,772 posts
is the URL correct? not seeing anything there.

Thoughts: Solo is a skin that works a bit different, does it work with other skins?

Which module are you using to get a different skin on the profile? jrProfileTweaks or jrAdminSkin?
serveion
@serveion
8 years ago
223 posts
sorry i just corrected tarikmainbrain.com JRProfiletweaks
updated by @serveion: 01/30/17 04:24:42PM
serveion
@serveion
8 years ago
223 posts
the default skin works fine. its only when i use jrProfiletweaks skin the page dont work
michael
@michael
8 years ago
7,772 posts
ok, tested this out, but not able to reproduce.

I have the Profile Domains set to allow a profile on my site to use its own profile domain. So my main site is http://yoursite.com. then a profile on that http://yoursite.com/michael has been mapped to its own domain, michael.com

on michael.com are all the things of that profile
michael.com/uploaded_audio
michael.com/blog
......

the available skin options in the ProfileTweaks module for that profile are a choice of:
* Lucid skin
* Sage skin
* Solo Skin
* Elastic2 (default)


I am able to change between any of the skins and have the whole skin change for michael.com.

Please correct me if Im not understanding something.
michael
@michael
8 years ago
7,772 posts
can see something happening on your site. believe its related to https: not sure what it is though. will keep looking.
serveion
@serveion
8 years ago
223 posts
hello @michael

you are correct that the same thing am doing. but for some reason mine don't work.
check the attachment of the skin i have enable.
updated by @serveion: 01/30/17 05:31:28PM
serveion
@serveion
8 years ago
223 posts
hello @michael

I try

Elastic default + profile skin = Audio Pro : OK
Elastic default + profile skin = Elastic : OK
Elastic default + profile skin = Solo Pro : No Good
Elastic default + profile skin = Solo Artist : No Good
serveion
@serveion
8 years ago
223 posts
Hello @michael
am using cloudflare.com for my domains. and it forces https:// let me make it http://

I try them both http:// & https:// same result.
updated by @serveion: 01/30/17 05:54:59PM
michael
@michael
8 years ago
7,772 posts
not totally sure what cloudflare.com is or how it relates to jamroom, what I think it is is some sort of global caching system that stores a cache of your site at multiple locations around the globe so people in those areas get your site loading faster.

makes me think there might be a stored cache of solo Pro and Solo Artist from before you turned off the https://

you could also try activating the https:// version for the profile domain from the MODIFY button:
"enable SSL"
for the domain from https://wowmusic.fm/customdomain/browse
serveion
@serveion
8 years ago
223 posts
Hello @michael

When I get home i will remove caches from cloudflare and see if i can check all caches, on the server and website if that is causing the problem i will update later.
brian
@brian
8 years ago
10,148 posts
I use profile tweaks + custom domains and I am not aware of any issues - the skin shown isn't changed by or dependent on custom domains.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
serveion
@serveion
8 years ago
223 posts
Hello

@brian i check and you right there is no issues with the custom domain, I was changing the skin using custom domain. So I though that was the problem. But is not.

@michael you are right cloudflare make cache of the websites for 4 hours around the world and the problem was added the domain to cloudflare and the cache was made, then soon i update the skin on jamroom to a new release and rebase all the skins, i belive that was the reason why Jr profiletweak didn't work. What i did was delete all cache from cloudflare so it can cache the new skin information everything is working correctly now.
michael
@michael
8 years ago
7,772 posts
:) Fantastic @serveion. Thanks for letting everyone know the fix if they run into this situation. Great to hear its working now.
updated by @michael: 01/31/17 12:35:11PM

Tags