Purab

how to prevent spam comments wordpress

If you are internet user then you know about what is spam. You know or saw spam emails earlier so many times. prevent spam comments wordpress is big task and important also.

how to prevent spam comments wordpress

Comment Spam Hacks

The following are not recommended for average users. They involve editing WordPress core files. BACKUP your files first.

Delete wp-comments-post.php

The ultimate end-all solution to your comment spam troubles. This will effectively disable comments and is good for stopping comment spam floods. No one will be able to comment on your WordPress site.

Delete wp-trackback.php

The ultimate end-all solution to your trackback spam troubles. This will effectively disable trackbacks and is good for stopping trackback spam floods. This will mean that no one will be able to trackback your posts, so do this after consideration.

Denying access with .htaccess

While drastic, you can make modifications in your .htaccess file if you are using an Apache server. Check the Internet and Apache for more information.

Use nofollow

The nofollow attribute is another method used to strip spammers of their page ranks. According to Google, “when Google sees the attribute (rel=”nofollow”) on hyperlinks, those links won’t get any credit when we rank websites in our search results.” Under WordPress v1.5, the nofollow attribute is automatically added to all links in the comments section.

WordPress comes with a pre installed antispam solution – Akismet.

In order to use Akismet, you should have a WordPress API key. To receive a WordPress API key, you should register at the official WordPress website. The key will be included in your welcome mail.

If you already have a registration at WordPress.org, you can see your API key by visiting the WP dashboard.

To enable Akismet for your blog, follow the steps below:

Step 1. Go to your WordPress admin area > Plugins > Installed.

Step 2. Click Activate.

There are many ways to protect your WordPress.com blogs from unwanted comments:

* WordPress.com blogs are protected by the Akismet comment spam filter.
* You can control whether comments are automatically approved or if they need to be reviewed before they are published.
* You can add rules for comment moderation to control which comments get marked as pending.
* You can add rules to the comment blacklist section to automatically mark some comments as spam.
* If you turn on email notifications, then you can watch those messages for spam and delete them quickly if you find any that get through the comment spam filter.

Akismet learns by those who mark comment spam as comment spam and legitimate spam is despammed. If your comments are being caught by Akismet, remove them from the Akismet Panel. It might take two or three times, but it will learn and automatically not designate your comments as spam.

Commenters on your blog may have their comments caught by Akismet. If you do not regularly check your Akismet Panel, have an easy way of allowing readers to email you if their comment did not appear.

With updates to the database and major changes to the software, this process may have to be repeated.

If you continue to have problems with Akismet catching your comments or too many of your readers’ comments, contact Akismet for more assistance.

Today WordPress.com goes down with millions of websites

WordPress news about Today WordPress.com goes down with millions of websites . Following are update which are on twitter.

Update #1: ‘We are working on restoring WordPress.com as quickly as possible.”

Following is update from twitter account of wordpress.com

Update #2: “We’ve isolated the issue on WordPress.com, and we are working on a fix.”

Update #3: “The vast majority of blogs are back up, bringing up the rest over the next few minutes after we verify them. — Matt Mullenweg”

Update #4: “That’ll come up later, probably in an hour or two. Focused on blogs right now.”

Update #5: “We’re focused on blogs right now — the ones still down, then home page, then stats, in that order.”

Millions of blogs had shown following message today

Software publisher Automattic, which runs WordPress.com, went down today and took millions of blogs and other websites with it. Sites down were WordPress.com hosted websites, VIP WordPress sites (like Anderson Cooper’s CNN Blog), link shortener WP.me, WordPress.tv, Automattic.com and probably more.

Automattic’s founder Matt Mullenweg’s personal website ma.tt was still online along with other Automattic websites:

* WordPress.org
* bbPress.org
* BuddyPress.org
* Gravatar.com
* PollDaddy.com

WordPress.org software installations on private servers were not affected by the outage. Domain name registrar GoDaddy was attacked with malware on Tuesday (June 8) which infected a number of WordPress installations hosted on them. Today’s problem at WordPress.com was not a security issue according to founder Mullenweg.

Twitter is scanning all shortened URLs befor being posted

Twitter is routing links within Direct Messages through our link service to detect, intercept, and prevent the spread of malware, phishing, and other dangers. Any link shared in a Direct Message has been wrapped with a twt.tl URL.

