Alvaro Degives-Mas

Try including “autostart=yes” like this example:

[audio:soundfile.mp3|autostart=yes]

You can tinker with other things in a similar way, just take a cue from the given options for the stand-alone version.

Clear your browser cache. Thoroughly.

Then reload and behold the magically appearing favicon.ico 🙂

Maybe you didn’t find any problems, but your WP install (including the theme + plugins in use) doesn’t generate anything closely resembling valid HTML. I just plugged in one post into the W3C validator – check for yourself: no less than 74 errors, and 38 warnings. The warnings you could skip – but those errors you’d better work on, first…

A strictly set Bad Behavior usually does the trick.

However, if for whatever reason it doesn’t work for you, you could try a different route: the WP http:BL plugin, which uses the same http:BL API key and very fast DNS type queries, but doesn’t have all the additional protective script filters that Bad Behavior affords.

Big difference between the two is that the http:BL plugin method just relies on blocking the known bad guys, whereas BB is also and especially able to stop ’em based on their displayed behavior – whether they’ve been spotted elsewhere before, or not.

Nerdy humor aside: in the http:BL plugin, the following line never fails to make me laugh out loud:

if ($blocked) die();        // My favourite line.

Can’t say I disagree.

Last thing that comes to mind – I skipped it because it seemed kinda obvious – is to check that there’s actually a call to the favicon.ico file in the theme.

E.g. check in the HTML source code (of any page on your website, doesn’t matter which one) whether you see something like this:

<link rel="shortcut icon" href="http://www.example.com/wp-content/themes/yourtheme/favicon.ico" type="image/x-icon" />

If you don’t see something like that, edit the theme’s header.php file to include it. A good place would be right underneath the line containing the HTML <title> tag.

The location of the favicon file doesn’t matter; it can be either in the webserver root folder (i.e. directly in the public_html or www folder) or just as in that example above, where I linked to the theme’s folder, as that’s very often where a favicon file is placed by the theme author (then again, it’d be strange if the theme’s author didn’t also include a proper favicon link in the theme’s header file but hey, could be an oversight).

The ‘Default’ theme doesn’t have a favicon though, so if you use that theme, you’ll have to upload the favicon file, and also include that line in header.php pointing to where you put that favicon file (the webserver root is usually the best place).

It helps to check that the file name is favicon.ico (and not ‘fav.ico’ or something else) and that it’s saved in the appropriate .ico format and size (e.g. 16×16, 32×32, 64×64 – don’t go overboard with bigger ones; typically the 16×16 size is used in address bars, and there’s a dramatic difference in filesize between ’em, too)

Finally, to be sure: put the favicon.ico file both in the webserver root folder (usually named public_html or www) and in the theme folder.

And once you’re done, clear your browser cache thoroughly – especially the favicon.ico files are persistent critters.

You’re hosted on a shared server. So, contact the webhosting company that hosts the site and ask them for help.

If you don’t have that information, and only if you registered the domain separately from your webhosting (always recommendable – here’s one very good example why!) the next step up the drastic but temporary countermeasures scale is going to the registrar (the company where you registered the domain loulisa.net for your site, e.g. GoDaddy or Network Solutions) and ask them to remove the DNS settings. That at least will make your site completely inaccessible, which stops your site being poisoned in search engine rankings.

Meanwhile, continue trying to get in touch with the webmaster, and for next year’s summer vacation, make sure you have contingency plans in place.

Once again, here’s a very good example of why that is a good idea, instead of relying on “other people taking care of it.”

Good luck!