It is not always the fault of Drupal

Take a look at following HTML snippet:

<img src="/sites/default/files/LOGO_adview_70_0_4.png" style="display: none;">

If you know a bit of css, you'll know that the image will be hidden in your browser. However, we had no idea where the inline style element came from, it shouldn't be there at all. We are using a simple node list generated by Views and after looking in the templates, custom modules, filters and tinymce settings we decided that this couldn't be a Drupal problem and had to look somewhere else.

In comes Adblock Plus, which is probably the first add-on I always install in my browser on a fresh OS install to block those annoying banners. And in our case, the add-on worked a bit to good. Take a close look at the name of the image file: LOGO_adview_70_0_4.png. The adview in the name is were things went wrong: when editing the same node again, Adblock Plus automatically added the inline style element in the HTML which is saved when updating the node.

It's really amazing how much time you can waste in debugging sessions.


Submitted by Niels Bom on April 5, 2009 - 23:19

Very familiar :)

Debugging for me is splitting a problem up into smaller and smaller parts and eventually coming across the false assumption you made.

Programmers/computer experts have to be very frustation-resistant, I know I struggle with that sometimes :)

Submitted by Grugnog on April 7, 2009 - 17:16

Been bitten by this one too ("works fine in IE, sidebar missing in Firefox") - and the lesson is - ensure you never use "ad" in your image field/cache names :)

Submitted by Brian Vuyk on April 17, 2009 - 22:16

Hehe - a client contacted me a few months ago about a similar issue. He had uploaded a number of images in a series with the word 'advanced' used in the title of all of them. They all got adblocked, and it took a while to figure it out!

It's too bad that as widely used a technology as AdBlock has the potential to restrict how we can even name files on the internet now.

Submitted by mzenner on June 30, 2009 - 11:32

I remember this one ;-) That was a frustrating waste of time. You can have this too when you are editing content ... you save it and everybody then sees the display: none;

Submitted by steeroy on July 20, 2009 - 12:38

@Anonymous: Good idea, that way you can look silly when your client points out compatibility problems that you didn't know about. :)

I've just been fixing this problem on a site that sells advertising space in magazines. That was fun. :)

Submitted by Libros on November 27, 2009 - 16:36

Any chances to have this code for 6.x? I'm done with my new design, but have to wait until I get this issues taken care of. Otherwise, it will be a PR bleeding. Also, how do you deal with URLs that automatically turn into links like I'd like to apply nofollow to all blog interaction. Thanks for sharing!

You are here