All Posts by Eric Busch

New “Media Library Filter” plugin released today

When your WordPress site starts to grow and you have lots of images in your library from Posts, Pages, Products and other WordPress content types, filtering the the media in your library becomes very difficult.

I thought for sure there would be a plugin available that would enable filtering of the media in my Media Library… but there wasn’t much. What I did find was a post on StackExchange from 2013 with a quick solution. So I spent a couple of days and put together the Media Library Filter plugin.

banner-1544x500

The Media Library Filter plugin allows you to filter the media in your library by taxonomy or term.

A taxonomy would be the type of category. For example some taxonomies might be Blog Categories, Product Categories, Post Tags, etc.

A term would be the name of an item in the category. For example the taxonomy Product Categories might contain the terms “Rock Climbing Shoes” and “Rock Climbing Helmets”.

If you have a suggestion or way to improve, please let us know.

Download the plugin

Enjoy!

Exclude duplicates based on Merchant ID

We’ve added a new option to the Exclude Duplicates filter in the Factory search form. Now you can also exclude duplicates based on the same merchant ID. This is useful if you want to create a list of the same product from multiple merchants without repeating any one merchant.

exclude-duplicates-by-merchant-id

Speeding up large Datafeedr + WooCommerce stores

I wanted to share a few links from Dave Hilditch over at http://www.affiliatewebdesigners.com/. He’s shared some tips on how to optimize for large, 100K+ product stores on WooCommerce. Check them out here:

Hopefully these help some folks struggling with building huge Datafeedr/WooCommerce stores.

30 WooCommerce Integration is Here!

You spoke, we listened! We’ve now integrated WooCommerce (the leading ecommerce platform for WordPress) with our massive database of 250 million affiliate products to give you a simple yet powerful affiliate store building solution.

What does this mean to you?

  • Automatic product updates
  • One fee, unlimited stores
  • Unlimited products per store
  • Product ratings and reviews
  • Responsive layouts
  • Faceted search
  • Easy-to-use interface in your WordPress admin area
  • Configurable update settings
  • Hooks & filters to customize product data
  • More end-user browsing features
  • More search query options
  • More product fields

… and the list goes on!

Learn how to get started or SIGN UP NOW!

Questions?

Feel free to ask your questions below or contact us.

30 Is the Datafeedr API Right for You?

