The final step involves a bit of modification to the xml.php file within the NextGEN – MonoSlideshow plugin. See the modified code below. First add the followImageLinks=’true’ attribute in the album configuration on line 43. Create a variable for your link as we have in line 62 which calls the custom field for your hyperlink that you created within the Custom Fields plugin using the nggcf_get_field function. Finally, add your link to the returned array in line 66.

Here is the complete modified xml.php file:

Source code

<?php
 
if(preg_match('#' . basename(__FILE__) . '#', $_SERVER['PHP_SELF'])) { die('You are not allowed to call this page directly.'); }
 
global $wpdb;
 
$ngg_options  = get_option ('ngg_options');
$options      = get_option ('monoslideshow');
$siteurl      = get_option ('siteurl');
 
// get the gallery id
$galleryID = (int) $_GET['gid'];
 
// check if someone send the preset value
$preset = ( isset($_GET['preset']) ) ? $_GET['preset'] : '';
 
// get the pictures
if ($galleryID == 0) {
	$pictures = $wpdb->get_results("SELECT t.*, tt.* FROM $wpdb->nggallery AS t INNER JOIN $wpdb->nggpictures AS tt ON t.gid = tt.galleryid WHERE tt.exclude != 1 ORDER BY tt.{$ngg_options['galSort']} {$ngg_options['galSortDir']} ");
} else {
	$pictures = $wpdb->get_results("SELECT t.*, tt.* FROM $wpdb->nggallery AS t INNER JOIN $wpdb->nggpictures AS tt ON t.gid = tt.galleryid WHERE t.gid = '$galleryID' AND tt.exclude != 1 ORDER BY tt.{$ngg_options['galSort']} {$ngg_options['galSortDir']} ");
}
// read some default options
$delay = (int) $options['delay'];
$randomize = ($options['randomize']) ? 'true' : 'false';
$scaleMode = $options['scaleMode'];
$kenBurnsMode = $options['kenBurnsMode'];
$onAlbumEnd = $options['onAlbumEnd'];
$controls = ($options['controls']) ? 'normal' : 'none';
$backgroundColor = ($options['bgTransparent'] == true) ? 'transparent' : '#' . $options['backgroundColor'];
$displayMode  = $options['displayMode'];
$config = false;
 
//look for a preset file
if ( !empty($preset) )
    $config =  nggMonoslideshow::read_preset( $preset );
 
// Create XML output
header('Content-Type: text/xml; charset=' . get_option('blog_charset'), true);
echo '<?xml version="1.0" encoding="' . get_option('blog_charset') . '"?'.'>';
echo "<album>\n";
if ($config === false) {
echo "\t<configuration followImageLinks='true' onAlbumEnd='$onAlbumEnd' fullScreenScaleMode='$scaleMode' scaleMode='$scaleMode' backgroundColor='$backgroundColor' delay='$delay' randomize='$randomize'>\n";echo "\t\t<caption displayMode='$displayMode' />\n";
echo "\t\t<controller type='$controls' />\n";
echo "\t\t<transition kenBurnsMode='$kenBurnsMode' />\n";
echo "\t</configuration>\n";
} else
echo "\t$config\n";
echo "\t<contents>\n";
 
if (is_array ($pictures)){
	foreach ($pictures as $picture) {
 
        $description = htmlspecialchars ( strip_tags( stripslashes( nggGallery::i18n($picture->description) ) ) , ENT_QUOTES );
 
        if (!empty($picture->alttext))
            $title = stripslashes( htmlspecialchars (nggGallery::i18n($picture->alttext) , ENT_QUOTES) );
        else
            $title = $picture->filename;
 
        $link = nggcf_get_field($picture->pid, 'ImageLinksTo');        $path = $siteurl . '/' . $picture->path . '/' . $picture->filename;
        $thumbnail = $siteurl . '/' . $picture->path . '/thumbs/thumbs_' . $picture->filename;   
 
        echo "\t\t<image id='$picture->pid' source='$path' title='$title' link='$link' description='$description' thumbnail='$thumbnail' />\n";	}
}
 
echo "	</contents>\n";
echo "</album>\n";
 
