CG-FlashyTitles: sIFR 2.0 for WordPress…

Cool plugin, but its not working for me. The admin works correctly, no errors. But on my site, the code blocks appear empty. I wonder if this has anything to do with it? In my source, I have .sIFR-hasFlash h2 { visibility: hidden; }

No that is not the problem, the h2 is hidden and the flashy title displayed in its stead.

Hrm ok…well I tried it on two utterly different WP installs, and same result..blanks where the text should be.

Well, you’ll have to wait for David to respond or contact him as it worked without a hitch on all 4 sites on which I installed it and I have no idea why it doesn’t work for you. Sorry.

Hey Arlo –

Unfortunately, that’s a good one — if you are seeing everything fine in the Admin interface, that generally means the code is working properly, and you have Flash working properly. If it doesn’t replace properly on the main site, I’d generally think it might be CSS related issues, such as an element being positioned/shifted improperly, or trying to force an element to a given size and the Flash doesn’t fit so it doesn’t show up. Something like that.

-d

hey david – i got the same problem. nothing appears instead of a blank white box.
when i switch from my theme to another everything is working fine.
so i thought it may be the css, but even when i switch to a theme using a blank css-file or when i delete mine it won?′t work. strange a€| so i redefined the css of all my h2-tags (h2 is what i want to flashify) to size:0, margin:0 etc. nothing changes.
any ideas?

thanks for time and support.

klick

i got wp 1.5.2

everything is working fine now.

tried diffent things and found the error.

i massively changed the hardcode of wp because i?′m gonna use it as a cms.
i removed ??<?php do_action(‘wp_footer’); ?>?? of the original footer.
returned it in – voila!!

so :))

thanks

Hrm, why would a footer call make a difference? I use get_footer(); …

Arlo, it is just yesterday’s news. Today we call the footer with get_footer() and use wp_footer() which you will find in the footer itself. Many plugins need the wp_footer() hook to do “their job”

wow thanks for the fix everyone.

I had the exact same problem Arlo had. Then I added the <?php do_action('wp_footer'); ?> and it fixed it!

The footer call is used to ‘run’ the javascript changes on the page (I have other plugins in the works that use this hook as well). Any ‘well behaved’ modern theme should have either the do_action(‘wp_footer’) call or just call wp_footer() (which does the do_action internally, thus much safer and streamlined…) somewhere near the very bottom of page generation.

-d

Any clue why on a fresh installation of WP 1.5.2 with Kubrick, the font-size would change according to what I typed in the FlashyTitles backend on the index page, but the font size doesn’t have an affect on the single.php page? It changes the font, so I know it’s affecting it, and the inline style has the enlarged pixel size, but it doesn’t change the size. Why would it be different from the index to the single in size only?

hmmmmm. I would guess this is a sIFR issue, not CG-FlashyTitles in particular.

sIFR has algorithms for sizing the fonts — and they don’t 100% respect the number you specify… In some cases, I believe the algorithm will ‘shrink’ the font if the text wouldn’t otherwise fit.

Otherwise, it could be a CSS issue, if your actual CSS font size is different for the title on index.php versus single.php, the CSS is (again, somehow..) taken into account for the final sizing. If that’s the case, there are specific things in the sIFR docs for overriding the CSS for things being sIFR-replaced, for exactly situations like this — you just need the right CSS, and you can match the single and index headers in size >only< when it’s the sIFR version of the CSS element(s).

-d

Thanks for the heads up – I just decided to design my own theme from scratch so I know exactly what is going on at each step. ??