A few weeks ago we released our API. Since then there has been a bit of confusion regarding whether you should use the Datafeedr Factory (http://www.datafeedr.com) or the Datafeedr API (https://v4.datafeedr.com) when building your store. I’d like to clear up that confusion in this post.

The API is not the next version of Datafeedr, despite “v4” appearing in the URL. The API is another way to build your store, not the new way.

A brief overview of the Factory and the API

The Datafeedr Factory allows users to search our product database, organize products returned from your searches into categories, and then import your products and categories (ie. your store) into your WordPress blog using the Datafeedr plugin. The plugin displays the products on your blog in a nice layout. You do not need to write any code in order to use the Datafeedr Factory and plugin.

The Datafeedr API (Application Programming Interface) allows users to query our product database programmatically (ie. by writing programming code). Each query is referred to as an API Request, a request made to the API which returns products as an array. The API does not handle anything other than allowing you to query the database and returning products. It does not insert products into your database or display them on your website. This functionality must be handled separately by a developer.

Should I use the API?

There are 2 reasons why you might choose the API over using the Factory:

  1. You are a developer – If you are a developer/programmer and want access to the product database but want to have control over what you do with the product data (ex. import into custom database, integrate into a mobile app, etc…) then the API is right for you.
  2. You want to use a third party integration – You don’t have to be a developer in order to use the API. We’ve partnered with other developers who have done the work for you. If you want to use a plugin or script that another developer has created (which connects to the Datafeedr API), then you’ll need the Datafeedr API. In most cases you’ll simply need your API Access ID and Secret Key (provided to you after you sign up for the API) to input into the integration software you have chosen. You can find all current integrations here: https://v4.datafeedr.com/integrations

Those 2 reasons don’t apply to me

If neither of the above 2 reasons apply to you, then the Datafeedr Factory is your best choice. The Datafeedr Factory makes it easy to create a beautiful store which seamlessly integrates with your WordPress blog. No programming required!

Still confused?

I hope this helps clear up any confusion about the choice between the Factory and the API. If you have any questions, please comment below.

2 The Datafeedr API Now in Beta

We’re happy to announce that our new API is now in beta and ready for release. With the API you can now access all of our product data (roughly 250 million products) through API requests.

https://v4.datafeedr.com/

If you’re a developer and want to create a plugin or app or software which integrates with the Datafeedr API, be sure to check out our partner program. Already third party developers are writing amazing scripts that integrate with the API and those will be promoted on the API site once they are live.

Feel free to posts your API questions as comments in this blog post.

12 Datafeedr is 5!

bday5Happy Birthday Datafeedr!

Five years ago today we launched datafeedr.com. I can’t believe it’s been 5 years already. I remember the night we launched. We replaced the “Coming soon…” message with our bare bones sales page. We sent out a few emails to our mailing lists. But a watched pot never boils, so I went out that night with my wife and friends. To my surprise, we had our first few members sign up before I even returned home. Some of those members are still with us to this day!

We should say thank you to all of our members for pushing us to make a better product. We listen to all of your feedback. Although we might not implement every feature request right away, we try to get at the essence of the feature request and deliver something that solves more than just 1 issue.

Since we launched, we’ve developed 3 significant versions of the Factory and plugin. We went from supporting 6 affiliate networks to 31. We started with about 450 merchants… now we support over 10,000. And if memory serves correctly, I believe we launched with less than 3 million products in our database. Now we have over 250 million products (not including Amazon’s products).

But in technology, as with most things in life, living in the past is not going to drive us forward. While it’s interesting to look at how far we’ve come, I rarely think of those things. I am constantly consumed with where we are going.

So where are we going?

We started development of Datafeedr right around the time Apple released the first iPhone. Since then there’s been a huge push in the mobile space as well as the tablet space. Browsing the web means something entirely different than it did 5 years ago. Better browser support for HTML5, CSS3 and JavaScript has turned websites into rich applications.

We need to catch up and keep up with all of these new technologies.

That’s why this month we plan on releasing our new API. We hope with the release of the API we (and you) can start to take advantage of all of the new technology and platforms that are powering the web and mobile applications. I don’t want to say too much about its potential right now but I can tell you we’re really excited about it! We’ll have much more to share about the API as we get closer to launching it.

If you are interested in developing applications using the new API, please let us know in a comment below.

Here’s to another 5 years!

Thanks,
Eric

Scheduled Maintenance (2013-04-12 9:00am GMT)

On Friday morning, April 12th, at 9am GMT (5am EST) we will be doing some scheduled maintenance in the Factory. We expect the maintenance to take roughly 15-20 minutes.

During this time, the Factory will be unavailable.

If you have any questions, please don’t hesitate to ask.

Thanks,
Eric

4 Create your own WordPress shortcode for Permalinks

I cringe every time I see a link in a blog post that is an absolute URL to other content on the same site. Here’s an example of what I mean:

In that example post you see a link to another page in my blog.

But what happens when you edit the slug of the post? The link will break.

Or what happens if you move your blog from /blog to /news? The link will break.

Or even worse, what happens if you change the domain where the content is hosted from http://www.mysite.com to http://blog.mysite.com? The link will break.

That’s why I cringe every time I see a link with an absolute URL to another page on the same site.

What’s the solution? Shortcodes.

Here’s an example of how to programmatically add links to your posts without being susceptible to the problems I mentioned above. The following code can be added to your theme’s functions.php file or to a custom plugin you might have.

After you add that code to your site, here’s how you can use it when writing a blog post or page.

To get the link to another post on your site all you need is the ID of the post you want to link to. Then in your post you would do something like this:

Now my link’s URL will be generated from the database and no matter how much we edit the other post’s slug or path, the correct URL will always appear in this link.

What if you want to avoid creating the <a href="">...</a> HTML code? That’s easy. Just do this:

Now when the post is rendered, the <a> tag will automatically be created and the title of the post will show up.

If you want to control the title of the link, you can do this:

Let me provide one last example to clear up any confusion… Let’s say you wrote a post on your blog. The post you wrote is titled Hello, World!, it has a slug of hello-world and the post has the ID of 33.

Here’s what the shortcode would look like in your posts and what would be returned:

Hope this helps future-proof the links in your blog posts.