Twitter is scanning all shortened URLs befor being posted

Links reported to us as malicious are blacklisted, and we present users with a page that warns them of potentially malicious content if they click blacklisted links. Twitter wants users to have this benefit on all tweets.

Twitter is scanning all shortened URLs befor being posted

Raffi Krikorian, a technical lead on the Twitter Platform Team, explained in a Google Groups posting that the t.co system will always format links to 20 characters.

Additionally, as we mentioned at our Chirp developer conference in April, if you want to share a link through Twitter, there currently isn’t a way to automatically shorten it and we want to fix this. It should be easy for people to share shortened links from the Tweet box on Twitter.com.

To meet both of these goals, we’re taking small steps to expand the link service currently available in Direct Messages to links shared through all Tweets. We’re testing this link service now with a few Twitter employee accounts.

This change will is specially made for mobile users. In addition to a better user experience and increased safety, routing links through this service will eventually contribute to the metrics behind our Promoted Tweets platform and provide an important quality signal for our Resonance algorithm—the way we determine if a Tweet is relevant and interesting to users. We are also looking to provide services that make use of this data, an example would be analytics within our eventual commercial accounts service.

How to use smiley images in wordpress posts

If you want to use smiley images in wordpress posts then you can use our tricks. Here in this article, we given sample and trick for using smiley in posts.

Follow our steps.

Find your smiley image files in the /wp-includes/images/smilies directory and back them up to another directory
Note the names of each smiley file. Your files must match these names and should be in the same ‘gif’ image format.
For predictable behavior, the image sizes should be similar.
Upload your new files to the /wp-includes/images/smilies directory with an FTP program.

How to use smiley images in wordpress posts

If you want to changes the names of smiley and you need to edit wp-includes/functions.php file.

In that file you will find the “smilies_init” function.

You will find the following code in that file.


if ( !isset( $wpsmiliestrans ) ) {
 $wpsmiliestrans = array(
 ':mrgreen:' => 'icon_mrgreen.gif',
 ':neutral:' => 'icon_neutral.gif',
 ':twisted:' => 'icon_twisted.gif',
 ':arrow:' => 'icon_arrow.gif',
 ':shock:' => 'icon_eek.gif',
 ':smile:' => 'icon_smile.gif',
 ':???:' => 'icon_confused.gif',
 ':cool:' => 'icon_cool.gif',
 ':evil:' => 'icon_evil.gif',
 ':grin:' => 'icon_biggrin.gif',
 ':idea:' => 'icon_idea.gif',
 ':oops:' => 'icon_redface.gif',
 ':razz:' => 'icon_razz.gif',
 ':roll:' => 'icon_rolleyes.gif',
 ':wink:' => 'icon_wink.gif',
 ':cry:' => 'icon_cry.gif',
 ':eek:' => 'icon_surprised.gif',
 ':lol:' => 'icon_lol.gif',
 ':mad:' => 'icon_mad.gif',
 ':sad:' => 'icon_sad.gif',
 '8-)' => 'icon_cool.gif',
 '8-O' => 'icon_eek.gif',
 ':-(' => 'icon_sad.gif',
 ':-)' => 'icon_smile.gif',
 ':-?' => 'icon_confused.gif',
 ':-D' => 'icon_biggrin.gif',
 ':-P' => 'icon_razz.gif',
 ':-o' => 'icon_surprised.gif',
 ':-x' => 'icon_mad.gif',
 ':-|' => 'icon_neutral.gif',
 ';-)' => 'icon_wink.gif',
 '8)' => 'icon_cool.gif',
 '8O' => 'icon_eek.gif',
 ':(' => 'icon_sad.gif',
 ':)' => 'icon_smile.gif',
 ':?' => 'icon_confused.gif',
 ':D' => 'icon_biggrin.gif',
 ':P' => 'icon_razz.gif',
 ':o' => 'icon_surprised.gif',
 ':x' => 'icon_mad.gif',
 ':|' => 'icon_neutral.gif',
 ';)' => 'icon_wink.gif',
 ':!:' => 'icon_exclaim.gif',
 ':?:' => 'icon_question.gif',
 );

You can edit that names as per your requirement and add more smiley.

If you want to put some css for your smiley then you can use or put following CSS class in your style.css file (Theme folder).

img.wp-smiley {
   float: none;
   padding:2px;
   border:none;
}

That sit! Have fun.

Use smilies/smileys in wordpress posts

By default, WordPress automatically converts text smileys to graphic images. In this post I showed how to Use smilies/smileys in wordpress posts

Use smilies/smileys in wordpress posts

Smileys, also known as “emoticons,” are glyphs used to convey emotions in your writing. They are a great way to brighten up posts.

By default, WordPress automatically converts text smileys to graphic images. When you type 😉 in your post you see when you preview or publish your post.

If you turn off graphic smileys, whatever you type in plain text will remain, and be displayed, as plain text.

Go to your Admin Panel
Select Settings -> Writing
In the Formatting section, uncheck the box for “Convert emoticons like 🙂 and 😛 to graphics on display“

Turning off emoticons means that when you type 😉 in a post you will see 😉 when you preview or publish your post. So it doesn’t stop you from using emoticons as plain text.

What Text Do I Type to Make Smileys?

Smiley images and the text used to produce them*:

text	text	full text	full text
🙂	🙂	🙂	😆
😀	😀	😀	😳
🙁	🙁	🙁	😥
😮	😮	😮	👿
😯	😯	😯	😈
😕	😕	😕	🙄
8)	😎	😎	❗
😡	😡	😡	❓
😛	😛	😛	💡
😐	😐	😐	➡
😉	😉	😉

