If Walmart Handed You A Store And Stocked It For You, Would You Make Money?

Whatever you do, Don’t Join InstantPlugNPay!

Well, at least not until you have read this review. My heading was not some ploy to get you to find out what is wrong with InstantPlugNPay. Rather, it was meant to get your attention because there are a few things I want you to know before you join.

Okay, so what is InstantPlugNPay?

To be totally honest, I cannot fault it any way whatsoever and if you continue reading you will soon find out why…

The concept behind InstantPlugNPay is really very simply. It was developed by Craig Haywood (or the blue guy) who is also the owner of highly successful sites like TrackThatAd. MyViralPopAds. ExitLightBox and MyViralSurfer.

From the above sites you can probably deduct that Craig focuses heavily on Viral Marketing which is good when you consider what he’s done with InstantPlugNPay

A quick summary of the IPP homepage reveals that IPP is a resell rights product website which integrates with mlm through viral marketing, but that doesn’t even begin to lift the layers of nice goodies. In Fact, Jane Mark from JPEAdvertising.com describes it better…

“I know. It’s resale rights gone MLM and viral but that doesn’t tell half the story. People who have no idea how to sell resale products have it made.

You set it for them You give them autoresponder sales letters and new, jazzy sales pages to work with. You give them all the viral tools to sell the products and they sit back and relax.

They don’t have to do a thing. I love it.

They can even let people know by twitter that they have a new product for sale right from the members area by just popping in their twitter information.“

Here is how it works…

Every member of IPP get a product store where all products in the store (supplied by Craig) is linked to your own domain name. (which you create free when you join)

Every month Craig ads 3 new products to the store, does the ad copy for you, integrate an auto responder follow-up series for you (which he hosts on your behalf). He also ties viral marketing to every product to ensure your visitors multiplies your selling efforts as well as social network marketing through the means of Twitter Tweets. Btw., if you join IPP Craig also helps you to virally grow your Twitter followers

Now, this is where it gets interesting. This is the first and only program I know of you can make a substantial income from without even paying a dime (although the pro benefits are exceptional…more on that later).

As a free member you will get 50% commission for any product sold from your store. The member who referred you will also get $2 for every product you sell, as will the member who referred them. Going pro makes this even more lucrative.

Every time you sell a product to someone, they will also get an option to join IPP (under you), so this makes it easy to get in more people underneath you, however, Craig has gone the full 9 yards to ensure getting signups is as easy as possible, by also providing you with a tracker that virally promotes itself (in other words, affiliate links you advertise) as well as your IPP products at the same time.

At the same time, you will also have access to all the information of people who buy from your store, which means you can import leads into your auto responder of known buyers.

Going Pro…

I am not going to tell you the price to be a pro member as this violates Craig’s terms of service. What I can tell you is that is that it is so low I thought it was a joke, but on a more serious note, it gives you the opportunity to rake in a small fortune every month.

As a pro member you will also earn 100% on all products in your store paid directly to your PayPal account. If you don’t have PayPal, Craig also provides you with another option that is globally accepted.

Something which made me realise Craig thought of everything is the pro member affiliate benefit. Since you get 100% profit on products in your store, it is only fitting that you should be able to get affiliates to promote your products for you.

As a pro member, each product in your store is set up with your own affiliate program which pays out 50% to your affiliates and 50% to you. All of this is handled without you having to do anything. The system even recruits affiliates for you.

Final Thoughts…

The InstantPlugNPay system is a rare gem. It is a full stay at home program where no skills are required from you. Everything, and I mean everything is done on your behalf.

I know you have probably heard the term: “You’ve never seen anything like this.” a thousand times before, but this time it is true.

This is one program I am giving a rating of 12 out of 10.

Hint: When you log in for the first time, you will be presented with a one time offer to go pro. While you can still upgrade later at a price which is still a joke, I highly recommend you do it when you are presented with the oto as it is the lowest you will ever get it at.

Click here to visit InstantPlugNPay.com

Tweet This Post

Mp3

US $91.00 (20 Bids) End Date: Thursday Sep-09-2010 8:01:19 PDT Bid now | Add to watch list

US $54.09 (9 Bids) End Date: Thursday Sep-09-2010 8:01:22 PDT Bid now | Add to watch list

US $59.95 (1 Bid) End Date: Thursday Sep-09-2010 8:01:25 PDT Bid now | Add to watch list

US $450.00 (1 Bid) End Date: Thursday Sep-09-2010 8:01:54 PDT Bid now | Add to watch list

US $91.99 (16 Bids) End Date: Thursday Sep-09-2010 8:02:25 PDT Bid now | Add to watch list

US $142.49 (16 Bids) End Date: Thursday Sep-09-2010 8:06:16 PDT Bid now | Add to watch list

