manstraw

I just noticed this thread which talks about the same error. http://wordpress.org/support/topic/70019?replies=5 He claims it’s the pmetrics plugin. He removed it from his footer, and now it’s fine.

I looked at your code again, and I see you have pmetrics installed. So that might be your problem. I have no idea what pmetrics is. Is there an update perhaps?

I also notice you have the performancing metrics, and you have it twice. You should fix that. You should only have it once on your page.

font-family: arial, verdana, ms sans serif;
font-size: 12pt;

Where in the style sheet? Well, I’d need to see the style sheet and site to tell you that.

Here, I googled a helpful looking tutorial on it. http://www.sitepoint.com/print/style-web-forms-css

edit: I just noticed that example uses tables, which are blecky! let’s just ignore that aspect of it.! 🙂

exploring the directory can be separately disabled.

the real risk comes from someone else who has access to your server. perhaps another web account on the same server. or a poorly written php script that allows a program to be uploaded that pretends to be a picture. let’s say you let people upload pics without any checks, and a hacker uses it to upload a program. If you have execute access to the directory, he might be able to use that space to install *and run* his program.

now, these days, a chmod of 777 is not as risky as it sounds, at least not on a server wide level. it’s just one layer of security. each virtual account is usually chrooted (actually, i don’t think cpanel accounts do that, unless that’s changed from the last time I used cpanel). you are running your own sort of virtual server environment. in other words, someone who hacks another persons account generally won’t be able to even see your account space.

to hack into your space, it really needs insecurely written scripts in order to do it. so one thing to be concerned about is any plugin that uploads something. it simply must check the data it’s plomping into your account space is actually what it’s supposed to be.

the topic is too large to discuss here, and i’m not an expert. I’ve had encounters with some of these issues though. php, mysql etc. can have their own security flaws. be sure your webhost is on top of that end. for your end, be careful what you install into wordpress, and keep wordpress up to date. if a hole is discovered plug it. worry about these things more than a directory that has permission of 777. but still, change it to 755 if you can.

That orange icon shows up in firefox in the location bar. I take it you mean you want one in the sidebar of your blog? Or somewhere else on the actual page? Is that what you’re after?

Frankly, that sounds like the visitor is infected with spyware other such ‘junk’. But if they tell you it only happens on your site, we’ll look deeper.

It’s possible someone put some javascript in a tagboard comment, or at some other place on your site. It could cause an onclick event when they click on a link, which could result in a popup. That’s just one example of how that could be done. I don’t think this is a wordpress specific issue, but it could be the result of a plugin.

Ask them to turn off javascript and see if it still happens. That’s where I would start. And I’d (relucantly) fire up internet explorer and see if I could get to happen to me. And when I say I and me, I mean you, since I really don’t want touch IE. 🙂

He means visit that website, and scroll down the page until you see the KIN plugin information.

from the website:

KIN is just a simple notepad for jotting down notes and ideas. Quick, useful and easy to use.

edit: oops, he beat me to it!

I think you really need to have the javascript as an external file, and then just insert the call to it through your hook. Is there a reason why that might not work for you?

I thought it was self explanatory. You need to have correct information in the file wp-config.php. It needs to know the user/pass to the mysql database. And it needs to know host name where the mysql database is (usually localhost, but not always). Contact the webhost for what that information needs to be, and edit the wp-config.php file accordingly.

Or it’s possible the mysql server is down. That’s another question for your webhost.