?>

Step-by-step Instructions

1. Install the NextGen Gallery plugin.  Create a gallery.

2. Install the NextGen – MonoSlideshow plugin.

3.  Install the NextGEN Gallery Custom Fields plugin

4.  Add a custom field to the NGG Custom Fields plugin.  Click on NGG Custom Fields > Image Custom Fields.  Add a field called ImageLinksTo.  Check the checkbox to include the field in your gallery or galleries.  Field type is text input.

5.  Replace the [wordpress dir]/wp-content/plugins/nextgen-monoslideshow/xml.php file contents with the code that we provide above.  Upload via FTP.

6.  Go back to your NGG custom gallery and edit it.  Add URLs to your ImageLinksTo field.  See graphic.

7.  Done.  Refresh page and view gallery with clickable images.

Big Import

In this project, we wrote custom VBA code in Excel to parse and format the data for over 10,000 products for import into a BigCommerce site from an Excel spreadsheet.
For almost all of these products, we had to first download a product image, rename the file, then upload it to the BigCommerce server. Modification of the Excel data was hardly trivial: some fields had to be scrubbed of a number of special characters, and we had to build compatible URLs for all the images. Our client was thrilled: for several days of our work, we saved them weeks of tedious manual product entry.

BigCommerce Export to Google Adwords

Here we built an Excel workbook with VBA to reformat data from our client’s BigCommerce-based site. Our utility turned the data into a compatible Google AdWords CSV feed with “AdGroup” records, “Ad” records, and 4 “keyword” records for each product. Imagine trying to manually build all this information in Excel for hundreds or thousands of products – it would be a HUGE task. Our cost effective script saved our client an substantial amount of work.

BigCommerce Export for Order Fulfillment

This client’s BigCommerce site sells products for another company and they need to regularly send that company a fulfillment order.

We provided a utility that automates the creation of a fulfillment order to be sent to a supplier. We used the BigCommerce API to export the data which is in XML format. We then wrote macro code which took care of all of the grunt work of converting the XML to neat
column delineated data for individual orders on a BigCommerce site.

Score 3 for 3 in the time-saving department! Now its just a few clicks to send the data on its way.

Need Help with Big Commerce?

Get in touch – we are glad to quote you for projects like this which will save you time and money.

Their existing procedure involved several steps:

(1) importing an order file from each of several sources into an Excel 2004 spreadsheet
(2) sorting to find duplicate addresses
(3) generating a new worksheet with orders combined from all sources
(4) constructing new columns such as the total cost and a barcode
(5) saving the resulting spreadsheet as a source for mail merges in Word 2004 to generate invoices and labels

The procedure was partially automated — they already had a template spreadsheet with formulas for the new columns, along with some VBA macros. Our task was to refine the process and make it more robust.

We first developed a VBA macro to automate the entire process. Under the new scheme, we store the order
files with fixed names, in a folder based on the date. We then run this new macro which does all the necessary importing, sorting, combining and saving.

Here are some specific changes and improvements that we implemented:

(1) Data Validation: The existing spreadsheet imported zip codes as numbers, with the result that leading zeroes were
dropped. The new macro explicitly imports the zip code column as text.

(2) Code Optimization: The existing spreadsheet had formulas to build the new columns, presuming a certain maximum
number of rows. The new macro builds the needed columns for just as many rows as are actually present.

(3) Error Trapping: Some orders are paid with PayPal and have authorization but no transaction ID. If the client didn’t catch this omission, he doesn’t get paid for that order. The new macro counts the PayPal authorizations and transaction IDs, with the transaction ID count highlighted in red if it doesn’t match the authorization count.

(4) Error Trapping: For international orders, the country name is found by looking up the country code in a table. We added an error trap to the macro in case the country code is not found.

(5) The existing procedure involved saving the worksheet as tab-delimited text to generate a file to be uploaded to mark orders as shipped. This worked fine except that the last line was missing the end-of-line character (CR). He had to edit the file manually and insert a CR at the end, or else the last line wouldn’t be processed. The new macro solves this problem by building the file directly with VBA file I/O.