The block containing the linkage renders properly and functions nicely. The trouble is that sometimes the image icons don't show up in the block. It's intermittent so it's hard to pin down what might be causing this. Usually, I reload the pages and then they are fine until the problem pops up on another page. I have a site under development where you can see the problem if you are patient to refresh the pages ofen enough. I wish I could give you better details on how to reproduce the issue, but I'm afraid that even I have that issue.

Thanks so much for the help!

Comments

q0rban’s picture

Status: Active » Postponed (maintainer needs more info)

Hi Sean!

Yeah, I woudn't mind looking at the site. Do you have images working fine in other areas of the site (imagefield, imagecache)? You can message me the url if you don't want it public.

Sorry you're having problems!

q0rban’s picture

Category: bug » support
Status: Postponed (maintainer needs more info) » Fixed

So, in looking at your dev site, it appears that the follow.css file is not being loaded on your subpages. Even when you navigate back to the homepage, you'll see a 'home' as the first argument in the path so it's acting as a subpage and the css is not loading. Once you remove the 'home' from the path, then the css loads again. Are you doing anything in your template.php file that's using drupal_add_css or something? I don't believe this is an issue with follow, though. I think it's an issue with your theme.

If you can't track it down, you could always just copy the contents of follow.css into your theme's css file. Not the greatest fix, but it will be quick and easy.

seaneffel’s picture

Status: Fixed » Closed (fixed)

I wasn't doing anything unusual in template.php, in fact the file is blank. I think what was happening was bad theme templating on my behalf where users when logged in were rendering conflicting divs that then superseded the divs called by follow.css.

I took the easy route and copied the follow.css file to my main theme css file and, so far, it seems to have done the trick. I figure this is OK since it is an issue in my custom theme to begin with.

Thanks for the help.