1

You can see it here.

The site looks fine when I remove Blueprint. I've tried adding Bootstrap and the same issue occurs.

I've been following this (excellent) tutorial.

BoltClock
  • 700,868
  • 160
  • 1,392
  • 1,356
d_ethier
  • 3,873
  • 24
  • 31

2 Answers2

2

According to chrome, this is the code causing this:

http://blazing-fog-1717.herokuapp.com/assets/application-fcc74be8bd91511db934f033390efd28.css

a:link::after, a:visited::after {
  content: " (" attr(href) ")";
  [...]

I have no idea why blueprint might be doing this, but you can just edit blueprint.css and remove the following rule:

content: " (" attr(href) ")";

Setting the media attribute of your links to print (media="print") can fix the problem as well.

If you don't like either of these solution, you should be able to over-write the css by adding the following CSS code AFTER the inclusion blueprint:

a:link:after, a:visited:after {
  font-size:90%;
  content: none;
}

I'm not sure about that last part, but you could try it out.

Chris
  • 121
  • 2
  • 1
    I had them separately defined but the pre-compile step was putting them both in the application.css file. I guess it was being done incorrectly. I pre-compiled bootstrap and everything looks fine now. Thanks for your help. – d_ethier Feb 13 '12 at 01:15
1

I had the same problem, try to add the following line to config/environments/production.rb 

config.assets.precompile += [ "blueprint/*.css" ]

This step is described in section 5.4.3 Deploying to production with Blueprint ;)

Aldo 'xoen' Giambelluca
  • 12,075
  • 7
  • 33
  • 39
  • 1
    Good suggestion, but I already had that line in the file. I even tried to pre-compile prior to pushing to Heroku. The display looks the same even with dev/test. I pre-compiled bootstrap and everything looks fine now. Thanks for your help. – d_ethier Feb 13 '12 at 01:13