Skip to main content


Showing posts from June 26, 2011

WordPress for webOS: A New Way to Blog

WordPress for webOS: A New Way to Blog    阅读原文» It’s a new way to blog, on a new type of platform. Today we’re excited to share a glimpse of the future for all the WordPress mobile apps. Drumroll please! I give you WordPress for webOS , available as a download for the HP TouchPad with support for more webOS 3.0 devices coming in the future. Here’s the run-down: It’s the first official WordPress app to have a full featured WYSIWYG ( what’s this? ) post editor. The app has been translated to all languages available on the TouchPad. It uses a “Sliding Panels” interface, which takes full advantage of the larger screen of the TouchPad and makes for fast and easy blog management on the go. Check out the video below to learn more! Of course the app also features everything else you’ve come to expect from a WordPress app. You can manage posts and pages, as well as add new ones. Moderation is built right in, and you can even reply directly to comments. If a comment comes in and you’re worki

Multiple Author Blogs vs Single Author Blogs

Multiple Author Blogs vs Single Author Blogs    阅读原文» When we were all amateurs, we started everything from scratch. However as time goes by, things relatively changed and the blogging community began to expand into a global thing and it’s even called as blogosphere or the WordPress community. The option to continue posting at that constant frequency to keep loyal readers and followers to date and to bring the “In” thing is relatively impossible for WPWebHost therefore to achieve that goals, we decided to have multiple authors to do that. However the biggest argument today that I would like to discuss here is the pros and cons of a multiple author blog and also the pros and cons of a single author blog. Single Author Blogs: Expectation from readers If you read a blog daily, you naturally get the flow of the blogger’s style and his general ideas as you know what you are about to get from the blogger and the topics that are usually covered. You also know the quality of the writings a

WordPress 3.1.4 (and 3.2 Release Candidate 3)

WordPress 3.1.4 (and 3.2 Release Candidate 3)    阅读原文» WordPress 3.1.4 is available now and is a maintenance and security update for all previous versions. This release fixes an issue that could allow a malicious Editor-level user to gain further access to the site. Thanks K. Gudinavicius of SEC Consult for bringing this to our attention. Version 3.1.4 also incorporates several other security fixes and hardening measures thanks to the work of WordPress developers Alexander Concha and Jon Cave of our security team. Consult the change log for more details. Download WordPress 3.1.4 or update immediately from the Dashboard → Updates menu in your site’s admin area. WordPress 3.2 Release Candidate 3 This release was about all that stood in the way of a final release of WordPress 3.2. So we’re also announcing the third release candidate for 3.2, which contains all of the fixes in 3.1.4; few minor RTL, JavaScript, and user interface fixes; and ensures graceful failures if 3.2 is run on P

Block WordPress spam comment with .htaccess

Block WordPress spam comment with .htaccess    阅读原文» If you have self hosted WordPress and always got lots of spam comments and getting frustrated by trashing them each day, you may actually block or reduce them through your .htaccess Apache configuration file. Most spammer attack your comment box not through the blog post but they actually access through your wp-comments-post.php file. Here is how you can stop them from attacking your blog with spam and at the same time stopping the unnecessary server load. You can find the .htaccess file in your root of WordPress installation folder have a basic setting written and there's no existing security configuration on it. Just add the rules as below.The source code as below was obtained from AllGuru.Net , # Protect from spam comments <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{REQUEST_METHOD} POST RewriteCond %{REQUEST_URI} .wp-comments-post\.php* RewriteCond %{HTTP_REFERER} !.*xyz.* [OR] RewriteCond %{HTTP_USE