US $60.00 (16 Bids) End Date: Thursday Sep-09-2010 8:09:13 PDT Bid now | Add to watch list

US $10.70 (2 Bids) End Date: Thursday Sep-09-2010 8:10:07 PDT Bid now | Add to watch list

US $82.00 (17 Bids) End Date: Thursday Sep-09-2010 8:10:23 PDT Bid now | Add to watch list

US $112.35 (2 Bids) End Date: Thursday Sep-09-2010 8:10:36 PDT Bid now | Add to watch list

Tweet This Post

WordPress Summer of Code 2009

Dad: Well, Billy, another school year is coming to a close. No more college parties, just another summer here at home. What will you do all day?

Billy: Oh, I dunno. I’ll probably work on my blog or something.

Dad: You need more direction! That blog is just your generation’s answer to comic books.

Billy: On the contrary, Dad, working on my blog utilizes my skills in programming, design, writing, critical thinking, and all sorts of other liberal artsy things that you’re paying those professors to teach me.

Dad: If only there were a more practical application for those skills, one that could lead you to fame and fortune!

Billy: Where’ve you been living, Dad? My skills are totally in demand in today’s questionable economy. An awesome WordPress developer is worth his/her weight in gold. Lead, even.

Dad: What is this WordPress?

Billy: Only the greatest open source publishing platform ever created. It’s what runs my blog. I like to fiddle around with the code and come up with cool hacks that make mine better than the average College Joe’s.

Dad: I had no idea you were that capable.

Billy: Duh, Dad. I’ve been using WordPress for a couple of years now. I could practically teach a course on it, though there are definitely things I could learn from the lead devs. They are like kings.

Dad: Hm. That kind of ability ought to be worth something. Seems like there would be programs in place for kids like you to utilize your skills while being nurtured  by people like these lead kings.

Billy: Lead devs, Dad. Not lead kings.

Dad: Maybe you could apply for an internship or something, earn a little money this summer instead of just spending mine.

Billy: Well, there is this one thing like that.

Dad perks up.

Billy: The Google Summer of Code lets college students work with lead developers on a bunch of open source projects, you can get college credit for it, and if you do a good job, you can earn up to forty-five hundred bucks over the summer. And WordPress is one of the participating projects.

Dad: !!

Billy: But it’s pretty competitive. My friend Joe applied last year and didn’t make the cut. I can improve my skills just by fiddling around on my own this summer without the rejection, thanks.

Dad: Don’t be lame! You said yourself you’re awesome. And that you could learn from the kings. And that you could earn over FOUR THOUSAND DOLLARS. Life is full of rejection, kid. Best way to get over that is to make yourself so awesome that no one wants to reject you. And know that even if they do reject you, there’s always next time.

Billy: I dunno, Dad.

Dad: Tell you what, if you apply, I’ll give you $500 toward that car you’ve been wanting, whether you’re accepted into the program or not. And if you get in and complete it successfully, I’ll match that $4500. I’d be so proud of you. And the bragging rights at work! My kid, a Google engineer!

Billy: I wouldn’t actually be a Google engineer, Dad.

Dad: Oh be quiet. Do you think Harold in shipping knows the difference?

Billy: Okay, Dad, I’ll do it!

Dad: That’s my boy.

…………………….

College students! Don’t wait for your parents to bribe you; apply to the Google Summer of Code program now! For the third year in a row, WordPress is participating, and this year we’ve got project suggestions ranging from core functionality to plugins and BuddyPress development. You name it, we want you to propose it. It’s true, competition is fierce, but hey, if you’re already hacking WordPress, you’re ahead of the pack as far as we’re concerned. Applications are being accepted as of today, and the deadline is on April 3, 2009. For more information, check out the WordPress Codex GSoC2009 page, where we suggest some projects and let you know who our kingly mentors will be this year. The GSoC FAQ is also a good place to get an overview of the program. To apply, head to the Google Summer of Code application site. Remember, we want *you* to work on WordPress this summer! And College Janes, this isn’t just for College Joes. Female applicants encouraged to apply!

Contributing to WordPress, Part I: Development

A week or two ago at WordCamp Denver, I gave a presentation about some plans to create more opportunities for people to contribute to the WordPress open source project. The icon design contest was such a success that it seems clear we need to come up with ways for non-developers to contribute their talents and skills to WordPress. Since the launch of 2.7, we’ve been working out what kinds of contribution opportunities would make sense, and we’ve come up with a handful.

This (long) weekend, many WordPress users and developers (including half the core team) will be in Austin, TX for South by Southwest. Matt Mullenweg, Ryan Boren, Mark Jaquith and I will all be there, so say hello if you’re there, too. In the spirit of all this WordPress community connecting, I’ll be posting here every day during after SxSW with information about the new contribution opportunities we’re creating. Each post will cover one or more of the following:

• Development (of course)
• QA
• Documentation
• Ideas and Opinions
• User Experience
• Graphic Design
• Accessibility
• Usability Testing
• WordPress.tv
• Community Organizing

Since the first thing people think of when they think of contributing to WordPress is PHP development, we’ll start there.

The code (which is poetry) is the meat of the application, so it makes sense that the most opportunities to contribute will continue to fall in this area. Trac is always filled with tickets that need patches, patches that need testing, and issues that need some creative developer thinking/collaboration to find the right solution to a problem that has us going in circles.

If you are proficient in PHP, consider looking through the tickets (especially the ones marked “bug,” since they should get higher priority) and writing a patch for one of them. If you’ve got more advanced skills, consider writing a patch for one of the more complex tickets, or offering corrections to a patch submitted by someone else (if needed). If you don’t trust your coding skills but know your way around the application files, look for tickets tagged has-patch and test the patches in as many browsers as you can, posting your results afterward in the ticket thread.

If you find a bug in the course of your daily use of WordPress, report it. First, check Trac to see if the issue already has a ticket. You could also scan the archives of the wp-testers list to see if people have been talking about the bug, or email the list yourself to see if anyone has any information on the problem. If these actions don’t bear fruit, start a new ticket in Trac (you’ll need to create a login to do this). Be as detailed as you can about the issue, and don’t forget to make the proper selections from the metadata dropdown menus. Just in case anyone is unsure of how to make these selections…

Use the severity field with caution. Most bugs will be of normal severity. Marking a bug as high severity will not necessarily speed up development, and if it turns out that you’ve marked a bug’s severity incorrectly it may even slow down development.

Priority will usually be normal. Leave it to the more senior developers to change the status to a higher priority, as they are familiar with all the tickets and Trac and will be better able to assess the priority in relation to other tickets.

Ticket type. This is one of most misused fields, with many people marking tickets as defects that should not be. To address this, here’s a reminder of the ticket types and their intended uses. Your choices are: defect (bug), enhancement, feature request, and task (blessed).

• Defect (bug). Something is broken. You know how the feature is supposed to work (if you’re unsure, check the Codex or ask in the dev channel), but something has gone awry that needs to be fixed.
• Enhancement. Something is awkward or slow and could be designed or coded better without overhauling the function or screen design. Please don’t mark something as a defect (bug) if it is really an enhancement.
• Feature request. If there’s something that could be improved that would require significant restructuring of code or screen design, it should be marked as feature request rather than enhancement. Please note: this is not really the place to request features that are not currently in WordPress. Please continue to use the Ideas forum to suggest new features. The core developers will add new feature requests to Trac as they review the Ideas forum with each release cycle.
• Task (blessed). This type indicates approval from the core development team. Only core developers should use this selection. If you mark something as Task (blessed) yourself, you will have bad karma.

Bug Hunts*! If you have checked the Codex page for bug hunts lately, you’ll notice it’s been awhile since there was one. No more! Official bug hunts, sprints for finding and fixing bugs, will be brought back on a regular basis. The first one will be announced soon, possibly next week, to try and tackle the bug tickets related to widgets. (No need to wait, though, there are hundreds of open tickets in the 2.8 milestone just waiting for a kind developer to pay them some attention.)

As always, contributing developers can communicate with each other and with the core team in the #wordpress-dev IRC channel at irc.freenode.net, on the wp-hackers list, and in the ticket threads on Trac. Regular developer chats in IRC will be returning to Wednesdays at noon (Pacific time) starting next week.

[* - I used to love the bug hunt challenge in Space Cadet 3D Pinball back in the days of Windows 95]

Change the Web Challenge

We’re excited to be part of the Change the Web Challenge.

Basically, the contest is to create a plugin, widget, mash up, hack, or other variety of web application that helps people find and share opportunities to take action. The grand prize is 50 benjis, and the best WordPress plugin will also be featured in the Plugin Directory. But the real prize is spreading a little more love in the world.

Click here for all the details.

“Writing a Plugin” in the WordPress Codex is where I got started when I needed to get hooked in to WordPress. Others might like to grab one of the over 4,000 open source WordPress plugins and tweak the source. If in need of a little help, the Plugins and Hacks forum is full of friends to assist you wrap your head around the code or debug a problem. Social Actions also has provided some developer resources.

Let’s show them how we change the web the WordPress way!

New and Improved Plugins Directory Search

One of the biggest problems and most frequent complaints we’ve had with the WordPress.org Plugins Directory is the horrible, horrible search results.

No longer.  We’re now using Sphinx (a “free open-source SQL full-text search engine”) to power search on the Plugins Directory both from the website and from within your blog’s admin (Plugins → Add New).