* In some instances, multiple text options are available to display the same smiley.

Note: The smiley or emoticon image graphics are found in the /wp-includes/images/smilies directory.

How to install siege on Linux box

In this article I given step by step information about How to install siege on Linux box. I given the full commands and there output with full description.

How to install siege on Linux box

ABOUT SIEGE – Background
Siege is an http load testing and benchmarking utility. It was designed to let web developers measure their code under duress, to see how it will stand up to load on the internet. Siege supports basic authentication, cookies, HTTP and HTTPS protocols. It lets its user hit a web server with a configurable number of simulated web browsers. Those browsers place the server “under siege.”

PLATFORM SUPPORT
Siege was written on GNU/Linux and has been successfully ported to AIX, BSD, HP-UX and Solaris. It should compile on most System V UNIX variants and on most newer BSD systems. Because Siege relies on POSIX.1b features not supported by Microsoft, it will not run on Windows. Of course you can use Siege to test a Windows HTTP server.

Download siege from following URL or Using following command
[kapil@kapil-pc ~]$ wget ftp://ftp.joedog.org/pub/siege/siege-latest.tar.gz
[kapil@kapil-pc ~]$ tar xzf siege-latest.tar.gz
[kapil@kapil-pc ~]$ mv siege-2.69 siege
[kapil@kapil-pc ~]$ cd siege
[kapil@kapil-pc siege ~]$ su
[root@kapil-pc siege ~]$ ROOT_PASSWORD

If you got above error Please Use following command.

[root@kapil-pc siege ~]$ yum install gcc*

Than run following command again

