Whilst building my latest affiliate store for console bundles using Datafeed Studio I decided to add some new features to the application.

The main new feature is cache support across all the affiliate sites and pages created by Datafeed Studio. By setting the $CACHE_TIME_IN_SECONDS value in the main configuration file you can specify how long a page should be cached for. Personally for my sites I have set it to the number of seconds in a day.

Once a page is cached, any subsequent visit to the page will require no database calls whatsoever until the cache time has expired.

That’s not all in the performance stakes though. From v2.1 the SQL used when displaying categories and products has been optimised. Previously when displaying a page with say ten products, this would have required 21 (yes, twenty-one!) database calls. One for the initial product selection, and then two more for each product to gather additional meta information about the product.

From v2.1 a similar page will require just one database call. This, coupled with the new caching feature, should result in much faster response times for your customers.

Apart from that, there are a few presentation changes with themes. First, store themes have a new ‘Buy Now’ button which should increase conversions, secondly themes now include both the main stye.css file and the local CSS file.

Previously the local style.css was a complete copy of the main style.css file and this was the only CSS file included in a page view.

From this version pages load both the main style.css and the local style.css, with the local style.css being empty by default, but loaded after the main style.css so you can override or apply any new customisations you want to the presentation.

This is handy if you have several affiliate sites all using the same Datafeed Studio database and theme type as you can make a “global” change by changing the main style.css file, without having to update each of your sites individually.

For full details of all the changes in v2.1, see the ChangeLog within the Datafeed Studio distribution.

You can download v2.1 here.

Upgrade Notes : If you are upgrading an existing installation note that for this release you must run the patch.php command-line tool located in admin/bin to upgrade your database (alternatively you can import the patch.sql file manually into your MySQL version or using a tool such as phpMyAdmin).

Ch-ch-ch-changes!

From V2 there is no PHP code in the Datafeed Studio templates!

This should be great news for template designers, as it is now much easier to modify the templates in an HTML editor of your choice without worrying about accidentally altering the obtrusive PHP code.

Technically Datafeed Studio now uses the great PHPTAL template system that gently nudges you down the path of W3C compliant HTML/XHTML designs. For more information see the PHPTAL manual if you are thinking of getting down’n'dirty with the Datafeed Studio templates.

It’s all pretty straight-forward, although it might take a few minutes to understand the changes from previous releases. Essentially, for store and price compare sites, the main layout for a page is now defined in the ‘layout.html’ file within each theme.

Every page within a theme will use that layout, so you can make major structural changes to the theme just by editing that file (in combination with purely presentational changes in the accompanying style.css file).

In the main layout.html file there is one special “div” element with an ID of “content”. The content of this element will be magically replaced depending on what page is being viewed, be it a product page, a content page, blog post, etc.

Each of these pages (product, content, blog, etc.) still has their own specific page which you can customise to your needs, but you only have to worry about that particular context, not the overall layout, as that is “inherited” from the main layout.html.

Enough of the positives, we need some negatives!

There’s only one really, and that is that any custom templates created in earlier versions are no longer compatible. They will have to be migrated to use the new template system. Unfortunately this step was unavoidable, and could mean some short-term pain, for long-term gain.

If you have developed some custom Datafeed Studio templates and would like help migrating them contact me and I’ll do all I can to help. From studying the already migrated themes that come bundled with Datafeed Studio you should be able to understand what’s required, but feel free to contact me if you run into problems.

V2.0 is available to download from here.

If you are upgrading, I strongly recommend moving your existing “templates” folder to “templates_old” prior to unzipping otherwise you will have both old and new template files in your theme folders – which I guarantee will lead to rapid hair loss.

It might only be a point release, but today’s release of v1.7.1 of Datafeed Studio is quite a major overhaul of the back-end administration UI, improving the usability and look’n'feel of the whole operation.

As well as the swish new UI, there are now integrated help links within the application that replace the need for the user manual (yes, there actually _was_ a user manual. You didn’t read it either, did you?).

The gory details for 1.7.1 :

• improved usability and look and feel of admin site
• default CSS for the store modern theme now uses a more neutral blue style rather than the old ‘Indiana Jones’ style brown
• integrated help system into the admin site, the old HTML manual is now deprecated
• fixed bug displaying content pages in side-menu using IE

Download it from here or click here to take it for a test drive.

Today sees the release of v1.7 of Datafeed Studio.

“So what?” you cry.

Well, what about these killer features?

• the ability to add static content pages to your stores with the built-in WYSIWYG editor
• the ability to add a blog to your sites to keep your visitors informed with the latest news about your product niche / your site.

In effect, Datafeed Studio has morphed into a specialised affiliate CMS, combining datafeed driven stores with your unique content. It doesn’t get much better, does it?

The full changelog :

• new feature – add a blog to your stores
• new feature – add pages of content to your stores
• added support for horizontal menu in default store theme
• fixed various problems when installing in a subfolder of a domain
• fixed bug displaying products with SEO friendly URLs when using default store theme

Download it here.

I’m very pleased to announce the release of v1.6.5 of Datafeed Studio.

This release comes with a major new feature – a GUI Settings editor for your sites, no more editing the PHP configuration files in order to get the site you want.

