NOTE: WordPress is right for you, only if you want to actually launch your membership site some day, make money from your site, and do not wish to spend an insane amount of time creating and maintaining it, and only if you do not wish to spend hundreds (or thousands) of dollars outsourcing the creation and maintenance of your site

I recently happened across a blog post that presents an argument about why you should not use WordPress for your membership site.

That seems to have caused quite a stir among my target audience (who are basically people who want to start a membership site using WordPress).

A couple of them wrote to me and asked me for my opinion, 1) because I am such a big evangelist of WordPress, and 2) because I have developed a Membership Plugin for WordPress.

I read the argument with interest, and of course felt that it was a very extreme, one-sided worldview of WordPress. I tried to comment there on the site itself, but I got a message that “the site owner has blocked you from commenting”. Not sure why. I will try again. But in the mean time, I simply had to post this here.

So, after you’ve read Alex’s argument for why you should not use WordPress for your membership site, read my (well-rounded, well-educated and balanced, IMHO opinion about why you would be foolish NOT to use WordPress for your membership site – especially if you’re a small-biz owner, info-product marketer, blogger or Do-It-Yoursef’er, and don’t have a big team or a big budget to outsource your membership site development.

My note to Alex…

Alex,

Having developed Wordpress and Non-WordPress scripts for almost 15 years now, I have to respectfully disagree with your argument for not using WP for membership sites.

Let me try to present an objective argument here.

You wrote:
>>it doesn’t matter which one you will choose to use as they all share one big flaw – their dependency on the core of WordPress!<<

I am the developer of a plugin called DigitalAccessPass (DAP), which does *not* have a dependency on the core of WordPress. DAP is a separate piece of software, that can be plugged on TOP of wordpress, and only needs a simple, light-weight “Plugin” that acts as a “bridge” between WP and DAP. In the 15 months since the launch of DAP, and 10 months prior to that when we were developing DAP, WP has released a huge number of updates in those 25 months (2+ years), and we have *never* had a single instance where a WP update affected our script.

Again, it’s all in the design, right? DAP was deliberately designed from the ground up *not* to have a dependency on *any* CMS, not even WP. That’s the reason why DAP works right out of the box with regular, plain-ol HTML web sites, and using the “bridge” plugin concept, can be integrated into other CMS like Joomla, Drupal, etc (Joomla plugin for DAP is in the works as I write this). In fact, with just a little bit of work, DAP can be made to work with every imaginable CMS out there, for this very reason.

>>By themselves they will not function and same goes the WordPress core<<
See above. DAP will function all by itself with just regular HTML web sites.

>>WordPress is Open Source and its code is constantly under scrutiny not only by the good guys but also by people who are looking for a way to compromise your site<<
I can kind of agree with you there, but then, even software and services from even high profile companies, like Google and Microsoft get hacked or gamed. So, just because it’s open source doesn’t mean it’s more vulnerable, and just because it’s “closed source” doesn’t mean it is secure. It all depends on the developers and the community behind it.

I mean, non-WP sites get hacked all the time because the shared-site owner left a PHP script in there that’s vulnerable to XSS attacks, or left the permissions wide open inviting hackers to come join the party. That actually says more about the security of PHP itself, and the security of a shared-host environment. But why blame WP for that?

>>You quickly contact support of the developer who created the plugin you use for Membership Management before jumping into upgrade, as you have to ensure that it will continue to work with new version only to learn that he is taking romantic vacation on secluded island somewhere in Fiji and will not be back for next couple weeks…<<

Yes, I agree, that if you went with a small-time, one-man-developer solution, then regardless of whether they are in Fiji, or get hit by a bus, you’re going to be in trouble. That’s why you pick software from companies like mine, which have been around for 15 years, have written millions of lines of code for small businesses as well as for the enterprise, have a team in place for support, and won’t be going away any time soon (we can’t, because this is what we do .

>>I personally prefer that my membership script is separate and with dedicated support!<<
DAP totally fits the bill here . It is separate, and has dedicated, “non-outsourced” support

You are recommending a downloadable script solution at the end of your post – one which is developed in PHP. PHP has always been (arguably) one of the most insecure programming languages, just because, if you didn’t quite know what you’re doing, it allowed newbies to easily shoot themselves in the foot. Of course, PHP has come a long way since then, but it’s still not the most secure language.

Are we next going to start recommending that no one should use PHP scripts at all, and instead use something like Java or .NET?

So, whether it’s a programming language (PHP), a content management system (WP) or an operating system (Windoze), the solution is only as secure as its developers, the company backing it, and the community supporting it.

And most importantly, the security of a site is only as good as the actual “user” using it (if you download spyware and infected .exe files from the web and your computer gets infected, can you really blame Microsft for it?).

I guess you could blame MS, but that doesn’t mean you’re right.

So, when it comes to the quality of code, extensibility (hooks and filters and plugins) and the community, and the insanely large user base, WordPress simply can’t be beaten.

And when it comes to a membership script for WordPress, DAP also can’t be beaten

My humble $0.02

Appreciate the soapbox, the opportunity, and for your great post which seems to have evoked so many great responses

Thanks much!

- Ravi Jayagopal
Founder & Developer, DigitalAccessPass .com
(Membership Script for WordPress)

I’m hoping to augment this soon with a more detailed article about using WordPress as the platform to build your membership site.

So stay tuned by subscribing to this blog or by following me on twitter.

Feel free to pass this link to other WordPress lovers, and don’t forget to add your comments below. And no, I won’t block them – even if you’re Alex

1 year ago, I launched a membership plugin for WordPress, called DigitalAccessPass (DAP).

It had some ground-breaking features – many firsts for its niche. Like “Content Dripping”, for example (I even coined a new word: ContentResponder .

Yesterday (October 11, 2009), DAP celebrated it’s 1st birthday!

Just some proof that with a lot of focus, hard work, persistence, passion, great customer service and a little bit of smarts, it is possible to create something a lot bigger than what was in your dreams

Click here to see how the birthday party went down…

1. Create a file called phpinfo.php




2. Enter these few lines of code in it: (you can copy-paste from below):
   
   <?php
phpinfo();
?>




3. Upload this to your root folder (where your home page (index.htm or index.html etc) lives.




4. Access this script via the browser like this:
   
   http://www.YourSite.com/phpinfo.php




5. You should see a nice page come up, with the PHP logo and headers, that shows all of your PHP configuration and settings. If you see it, then: Hurrah, you can run PHP on your site!




6. If you see some kind of errors, first try changing the file’s permissions (chmod) to 755. (CHMOD Tutorial)




7. If that still doesn’t work, then you’re probably SOL (S#!t Outta Luck). Confirm it with your web host.




8. If your web host doesn’t support PHP, don’t waste your time – or your web site – with your current host. Just switch to where I host my own sites.




9. WARNING: Don’t forget to delete the phpinfo.php file from your web site. Hackers can figure out a lot of stuff from this page!

I recently asked a very close non-blogger, never-blogged-before friend to start his own blog on my new multi-blog site, YehHaiIndia.com (driven by WordPress Mu – very cool software).

His immediate response was:

The problem with blogging is you need ideas and thoughts you want to write.

And you are assuming I have thoughts that are worth writing about….

The biggest problem with publishing a blog, is not that you may not have enough or something worthy to say.

The biggest problem is actually “fear”.

“I can’t believe he wrote something that stupid!”
“What the heck was she thinking when she wrote that?”
“He has no idea what he is talking about!”

Fear of criticism. Fear of being judged.

We don’t want to put our thoughts and opinions “out there” for everyone to judge; and for some to call us “a moron”, “clueless”, “totally wrong”.

Whereas blogging is like thumbing your nose at this fear.

You put yourself out there in every post. Every thought and comment and opinion in your blog is yours – and yours alone. You are setting yourself up for criticism and judgment and name-calling. And you want people to read your posts, criticize you, judge you, interact with your blog and give you feedback.

As long as we fear this feedback, we simply cannot do remarkable things.

No, it doesn’t mean you ignore common sense and do something stupid (like putting crazy photos of you on your blog while somehow involving your employer).

It means that if your post makes sense, and all you fear is being judged by your colleagues, friends or family – and fear about what others might say, then I say, just get over it, thumb your nose at your fear, and get ‘er done.

The whole idea of podcasting is not to be just able to publish your audio files online, but to make your audio posts “subscribable” – i.e., your listeners should be able to set up their podcasting software (like iTunes) to subscribe to your feed, in which case the software (in this example, iTunes) will automatically download your newest posts to their hard disk, as soon (or soon after) you make your posts live.

Which means, when they next sync up their mp3 player (say, iPod), your newest audio posts will automatically be synced from your subscriber’s hard disk to their iPod.

That’s the real “subscription” model of podcasting.

So how to make your WordPress feed refer to your podcast? Simple:

1. Create your audio file (mp3, mp4, etc)
2. Upload it to your server (into a folder in your main directory, say “podcasts”)
3. Your post can have your usual text content, but make sure your post has a link to the actual audio file. Note: It has to be the full path.

   Wrong: <a href="yourfile.mp3">My podcast</a>
Right: <a href="http://Example.com/podcasts/aug2007-vol1.mp3">My podcast

4. WordPress automatically links your feed to your audio file, such that if someone were to view your blog posts in a feed reader, and clicked on the link for your audio post, then they won’t be led to your blog, but the audio file will start playing instead.
5. Once your listeners “subscribe” to your feed, their podcasting software automatically downloads new files (posts with your audio file in it) to their hard disk automatically.

WordPress is not perfect – not just yet. But there really isn’t any software out there that can do all it does: well written, open-source, extensible, has lots of plugins, and has a great community around it – like WordPress.

So, just make peace with the “comparison war” (which is better: WordPress, Drupal, Joomla, etc), simply download WordPress (or sign up for a free blog online), and get going with your content.

Content is what makes money – not your blog software.

You know what is Blog-And-Ping. Blog-And-Bookmark is quite similar.

You first blog about something (hopefully) interesting, then once your blog’s ping service has done its work on the back-end pinging all of the various web sites and your post is live, then you go to work as follows.

Use a one-to-many social bookmarking tool like AddMe.com or Socializer. I use AddMe on my blog itself, but use Socializer when I am actively bookmarking my own posts. Also check out the one-form-many-bookmarks site OnlyWire.com.

Add a bookmark to your post at all leading sites starting with StumbleUpon.com, Digg.com, Reddit.com and Netscape.com. You should do it manually for these sites, and use OnlyWire.com for automated submission to the rest of the sites.

I highlight StumbleUpon, Digg, Reddit and Netscape here, because those are the ones that send about 95% of the social bookmarking traffic that my blog gets. The rest of them add up to only about 5%, but pursuing them is still worth it due to the number of back-links (incoming links) you will get.

See the Feedburner statistics (screenshot) below for RavisRants.com.

Note the spike in traffic every time I do blog-and-bookmark myself. It not only brings in a fresh supply of visitors, but also increases my number of average subscribers (Feedburner only reports that number for one given day, as the number can vary from day to day). This is not only a great way to get first time visitors, but also to get some new feed subscribers.

So, don’t forget to blog-and-ping, tag-and-ping, and blog-and-bookmark every single time you post.

I was getting about 500+ spam-comments a day. I’m now down to about 20. Based on my personal experience with spam, I have created a list of “bad words”, which, when used as a blacklist, will make most of your spam go away.

If you’re using Wordpress, copy the list below and paste it into the “Options > Discussion > Comment Blacklist” box.

Now WordPress warns:

“This is a list of words that you want completely blacklisted from your blog. Be very careful what you add here, because if a comment matches something here it will be completely nuked and there will be no notification. Remember that partial words can match, so if there is any chance something here might match it would be better to put it in the moderation box above.”

So, go through the list and weed out any words that you think might be acceptable for your blog. So here goes…

Note: This list will be updated as often as I find new words to blacklist. So bookmark this post (see “bookmark” and “subscribe” links in the menu to your right) and check back occasionally.

4free
4u
accutane
actos
acyclovir
adderall
adipex
allegra
Alprazolam
altace
ambien
Amoxicillin
amoxil
amphetamine
anal
anime
antibiotic
arousal
atfreeforum.com
ativan
attorney
augmentin
Azithromycin
babe
baccarat
bdsm
benadryl
biaxin
bitch
blackjack
blowjob
bondage
boob
booty
bowflex
bulabital
bupropion
butalbital
camry
car
carisoprodol
cartier
casino
celebrex
celexa
chick
cialis
cipro
citalopram
claritin
clonazepam
cock
codeine
codine
Crestor
crotch
cruise
cruises
cum
cunt
cyclen
cyclobenzaprine
cymbalta
dada
diazepam
dick
didrex
diovan
directbookmarks.info
dodge
doxycycline
drugstores
edvttj
Effexor
elavil
ephedra
ephedrine
erotica
escort
estate
facial
famvir
finland
Fioricet
forex
freewebs
fuck
gambling
gay
glucophage
gucci
helsinki
hentai
holdem
honda
hoodia
horny
hummer
hydrochlorothiazide
hydrocodone
incest
indianapolis
jaguar
jewelry
Lamictal
lasix
lesbian
lesbians
levaquin
levitra
Lexapro
lexus
lipitor
loan
lopressor
lorazepam
masterbating
mazda
medication
meridia
metalica
mevacor
Minolche
myfreedir.info
mysex
necklace
Nexium
Nicotine
nissan
norvasc
nude
orgasm
orgy
Oxycodone
Oxycontin
p0tassium
panties
panty
paxil
penis
percocet
pharmacy
phentermine
phpbb
plavix
poker
porn
Potassium
pravachol
prednisone
prevacid
prilosec
propecia
Protonix
prozac
pussy
rape
refinance
ringtones
ritalin
rolex
roulette
seroquel
sex
shemale
silveno
slot
soma
sphost
swinger
tadalafil
tadalis
tawnee
teen
testosterone
tetracycline
tissot
tit
toon
toyota
Tramadol
Trazodone
twinks
ultracet
ultram
valerian
Valium
viagra
Vicodin
vioxx
Wellbutrin
wholesale
Xanax
xenical
xxx
zanaflex
Zenegra
zithromax
zocor
Zoloft
zolus
zovirax
Zyprexa

Last updated on…:
2007: 3/30, 3/31, 4/2, 4/3, 4/20, 7/17