It works much better. There are a few oddities floating around (our fault not sphinx’s) that we’ll be cleaning up shortly, but we’re happy enough with it on the whole to start letting everyone else use it

Currently, the search only indexes the plugin’s title and description/installation/FAQ/etc. (from the plugin’s readme.txt file), but we’ll be adding things like authors and tags soon.

WordPress 2.7.1

2.7.1, the first 2.7 maintenance release, is now available.  2.7.1 fixes 68 tickets.  You can automatically upgrade from 2.7 to 2.7.1 via the Tools → Upgrade menu, or you can download the package and upgrade manually.

You may have noticed that we went much longer than usual to release this .1 update. We’re very proud of this fact because it’s a testament to the testing all of you contributed prior to the release of 2.7 which helped make it the most bug-free release we’ve had.

Consult the list of fixed tickets and the  full set of changes between 2.7 and 2.7.1 for details.

Finally partly due to the stability of the 2.7 we’ve decided to push back 2.8 a few more weeks so we can bring in a few more speed optimizations, taxonomy enhancements, and new theme features. We also need to figure out which jazz musician to name the release after.

Thank a Plugin Developer Day

WordPress by itself is very simple — what makes it compelling for most of its users is the wide array of plugins (and themes) available for WP. The average WordPress blog has about 5 plugins installed! Today we just passed 4,000 plugins available in our plugin directory. (Which is also embedded into everyone’s WordPress 2.7 or above.)

I declare January 28th our official “Thank a Plugin Developer” day. To celebrate take a look at the plugins you use and love, visit the author’s site, find their contact form, and drop them a note thanking them. (Or Paypal!) Look for the links in the plugin directory to “author homepage” and also to donate directly if they’ve specified a Paypal address.

Thank you to everyone who has ever written a plugin for WordPress, and here’s to the next four thousand.

WordPress.tv

Today we’ve switched on WordPress.tv, your visual resource for all things WordPress.

On WordPress.tv, you’ll find tutorials for both WordPress self-installs and WordPress.com to help you get blogging fast and hassle-free. We’ve kicked things off with the basics — now you can shape what comes next. Just drop us a line and let us know what you’d like to see added.

WordPress.tv is also now the place to find all that awesome WordCamp footage that was floating around the web without a home. See the presentations you missed and get a peek at behind-the-scenes action. We call it WordCampTV.

You’ll also find slideshows of presentations made by WordPress gurus, plus interviews I’ve done with the media and fellow bloggers.

I hope you’ll consider WordPress.tv not just a support resource, but also a place to hang out and keep up with all the geeky goodness going on in the WordPress community. Tune in regularly for fresh content and updates to the WordPress.tv blog. Lots more is on the way.

Prioritizing Features for WordPress 2.8

Everyone knows by now that WordPress 2.7 is packed with new features. Now that it’s available (almost 600,000 downloads as I write this!), it’s time to start working on 2.8. There were dozens of things that got tabled during 2.7 due to time constraints, and there are a lot of high-rated features in the Ideas forum, so there are a lot of potential features under consideration.

Right now, the lead developers are thinking the top priorities for 2.8 will be widget management, theme browser/installer and performance upgrades. The rest of the development time will be taken up with bug tickets and additional features/enhancements from a prioritized list. To that end, we’ve posted a new survey for you to help us prioritize features for 2.8. The list pulls from the developers’ “2.7 leftovers” list as well as the most popular features from the Ideas forum. Just rank each feature and tell us your top pick (up to three). You also have the option of adding comments or additional suggestions, but this is not mandatory. For your response to count, you must rank all of the features in the list. The survey has only one page.

Note that media features are not included in this list as we will be posting a separate survey for media-specific features soon.

Cast your votes any time this week, but as always the sooner the better. This survey will close at noon on December 31, 2008 UTC.

In the new year, we will be reviving scheduled IRC developer chats, where the lead developers will discuss the week’s progress on feature development, providing opportunities for people to ask questions or make suggestions. These will be held early in the day on Wednesdays (U.S. Wednesday), and the specific time will be posted here on the development blog once it’s been finalized.

As a related aside, we spent a significant amount of time during 2.7 development sifting through Trac tickets that really shouldn’t have been there. Feature ideas and requests do not belong in Trac, they belong in the Ideas forum. Please reserve Trac for reporting bugs and things that need fixing (typos, code enhancements, etc.). If you are asking for a new UI, a new feature, or a new approach to coding something, that’s not an enhancement, it’s a new feature. New features will be entered into Trac by developers once it has been determined that the feature should be included in core. To help speed up development, moving forward we will close Trac tickets that are actually feature requests, with the comment that they should be posted in the Ideas forum instead. Please help the developers maximize their time by following this guideline.

Thanks for your help!