[root@kapil-pc siege ~]$ ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking whether make sets $(MAKE)… yes
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking for style of include used by make… GNU
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ANSI C… none needed
checking dependency style of gcc… none
checking how to run the C preprocessor… gcc -E
checking for egrep… grep -E
checking for AIX… no
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ANSI C… (cached) none needed
checking dependency style of gcc… (cached) none
checking for a sed that does not truncate output… /bin/sed
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for /usr/bin/ld option to reload object files… -r
checking for BSD-compatible nm… /usr/bin/nm -B
checking whether ln -s works… yes
checking how to recognise dependent libraries… pass_all
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking dlfcn.h usability… yes
checking dlfcn.h presence… yes
checking for dlfcn.h… yes
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking dependency style of g++… none
checking how to run the C++ preprocessor… g++ -E
checking for g77… no
checking for f77… no
checking for xlf… no
checking for frt… no
checking for pgf77… no
checking for fort77… no
checking for fl32… no
checking for af77… no
checking for f90… no
checking for xlf90… no
checking for pgf90… no
checking for epcf90… no
checking for f95… f95
checking whether we are using the GNU Fortran 77 compiler… yes
checking whether f95 accepts -g… yes
checking the maximum length of command line arguments… 32768
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for objdir… .libs
checking for ar… ar
checking for ranlib… ranlib
checking for strip… strip
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC
checking if gcc PIC flag -fPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
configure: creating libtool
appending configuration tag “CXX” to libtool
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC
checking if g++ PIC flag -fPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
appending configuration tag “F77” to libtool
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for f95 option to produce PIC… -fPIC
checking if f95 PIC flag -fPIC works… yes
checking if f95 static flag -static works… yes
checking if f95 supports -c -o file.o… yes
checking whether the f95 linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for perl… /usr/bin/perl
checking for a POSIX-compliant shell… /bin/sh
checking whether make sets $(MAKE)… (cached) yes
checking for a BSD-compatible install… /usr/bin/install -c
checking for buggy pthread mutex initializers… no
checking for dlopen() in -ldld… no
checking for dlopen() in -ldl… yes
checking for ssl support… yes
checking off/include/openssl/opensslv.h usability… no
checking off/include/openssl/opensslv.h presence… no
checking for off/include/openssl/opensslv.h… no
checking /usr/include/openssl/opensslv.h usability… yes
checking /usr/include/openssl/opensslv.h presence… yes
checking for /usr/include/openssl/opensslv.h… yes
checking for OpenSSL version… >= 0.9.8 (appropriate flag set)
checking for ANSI C header files… (cached) yes
checking for sys/wait.h that is POSIX.1 compatible… yes
checking fcntl.h usability… yes
checking fcntl.h presence… yes
checking for fcntl.h… yes
checking for unistd.h… (cached) yes
checking signal.h usability… yes
checking signal.h presence… yes
checking for signal.h… yes
checking sys/socket.h usability… yes
checking sys/socket.h presence… yes
checking for sys/socket.h… yes
checking sys/select.h usability… yes
checking sys/select.h presence… yes
checking for sys/select.h… yes
checking sys/time.h usability… yes
checking sys/time.h presence… yes
checking for sys/time.h… yes
checking sys/times.h usability… yes
checking sys/times.h presence… yes
checking for sys/times.h… yes
checking sys/resource.h usability… yes
checking sys/resource.h presence… yes
checking for sys/resource.h… yes
checking errno.h usability… yes
checking errno.h presence… yes
checking for errno.h… yes
checking arpa/inet.h usability… yes
checking arpa/inet.h presence… yes
checking for arpa/inet.h… yes
checking netinet/in.h usability… yes
checking netinet/in.h presence… yes
checking for netinet/in.h… yes
checking netdb.h usability… yes
checking netdb.h presence… yes
checking for netdb.h… yes
checking pthread.h usability… yes
checking pthread.h presence… yes
checking for pthread.h… yes
checking for string.h… (cached) yes
checking for strings.h… (cached) yes
checking sched.h usability… yes
checking sched.h presence… yes
checking for sched.h… yes
checking openssl/e_os.h usability… no
checking openssl/e_os.h presence… no
checking for openssl/e_os.h… no
checking openssl/e_os2.h usability… yes
checking openssl/e_os2.h presence… yes
checking for openssl/e_os2.h… yes
checking for an ANSI C-conforming const… yes
checking for size_t… yes
checking whether time.h and sys/time.h may both be included… yes
checking return type of signal handlers… void
checking for working alloca.h… yes
checking for alloca… yes
checking for strchr… yes
checking for memcpy… yes
checking for strncpy… yes
checking for strstr… yes
checking for strlen… yes
checking for strncasecmp… yes
checking for strncmp… yes
checking for socket… yes
checking for gethostbyname… yes
checking for snprintf… yes
checking for strdup… yes
checking for rand_r… yes
checking for localtime_r… yes
checking for getipnodebyname… no
checking for freehostent… no
checking for getopt_long… yes
checking for socket in -lsocket… no
checking for pthread_attr_init in -lpthread… yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating doc/Makefile
config.status: creating html/Makefile
config.status: creating lib/Makefile
config.status: creating lib/joedog/Makefile
config.status: creating include/Makefile
config.status: creating include/joedog/Makefile
config.status: creating utils/Makefile
config.status: creating include/config.h
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: executing default-2 commands
config.status: executing default-3 commands
config.status: executing default-4 commands
config.status: executing default-5 commands
config.status: executing default-6 commands

