Joomla Templates Club 406,261 posts

[adrienne pitman Friend adrienne pitmanJoin date: September 2007Posts: 53Downloads:28Uploads:7 Thanks: 2]

#889428

Instead of picking the social icons from the chosen blue theme image path, the template is loading them from the general image path.
The template is running in development mode, therefore it should be picking LESS variables.
I’ve cleared the cache on my browser and there’s no server side caching of any kind.

templates/ja_nex_t3/less/themes/blue/variables.less shows

@T3ThemeImagePath:      "@{T3BaseImagePath}/themes/blue";

whereas template.less states

background-image: url("@{T3ThemeImagePath}/icon-facebook.png");
background-image: url("@{T3ThemeImagePath}/icon-twitter.png");
background-image: url("@{T3ThemeImagePath}/icon-linkedin.png");

among others.

All invoked files are stored in templates/ja_nex_t3/images/themes/blue and I have confirmed that the images are in deed blue.

Finally, it worked correctly at some point, but not anymore.

What could have gone amiss?

[Adam M Moderator Adam MJoin date: May 2014Posts: 5159Downloads:33Uploads:66 Thanks: 95 Thanked: 1271 times in 1235 posts]

#889863

Hi @adrienne pitman,

Please stay tuned while I’m checking this matter for you and I will reply back shortly.

Best regards,

Adam.

[Adam M Moderator Adam MJoin date: May 2014Posts: 5159Downloads:33Uploads:66 Thanks: 95 Thanked: 1271 times in 1235 posts]

#890123

Hi @adrienne pitman,

Thanks for your patience. As I can see in your site, there’s no problem with those icons, could you please confirm your status ?

---

Attachments:

1. 

[adrienne pitman Friend adrienne pitmanJoin date: September 2007Posts: 53Downloads:28Uploads:7 Thanks: 2]

#890256

The problem is not solved.

Instead of addressing the issue, you’ve merely moved the head-social position back into the header block and then created a new position called head-social-1 in the top header block. This, in my book, is basically cheating.

I want to display the social icons in the head-social position on the top header block and the template picks the image from the wrong location when I do that. Please do not touch the layout, as it has nothing to do with the reported issue.

The real question at hand is why does the template retrieve the social icons from the wrong folder when the head-social position loads in any block other than header. Thank you.

Nuno, Developer at RTVN.

[Adam M Moderator Adam MJoin date: May 2014Posts: 5159Downloads:33Uploads:66 Thanks: 95 Thanked: 1271 times in 1235 posts]

#890974

Hi @adrienne pitman,

Yes, indeed the problem is still remain until you confirmed so. Please note that there’s no reason for us to login to your site, change something, then come back and ask you about the status. Even if we have to do so, it would be for the last case, after we asked you (customer) that we will have to do that. If you take a quick look around the forum, you can see that we only provide you the code to fix the problem or suggest you to fix it, that’s all.

Back to your matter, I checked it at my end and look like the code is fixed to header block only, so you can open file templates/ja_nex_t3/less/themes/blue/template.less and look for this part :

.t3-mainnav {
    .logo-image a {
        background-image: url("@{T3ThemeImagePath}/logo-ltr.png");
    }

    .ja-social .social {

      .ico-facebooks {
        background-image: url("@{T3ThemeImagePath}/icon-facebook.png");
        border: none;
      }

      .ico-twitters {
        background-image: url("@{T3ThemeImagePath}/icon-twitter.png");
      }

      .ico-rss {
        background-image: url("@{T3ThemeImagePath}/icon-rss.png");
      }
    }
}

remove the wrapper class as below :

.logo-image a {
    background-image: url("@{T3ThemeImagePath}/logo-ltr.png");
}

.ja-social .social {

  .ico-facebooks {
    background-image: url("@{T3ThemeImagePath}/icon-facebook.png");
    border: none;
  }

  .ico-twitters {
    background-image: url("@{T3ThemeImagePath}/icon-twitter.png");
  }

  .ico-rss {
    background-image: url("@{T3ThemeImagePath}/icon-rss.png");
  }
}

I also raised a bug report here so our development team can fix it in next version.

[Author]

Posts