What we don’t have (still) is a name.. This is turning into a nightmare.
We’ve tried all sorts of “name generators” and domain name tools.. still stuck..
We’ll let you know when we sort this out..
Note: this is NOT procrastination. More like “writer’s block’..
AliDropship pulled a master-stroke last weekend: they offered us FREE HOSTING for a year! (Try joining their mailing list and watch out for the offers)
That was enough for us to get off the fence and buy-in.
So, for the usual price of $89.95 (£72), we got the plugin and free hosting.. Result! (we could have save 15% if we didn’t take the hosting, by using code: STARTER15)
So we now have a hosting account for this project that doesn’t rely on our usual “unlimited” hosting (slow).
AliDropship have also agreed to set this up for us. For free.
All we need now is a name for the shop.. which will also be the domain name.
And that’s trickier than you think. Most of the ones we thought of are already taken..
Oberlo have videos and tutorials on this subject, so we’ll take another look at those (I think Wholesale Ted may have something as well.)
So, we’ll get back to you when we have a domain name.
Then, it’s just a case of setting the site up, picking a niche, and some products..
And then comes the real work: Marketing…
There are two main ways to set up a dropshipping store:
Shopify/Oberlo, or WordPress/AliDropship.
We have chosen to use the second option, because
1. we already have hosting (£4/month!) – if you don’t, try AliDropship hosting..
2. we are familiar with domain registration (GoDaddy)
3. we already know our way around WordPress ( we run several WP sites )
4. the AliDropship plugin is $75 (one-off payment, with discount)
The alternative (which we think is better suited for beginners or non-techies, is:
1. £29/month for a shopify account
2. £13 a year for a domain name
3. Oberlo (free up to 50 sales)
** please note: within the WordPress/AliDropship route, there are two options:
For the sake of simplicity, and also because we’ve never used WooCommerce before, we’ve decided to use the Non-Woo version.
This may come back to bite us later, and it also means we are stuck with the themes that come with the non-woo plugin, but it should reduce the learning curve a bit.
BOTH versions of the plugin are included in the one-off $75 price.. don’t forget to use the “STARTER15” discount code..
Actually, you can save yourself a LOT of effort if you buy a custom-built store direct from AliDropship..
There are two main routes we can take:
For reasons I will explain more fully later, I am going to be going the AliDropship way..
This means I need to purchase the AliDropship plugin, which usually costs $89, but I’ve found a discount code: STARTER15, which knocks 15% off that. ($75).
Here’s the link to the AliDropship site: Get the AliDropship plugin for 15% off (don’t forget to apply the STARTER15 discount code)
I’ll let you know how I get on with this.. and why I picked this option.
My hosting company finally got around to enabling Let’s Encrypt SSL certificates. I’d been nagging for at least a year.
I managed to move ALL my sites to SSL for free (apart from the ones I’d already bought certificates for), in one morning.
All I did was enable Let’s Encrypt for each site in turn, in PLESK, take the default options, and then use the “Really Simple SSL” WordPress plugin.
That’s it. Sorted. For Free. If your hosting company doesn’t support Let’s Encrypt, MOVE.
REMEMBER: Google promotes encrypted sites above others in search results. Chrome marks unencrypted sites as “Not secure”. You don’t want that.
I recently needed to upgrade an existing wordpress site to SSL/https:.
This was made more complicated by the fact that it was on a shared hosting server, AND used cloudflare CDN.
This should have been simple:
Except it didn’t work.
I couldn’t get it to reliably use https:// or redirect http://website.com or http://www.website.com
Eventually, after raising tickets with Cloudflare and The hosting company, I found a plugin called “Really Simple SSL”.
This configured wordpress to use https AND rewrote the htaccess file to do the redirects. In the end I had to manually edit the file as my htaccess file is secured, but at least they gave me the code to do that.
I left the cloudflare CDN SSL setting as “flexible”, as anything else caused problems.
The best way to make this work is to use the Jetpack plugin, and enable the post-by-email feature.
That gives you an e-mail address where anything it receives is published as a blog post.
However, I found I couldn’t get it to work until I switched from ithemes security to wordfence. Apparently, it’s a known problem: ithemes security blocks xmlrpc, so post-by-email isn’t available..
I’ve just uploaded a new version of Text File Widget (2.0).
This addresses the php v5.0 constructor issue – WordPress 4.3 will throw a warning if it encounters php v4.0 contructors.
Thanks to Remy Corson for providing a working example of the correct code. Not sure why I didn’t use that in the first place..
Anyway, I’ve tested it on WordPress 4.3 Beta 4, and it worked fine – no warnings. Rah!