Just when you think you’ve got technology under control, some small gnat comes along to bit you. I had just added and styled the nice registration form for people interested in Foliopress WYSIWYG and SEO Images to the previous post :
and then I began seeing double. That is to say two me:
dd add signature plugin error
That nice headshot with the articles is created by Alastair Dagon Design’s Add Signature Plugin. What’s seems to be causing the doublevision is the inclusion of a form inside a post. I tried moving the form into a Sniplet (where it should have been in the first place, quite frankly and reuseable). I’ve cured a few WordPress malfunctions by pulling code outside a post and into a Sniplet – but that was pre-Foliopress WYSIWYG. Most of the WordPress Editors damage or modify code so a Sniplet can stop them from getting a chance to break code. But this time the Sniplet trick didn’t work.
I couldn’t find the issue in the plugin itself:
wp-content/plugins/dd-add-sig.php
Nor does the issue seem to be in our template index.php file, although there seems to be room for such an issue there.
But unique to our install is that the manual override for the signature (include an html comment anywhere in your post and your signature should appear there and nowhere else) isn’t working either.
I don’t know where to chase down the content loop itself – and presumably neither John nor Jérémie would have altered the content loop.
Somebody else will have to fix this. If anyone has any ideas, please let me know. My best advice: if you can keep computers out of your life, do. Nothing more reliable and crash resistant than pen and paper. Tolstoy, Stendhal and Lermontov all wrote with pen and ink. These gentlemen didn’t even have typewriters.
Alec Kinnear
Alec has been helping businesses succeed online since 2000. Alec is an SEM expert with a background in advertising, as a former Head of Television for Grey Moscow and Senior Television Producer for Bates, Saatchi and Saatchi Russia.
I’ve cured the above – visually at least – in Firefox and Safari. But I’m not sure that the cure is any better than the illness. I’m a much better CSS designer than PHP coder so I’ve attacked the problem for the other side.
What I’ve done is add a sibling selector to my code:
form + h5 {display: none;}This gets rid of the signature pronto. I could even add a class to the h5 (which I’ll do now: h5.byline) to make sure that I don’t accidentally make an important image disappear.
Of course this isn’t going to help the Internet Explorer visitors. But the IE visitors probably don’t care all that much about small design issues anyway. The Firefox/Safari Design crowd – you know who you are – won’t even see an issue.