To try out this new feature, log into the demo (http://olaxi.com/admin, username : demo, password : demo) and click on the ‘Setttings‘ action next to the registered site name.

(Remember that this is a read-only demo, any attempts to update values will result in warnings).

The full changelog for v1.6.5 :

• new GUI editor for site settings
• standalone ‘Price Compare’ pages can now only be created via the ‘PC Pages’ tab, not from the site screen
• removed PUBLIC_URL from site configuration settings, this will now be taken from the registered site URL
• removed PHP short tags from theme editor for improved compatibility with different hosts
• renamed MyKey to ‘Product Key’ in product display page for consistency

I hope you like this new feature. Note, if you really still want to edit the configuration files manually, this is still possible,the configuration files still live in the site_configs folder as usual.

The latest release is available to download from here.

Yep – a new release!

This is a mix of some fairly minor bug fixes and usability improvements on the admin side.

The most useful addition are two new datafeed filters, that allow you to Prepend or Append your own content strings to any field in a feed, e.g. adding your own suffix to an affiliate URL.

• added two new filters, prepend and append, that can prefix or suffix field data with content of your choice
• added status message when filters are added / updated
• fixed a big with the BuyAt stock checker that may have prevented other filters from working
• added convenient accesskeys for the admin site tabs, based on the numeric position of the tab, e.g. 1 = Home, 2 = Datafeeds, etc.
• added a test for the presence of the MySQLi extension during installation
• now dynamically filters site themes based on the type of site selected in New/Edit Site screen
• if you create a dynamic product category from your search results, any SQL limit clause in the generated SQL query is now automatically removed as it could previously break pagination of dynamic products
• the products shown on store home pages can now be generated by a single tag, display_home_category(). This will now display manual / dynamic categories (formerly only manual were allowed), or if the store $HOME_CATEGORY is unset, or set to ‘random’, a random selection of products will be displayed from your database.
• fixed Case 48 – extra spaces in user queries were returning no results
• fixed Case 24 – if a product name is overridden, it now correctly shows in the “HOT DEAL” text of the Store modern theme

Phew…

It is available to download from here.

Information for existing Datafeed Studio owners – there are no database changes required for this release.

To upgrade it is recommended to backup your existing installation folder and extract this new version over it. You may then wish to copy back over any custom template modifications you made in previous releases (or simply copy the old “templates” folder completely).

A bug fix release recommended for all users.

New in v1.6.3

• fixed “Search results for” string on store default search results page, was missing product term
• increased security on search queries to prevent possible XSS attacks
• increased security on admin/bin/patch.php to disallow running from web environment
• support for tab-separated feeds (parser separator of ‘\t’ without the quotes)
• disallow index.php?id= URLs being indexed via robots.txt
• fixed store modern theme, would use value of last product title in the list as the text for the product review heading
• updated .htaccess to allow existing files to bypass index.php routing

Available to download now.

If you are upgrading remember to backup your templates folder before extracting the new version if you want to retain any custom template changes you may have made.

Update : This post is really old now – and even though the information below will still work, the far easier way is to use the WordPress plugin that Datafeed Studio now comes with, which allows you add a price compare box to your Wordpress posts or pages as simply as writing :

[ds query='pleo']

anywhere within the page/post content.

Sometimes you may want to access product information contained within your affiliate datafeeds outside of a Datafeed Studio created site, e.g. inside a WordPress blog.

This post will show you how to easily achieve this if your WordPress site (or similar) resides on the same physical server as your Datafeed Studio installation. To illustrate what is possible I’ve quickly created a new WordPress site for the Pleo Toy. This WordPress theme has three columns.

The middle column is the one we are interested in – it shows all the current prices and retailers of the Pleo according to the data held in our Datafeed Studio installation.

How does this work?

Well, as our site is on the same server as Datafeed Studio we just hook into the datafeed functions with the following few lines of code :

Just paste these into the appropriate file of your WordPress theme and you can get a similar list of product prices, such as these Pleo Prices embedded in your blog or web site.

Neat, huh?

All you need to change above is :

$DS_LIB – the path to the Datafeed Studio installation “lib” folder on your server

$PUBLIC_URL – the main URL of your public Datafeed Studio site

and, of course, you want to change the product name to be something other than ‘pleo’ in the line containing the “get_products” function call

That’s it.

A future article will show a similar method integrating with WordPress custom fields to dynamically do a product price compare within WordPress.

Quick Update – the latest version (V1.6.2) of Datafeed Studio now comes with built-in datafeed parsers for the Paid On Results and ShareASale affiliate networks.

This now means that Datafeed Studio supports feeds from five different affiliate networks. Full list :

• Affiliate Window
• BuyAt
• Paid on Results
• Share A Sale
• Trade Doubler

If you have any feedback on these parsers, or have a suggestion for a new one, please don’t hesitate to contact me.

Don’t forget you are not limited to this list, you can easily create your own within the application by specifying the mapping of internal database fields to that of the CSV file you want to parse.

Datafeed Studio now supports SEO friendly URLs for your product categories and products.

Previously, Datafeed Studio URLs were pretty ugly :

http://example.com/display_product.php?mykey=123_123456789


Now, if you enable the SEO_FRIENDLY_URLS option in the configuration (enabled by default) you will get product URLs in the form :

http://example.com/123_123456789.html


Hmm…I suppose that is a slight improvement I hear you say, but wouldn’t it be great if I could choose the value of the URL myself.

Well, now you can!

The latest Datafeed Studio release has “slug” support. Every product in your database can now have an unique slug (or path or permalink, call it what you will), so you can finally have URLs of your choosing, e.g.

http://example.com/my-cool-product.html

What’s more, slug support has been added to categories, so instead of :

http://example.com/show_category.php?catid=24

You now get :

http://example.com/category-bouncy-castles

To demonstrate the new URL structure I’ve created a new baby car seat site, check it out to see the new SEO friendly URLs in action.

If you still prefer the non-SEO friendly URLs just set the SEO_FRIENDLY_URLS option to zero (this option can also be set in the site specific configuration files so you can enable/disable it on a per site basis).