——————————————————–
Configuration is complete

Run the following commands to complete the installation:
make
make install

To upgrade an old siegerc file (optional):
mv ~/.siegerc.new ~/.siegerc

For complete documentation: http://www.joedog.org
——————————————————–

Than Use following command

[root@kapil-pc siege ~]# make
Making all in .
make[1]: Entering directory `/home/kapil/testing/siege’
make[1]: Nothing to be done for `all-am’.
make[1]: Leaving directory `/home/kapil/testing/siege’
Making all in include
make[1]: Entering directory `/home/kapil/testing/siege/include’
make all-recursive
make[2]: Entering directory `/home/kapil/testing/siege/include’
Making all in joedog
make[3]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Nothing to be done for `all’.
make[3]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Nothing to be done for `all-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include’
make[2]: Leaving directory `/home/kapil/testing/siege/include’
make[1]: Leaving directory `/home/kapil/testing/siege/include’
Making all in lib
make[1]: Entering directory `/home/kapil/testing/siege/lib’
Making all in joedog
make[2]: Entering directory `/home/kapil/testing/siege/lib/joedog’
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o memory.lo memory.c
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c memory.c -fPIC -DPIC -o .libs/memory.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c memory.c -o memory.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o notify.lo notify.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c notify.c -fPIC -DPIC -o .libs/notify.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c notify.c -o notify.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o perl.lo perl.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c perl.c -fPIC -DPIC -o .libs/perl.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c perl.c -o perl.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o util.lo util.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c util.c -fPIC -DPIC -o .libs/util.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c util.c -o util.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o snprintf.lo snprintf.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c snprintf.c -fPIC -DPIC -o .libs/snprintf.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c snprintf.c -o snprintf.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c -o stralloc.lo stralloc.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c stralloc.c -fPIC -DPIC -o .libs/stralloc.o
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I/usr/include/openssl -I/usr/include -W -Wall -g -O2 -c stralloc.c -o stralloc.o >/dev/null 2>&1
/bin/sh ../../libtool –tag=CC –mode=link gcc -W -Wall -g -O2 -o libjoedog.la -version-info 1:0:1 memory.lo notify.lo perl.lo util.lo snprintf.lo stralloc.lo
libtool: link: warning: `-version-info/-version-number’ is ignored for convenience libraries
ar cru .libs/libjoedog.a .libs/memory.o .libs/notify.o .libs/perl.o .libs/util.o .libs/snprintf.o .libs/stralloc.o
ranlib .libs/libjoedog.a
creating libjoedog.la
(cd .libs && rm -f libjoedog.la && ln -s ../libjoedog.la libjoedog.la)
make[2]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/lib’
make[2]: Nothing to be done for `all-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/lib’
make[1]: Leaving directory `/home/kapil/testing/siege/lib’
Making all in src
make[1]: Entering directory `/home/kapil/testing/siege/src’
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c auth.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c base64.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c client.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c cookie.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c cfg.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c crew.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c data.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c date.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c eval.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c getopt.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c getopt1.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c handler.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c hash.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c http.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c init.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c load.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c log.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c main.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c md5.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c sock.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c ssl.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c timer.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c url.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c util.c
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/include/openssl -I/usr/include -I/usr/include/openssl -I/usr/include -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -c version.c
/bin/sh ../libtool –tag=CC –mode=link gcc -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -L/usr/lib -lpthread -o siege auth.o base64.o client.o cookie.o cfg.o crew.o data.o date.o eval.o getopt.o getopt1.o handler.o hash.o http.o init.o load.o log.o main.o md5.o sock.o ssl.o timer.o url.o util.o version.o ../lib/joedog/libjoedog.la -ldl -lssl -lcrypto
mkdir .libs
gcc -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -W -Wall -DOPENSSL_NO_KRB5 -g -O2 -o siege auth.o base64.o client.o cookie.o cfg.o crew.o data.o date.o eval.o getopt.o getopt1.o handler.o hash.o http.o init.o load.o log.o main.o md5.o sock.o ssl.o timer.o url.o util.o version.o -L/usr/lib -lpthread ../lib/joedog/.libs/libjoedog.a -ldl -lssl -lcrypto
make[1]: Leaving directory `/home/kapil/testing/siege/src’
Making all in utils
make[1]: Entering directory `/home/kapil/testing/siege/utils’
make[1]: Nothing to be done for `all’.
make[1]: Leaving directory `/home/kapil/testing/siege/utils’
Making all in doc
make[1]: Entering directory `/home/kapil/testing/siege/doc’
make[1]: Nothing to be done for `all’.
make[1]: Leaving directory `/home/kapil/testing/siege/doc’
Making all in html
make[1]: Entering directory `/home/kapil/testing/siege/html’
make[1]: Nothing to be done for `all’.
make[1]: Leaving directory `/home/kapil/testing/siege/html’

Now you can use following command.

[root@kapil-pc siege ~]# make install
Making install in .
make[1]: Entering directory `/home/kapil/testing/siege’
make[2]: Entering directory `/home/kapil/testing/siege’
make[2]: Nothing to be done for `install-exec-am’.
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege’
make[1]: Leaving directory `/home/kapil/testing/siege’
Making install in include
make[1]: Entering directory `/home/kapil/testing/siege/include’
Making install in joedog
make[2]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[2]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include’
make[2]: Leaving directory `/home/kapil/testing/siege/include’
make[1]: Leaving directory `/home/kapil/testing/siege/include’
Making install in lib
make[1]: Entering directory `/home/kapil/testing/siege/lib’
Making install in joedog
make[2]: Entering directory `/home/kapil/testing/siege/lib/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/lib/joedog’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/lib’
make[3]: Entering directory `/home/kapil/testing/siege/lib’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/lib’
make[2]: Leaving directory `/home/kapil/testing/siege/lib’
make[1]: Leaving directory `/home/kapil/testing/siege/lib’
Making install in src
make[1]: Entering directory `/home/kapil/testing/siege/src’
make[2]: Entering directory `/home/kapil/testing/siege/src’
test -z “/usr/local/bin” || mkdir -p — “/usr/local/bin”
/bin/sh ../libtool –mode=install /usr/bin/install -c ‘siege’ ‘/usr/local/bin/siege’
/usr/bin/install -c siege /usr/local/bin/siege
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/src’
make[1]: Leaving directory `/home/kapil/testing/siege/src’
Making install in utils
make[1]: Entering directory `/home/kapil/testing/siege/utils’
make[2]: Entering directory `/home/kapil/testing/siege/utils’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/utils’
/bin/sh ../utils/mkinstalldirs /usr/local/bin
/bin/sh ../libtool –mode=install /usr/bin/install -c bombardment /usr/local/bin/bombardment
/usr/bin/install -c bombardment /usr/local/bin/bombardment
/bin/sh ../libtool –mode=install /usr/bin/install -c siege2csv.pl /usr/local/bin/siege2csv.pl
/usr/bin/install -c siege2csv.pl /usr/local/bin/siege2csv.pl
/bin/sh ../libtool –mode=install /usr/bin/install -c siege.config /usr/local/bin/siege.config
/usr/bin/install -c siege.config /usr/local/bin/siege.config
make[3]: Leaving directory `/home/kapil/testing/siege/utils’
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/utils’
make[1]: Leaving directory `/home/kapil/testing/siege/utils’
Making install in doc
make[1]: Entering directory `/home/kapil/testing/siege/doc’
make[2]: Entering directory `/home/kapil/testing/siege/doc’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/doc’
make[3]: Leaving directory `/home/kapil/testing/siege/doc’
test -z “/usr/local/man/man1” || mkdir -p — “/usr/local/man/man1”
/usr/bin/install -c -m 644 ‘./siege.1’ ‘/usr/local/man/man1/siege.1’
/usr/bin/install -c -m 644 ‘./siege.config.1’ ‘/usr/local/man/man1/siege.config.1’
/usr/bin/install -c -m 644 ‘./bombardment.1’ ‘/usr/local/man/man1/bombardment.1’
/usr/bin/install -c -m 644 ‘./siege2csv.1’ ‘/usr/local/man/man1/siege2csv.1’
test -z “/usr/local/man/man5” || mkdir -p — “/usr/local/man/man5”
/usr/bin/install -c -m 644 ‘./urls_txt.5’ ‘/usr/local/man/man5/urls_txt.5’
test -z “/usr/local/man/man7” || mkdir -p — “/usr/local/man/man7″
/usr/bin/install -c -m 644 ‘./layingsiege.7’ ‘/usr/local/man/man7/layingsiege.7′
make[2]: Leaving directory `/home/kapil/testing/siege/doc’
make[1]: Leaving directory `/home/kapil/testing/siege/doc’
Making install in html
make[1]: Entering directory `/home/kapil/testing/siege/html’
make[2]: Entering directory `/home/kapil/testing/siege/html’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/html’
HTML pages not installed
make[3]: Leaving directory `/home/kapil/testing/siege/html’
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/html’
make[1]: Leaving directory `/home/kapil/testing/siege/html’

Now siege installation is done. Than Use following command for using the siege for testing.

[root@kapil-pc siege ~]# siege
SIEGE 2.69
Usage: siege [options]
siege [options] URL
siege -g URL
Options:
-V, –version VERSION, prints version number to screen.
-h, –help HELP, prints this section.
-C, –config CONFIGURATION, show the current configuration.
-v, –verbose VERBOSE, prints notification to screen.
-g, –get GET, pull down headers from the server and display HTTP
transaction. Great for web application debugging.
-c, –concurrent=NUM CONCURRENT users, default is 10
-u, –url=”URL” Deprecated. Set URL as the last argument.
-i, –internet INTERNET user simulation, hits the URLs randomly.
-b, –benchmark BENCHMARK, signifies no delay for time testing.
-t, –time=NUMm TIME based testing where “m” is the modifier S, M, or H
no space between NUM and “m”, ex: –time=1H, one hour test.
-r, –reps=NUM REPS, number of times to run the test, default is 25
-f, –file=FILE FILE, change the configuration file to file.
-R, –rc=FILE RC, change the siegerc file to file. Overrides
the SIEGERC environmental variable.
-l, –log LOG, logs the transaction to PREFIX/var/siege.log
-m, –mark=”text” MARK, mark the log file with a string separator.
-d, –delay=NUM Time DELAY, random delay between 1 and num designed
to simulate human activity. Default value is 3
-H, –header=”text” Add a header to request (can be many)
-A, –user-agent=”text” Sets User-Agent in request
[root@kapil-pc siege ~]#

how to use update option in wordpress plugin

Most of wordpress plugin writer choose the new table for saving data for plugin setting and any setting in wordpress plugin. In this article we will show, how to use update option in wordpress plugin. I recommend to use the update option for saving data in wordpress database.

how to use update option in wordpress plugin

There is ready made option is provided by wordpress to save custom data in there table.

Here with very simple code I will show how use save the data in wordpress database.

&lt; ?php
$variable = array(‘var1′ =&gt; $_POST['var1'], ‘var2′ =&gt; $_POST['var2']);
update_option(‘myPlugin_var1′, serialize($variable));
get_option(‘myPlugin_var1′) == “” ? “” : $new = unserialize(get_option(‘myPlugin_var1′));
?&gt;

You should save data in simple variable format or I suggest always save data in array format.

For more reference you can check the following URL
http://phpxref.com/xref/wordpress/wp-admin/options.php.source.html

Yahoo and Facebook Users now exchange content and data

Yahoo users can now view their Facebook News Feed via their Yahoo home page, Yahoo Mail, and other Yahoo sites, the company said. Additionally, content created on Yahoo sites, including Yahoo News, Sports, Movies and the photo-site Flickr, can be shared with friends on Facebook.

Yahoo and Facebook Users now exchange content and data

Ethan Beard, director of Facebook Developer Network, was quoted in the Yahoo statement saying that, “by integrating with Facebook on a global scale, Yahoo is building upon an already valuable brand to give people easy ways to share the content they enjoy on Yahoo! with their friends on Facebook.”

Yahoo offered more details of the way people can connect with Facebook sites on its blog, but Facebook remained mum on the issue early Monday, without any details in its press center, blog or twitter feed. The most recent communications on these pages largely addressed privacy concerns.

Yahoo and Facebook first announced a plan to integrate services much more closely last December. At the time, Yahoo users in the U.S. were able to call up their Facebook activity streams and post status updates from the Yahoo home page, as well as use buttons to share certain Yahoo content. The companies promised much more this year via the use of Facebook’s Connect technology across Yahoo sites.

how to upload videos to wordpress blog

Here in this article we will show, how to upload videos to wordpress blog using wordpress plugin called videopress. Videopress is best worpdress plugin for videos.

VideoPress is a strong supporter of free software, including video formats and codecs. All videos uploaded to VideoPress are available for download in Ogg video format with Theora video and Vorbis audio. If you blog on WordPress.com you now have the ability to restrict VideoPress embed to only free video formats unrestricted by known patent claims or intellectual property licensing hurdles.

how to upload videos to wordpress blog

Publishers concerned about the freedom restrictions of the default VideoPress player’s use of Adobe Flash, MP4, H.264/AVC High profile video, and AAC–LC can override the default behavior through their WordPress.com blog’s Media Settings page (yourblog.wordpress.com/wp-admin/options-media.php). Your free software formats choice applies to all VideoPress videos embedded on your blog, including videos from other VideoPress publishers.

Videos included in your posts and pages will be output using HTML5 for playback using default video controls in supporting web browsers such as Mozilla Firefox 3.5+, Google Chrome 3.0+, and Opera 10.5+.

The free formats setting may be expanded in the future to include additional formats free of known patent claims. The newly supported WebM file container with VP8 video and Vorbis audio is an early example of what could become a video format without known intellectual property claims prohibiting open distribution. We plan to add support for freedom preference for self-hosted WordPress blogs through our VideoPress plugin once we have tested this new feature with the millions of active blogs on WordPress.com.

Best contact form wordpress plugins

In this article, we will tell you very nice resources for contact form in wordpress plugins. We collected unique Best contact form wordpress plugins.

best contact form wordpress plugins

1. Contact Form 7

WordPress plugin for contact form is Contact Form 7.
Contact Form 7 can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup. The form supports Ajax-powered submitting, CAPTCHA, Akismet spam filtering and so on.
You can download this plugin from following url.
http://ideasilo.wordpress.com/2007/04/30/contact-form-7/

This plugin is good to use but there no advanced options like customize css and look of contact form.

2. Spam-Free Contact Form

Spam Free Contact Form. On errors, displays elegant error messages and confirmation messages on successful mail delivery.
You can download this plugin from following url.
http://wordpress.org/extend/plugins/spam-free-contact-form/

3. WP Clean-Contact

Clean-contact hides itself from spam-bots by, and optionally will filter messages using Akismet — Capctha and skill testing questions not required.
You can download this plugin from following url.
http://www.checkfront.com/dev/extras/wp-clean-contact

4. Secure Form Mailer Plugin For WordPress

You can download this plugin from following url.
http://www.dagondesign.com/articles/secure-form-mailer-plugin-for-wordpress/

5. cformsII

Cforms is a great plugin but it hardcode some datas in PHP and JS files. It also save on WP options the URL of the blog, it’s cause some problem when you want moving your blog.
This plugin allow edit this parameter from WordPress without open your FTP client or use phpMyAdmin.
You can download this plugin from following url.
http://www.deliciousdays.com/cforms-plugin/

6. Fast and Secure Contact Form

Fast and Secure Contact Form for WordPress. This contact form lets your visitors send you a quick E-mail message. Blocks all common spammer tactics. Spam is no longer a problem. Includes a CAPTCHA and Akismet support. Additionally, the plugin has a multi-form feature, optional extra fields, and an option to redirect visitors to any URL after the message is sent. Does not require JavaScript.
You can download this plugin from following url.
http://wordpress.org/extend/plugins/si-contact-form/

how to prevent spam comments wordpress

Comment Spam Hacks

Share Article:

Share Article:

Twitter is scanning all shortened URLs befor being posted

Share Article:

How to use smiley images in wordpress posts

Share Article:

Use smilies/smileys in wordpress posts

What Text Do I Type to Make Smileys?

Share Article:

How to install siege on Linux box

Share Article:

how to use update option in wordpress plugin

Share Article:

Yahoo and Facebook Users now exchange content and data

Share Article:

how to upload videos to wordpress blog

Share Article:

best contact form wordpress plugins

1. Contact Form 7

2. Spam-Free Contact Form

3. WP Clean-Contact

4. Secure Form Mailer Plugin For WordPress

5. cformsII

6. Fast and Secure Contact Form

Share Article: