ProBloggerss.com

Link To Full Story: DomainGang

WordPress 3.2 was just released; in the process of updating, one plugin broke our database and left us for about 5 minutes without access to the WordPress administrative section. How did we fix it? Simple. If a plugin breaks your database, you need to remove it from the list of active plugins in the database. [...]

Link To Full Story: morganlinton.com

First let me be clear with my goals for my Facebook Fan Page. The goal of a Fan Page is to drive more traffic to your domain and engage and interact with a targeted audience online. There is no reason to think that at fan page would ever replace a domain, it can’t, won’t, and really isn’t intended to so get that out of your mind. The fact of the matter is that there are tons of people who love kayaking on Facebook and while some of them find my site through other means many of them wouldn’t know my site existed without Facebook.

Link To Full Story: ottopress.com

Shared by JohnH
Go Otto!

As I’ve gotten involved with helping the WordPress.org theme review team, I’ve seen some strange things. One of the stranger ones was a theme virus that actually propagated from one theme to all others in a WordPress installation. That one was awfully clever, but it ultimately didn’t really do anything but propagate and generally be a pain in the ass.

However, today, @chip_bennett discovered that one of his themes had been copied and was being redistributed by a site called top-themes.com.

It had malware inserted into it that is of a much more malicious and spammy nature. Further investigation reveals that ALL of the themes on that site contain basically the same code. This code is not actually “viral”, but it’s definitely malware and it’s worth investigating to see some of the ways people try to hide their spam.

So today, I’m going to dissect it and serve it up on a platter for everybody to see.

Infection Point

We’ll start with the most obvious starting point, and that is in the functions.php file. At the very end of the functions.php file, we find a call to “get_custom_headers();”. An innocuous enough sounding name, so we go find that function. Here’s the first part of the function:

Link To Full Story: howardneu.com

Under Federal law, web sites are generally not liable for comments posted by others on the sites. However, the courts have held that they can be forced to reveal the poster's identity if the post includes false facts. Calling someone names like "jerk" or MORON", is safe from a lawsuit because it is stating an opinion, which is not actionable. But if the comments are factually false or malicious like he is a thief or he wrongfully put taxpayer's money in his pocket, these words are defamatory and are the basis of a libel or slander suit.

Link To Full Story: www.mattbartus.com

On February 17, 2010, the Word of Mouth Marketing Association released a guide which may begin to set some industry standards for how to provide appropriate disclosures (in not too many characters). Examples include:

• I am an employee [or representative] of company name.
• I received product or sample from company name to review.
• I was paid by company.
• For microblogs such as Twitter, include the hashtags #spon, #paid, or #samp.

The social media world continues to evolve very quickly and surely corporate compliance with the new FTC endorsement guidelines will evolve as well.