BlinkWeb Affiliate Program

I just discovered this one after signing up for a free web site space on BlinkWeb.

After you're signed up (free) and logged in then surf on over here where it says this:

Sign up below to get your unique Blinkweb affiliate link and start earning passive, residual income promoting Blinkweb. By promoting BlinkWeb, you'll earn a very nice recurring commission of 20%, 25%, or 30% per sale, depending on the level of overall sales you have achieved. Click here to learn how to increase your commission percentage.

If someone signs up for a free BlinkWeb account and decides to purchase a domain or hosting with them, you'll instantly earn 20%, 25%, or 30% of the price they paid for the subscription. You will also earn a commission for any backend sales made via Blinkweb. You will be paid every month for the entire lifetime of the customer! Obviously, there is the potential to earn ALOT of money via the Blinkweb affiliate program.

Commissions will be paid via PayPal on the 21st of each month, for the previous month's earnings. Commissions will be paid out when your total commission earned reaches $50. If your monthly commission has not reached $50, it will be carried over to the next month's commission amount.

Fill Out that Form to Become a BlinkWeb Affiliate

Handling the Temporary Internal Incoming Email Outage on Your ShiftCode GPT Site

Recently I had the chance to organize me thoughts concerning the recent internal incoming email outage affecting ShiftCode GPT sites by responding to a posted question on the ShiftCode Official Facebook Group.

Q:  The main site seems to be down and so is the e-mail client. Can anyone help please? Thank You

A:  Addressing the GPT internal incoming email outage (likely temporary) - the attitude I've taken is that since GPT site domain based internal incoming email doesn't fall into the 'mission critical' category (with me) then I've simply configured my 'From E-mail' in the ShiftCode admin panel (right side menu Main > Configure > E-mail) to a free Gmail based email address.

This assures me that I'll still get system notifications from the GPT script while also providing a viable uninterrupted 'from' email address that's reachable during the temporary email outage (once you've changed this email address field then all of your member email notifications from the system will also appear to be coming from this new email address (it's always been 'spoofing' whatever email address you poke in here))

Don't feel shy about promoting the extra temporary email address because when the built-in domain email service comes back then you can just forward the temp email account messages back to the old domain based email account

If you do decide to just stick with the free email account (Gmail, Hotmail, etc) then know that you're not losing or trading much off here. The email address is just there to provide a viable return message path as a return email address to all your GPT's system messages to the member and to provide you (the admin) with messages from the GPT script as to what's happening on your GPT (notice of withdrawals, inbox messages, etc.)

I'm quite comfortable just using my Gmail based email address for as long as the outage lasts.
Last things to consider might include:

1) notifying your members via a mass email blast (yes, the mass email function still works just fine) of the temporary email outage condition while offering up the new email address for them to white list and use for any and all near future email contact attempts to your GPT administration; and

2) if the email outage persists then slowly make a round to change (or add) the new temp email address to any affiliate network, service provider (ProxStop, etc) and payment processor accounts (PayPal, etc)
____________________

For those who are searching for true alternatives to the built-in domain email provided by ShiftCode then here's is an article that I ran across concerning free options (though I don't know how old the information in the article is still accurate):

What Should I Do Now that Google Apps Accounts Are No Longer Free? [http://lifehacker.com/.../what-should-i-do-now-that... ]

Another option is to use your own domain hosting account for email hosting only (while ShiftCode hosts the actual domain - see the MX records statement below))
If you do choose to use an alternate domain email provider then you will ultimately likely need to contact ShiftCode to make the necessary domain 'MX record' (mail exchange) changes for you (since ShiftCode IS your 'DNS' provider if your name servers are ns1.shiftcode.com, etc. - highly likely)

[Please feel free to inbox me if you're confused or need assistance with any of this (though note I am NOT ShiftCode staff) I'm almost always happy to help freely as my spare time permits]

Avoid Unintended Unnecessary Member Re-logins by Always Coding Templates Using Relative Links

In addition to being a GPT site admin, and a script coder, I'm also a site member at most all of the popular ShiftCode GPTs out there.  Occasionally I've run across a few GPTs where I've noticed an annoying problem based in the way the site admin or designer has coded links.

The symptom of this issue is where I've already logged into the site once for the session and then I click on a link on the site and it prompts me to re-login to the site.

ShiftCode sites usually have at least three ways of accessing the site.  One would be the standard (usually thought of) primary domain name (http://www.mygpt.com), the second would be the domain name without the www. (http://mygpt.com), and the third would be the ShiftCode subdomain (mygpt.shiftcode.com)  That's all fine and good but can cause problems if your links are not all standardized on your template and script coding throughout your entire site.

The re-login issue I speak of is based in the way browser cookies handle all these instances.  With cookies, www.mygpt.com  and mygpt.shiftcode.com are essentially entirely different domains thereby requiring a new cookie for each.  If a member has logged in at www.mygpt.com and then clicks on a link on your site that has been coded to go to a page at mygpt.shiftcode.com then the member will be prompted to re-login in order to see the target page.

This problem may be present on your site right now without you knowing it (and members are not likely to report this particular problem -usually  Though it does tend to reflect negatively on their overall site experience)

To check whether your site has this issue I would suggest taking the time to check each link on your site.  Simply log on to your site as a member and hover over each of the links on your site.  Your browser will show you each link's target somewhere depending upon what browser you are using.  In FireFox it will show where the link goes to in the lower left corner.  ALL of your links should be pointing to your own domain name.  If your see any links pointing to your version of mysite.shiftcode.com then those links are problem links and should be edited.

The best solution to this problem is to get in the habit of always using relative links (/members/promo.php) in code rather that what are called hard coded "fully qualified" links (http://www.mygpt.com/members/promo.php)

A good example in code would be:

<a href="/members/promo.php">Promo Codes</a>

Rather than hard coded links (bad) like:

<a href="http://www.mygpt.com/members/promo.php">Promo Codes</a>

or

<a href="http://mygpt.com/members/promo.php">Promo Codes</a>

or

<a href="mygpt.shiftcode.com/members/promo.php">Promo Codes</a>

The first (good) example will always use the same login cookie no matter how the member enters the site (as long as all your links are relative rather than fully qualified and/or hard coded.)  And the member will remain logged in for their entire visit to your site.   Simple!