$ip = $_SERVER['REMOTE_ADDR']; 

    $url = "http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20ip.location%20where%20ip%3D'{$ip}'&format=xml&env=http%3A%2F%2Fdatatables.org%2Falltables.env";
    $xml = simplexml_load_file($url, 'SimpleXMLElement', LIBXML_NOCDATA);

    // if you need to see what is coming back.. uncomment below.
    // print_r($xml);

    // store the information you want using xpath

    $country =  $xml->xpath("/query/results/Response/CountryCode");
    $city =  $xml->xpath("/query/results/Response/City");
    $lat =  $xml->xpath("/query/results/Response/Latitude");
    $long =  $xml->xpath("/query/results/Response/Longitude");

    echo "<p>" . $country[0];
    echo "<p>" . $city[0];
    echo "<p>" . $lat[0];
    echo "<p>" . $long[0];

Download: ext.edit_custom_field_by_label.zip

To use the extension, install the files in their standard locations, enable and then edit the settings (fill in your field with the appropriate field label).

If you have any problems feel free to leave a comment and I’ll help you when I can.

My wife found this site and I just spent 20 min watching the video: http://www.storyofstuff.com

If the consumption mind set of our culture troubles you.. check out the video, it’s worth watching.  I’m not sure about the validity of all the stats or claims.  A few of them seem a little over the top and might be “spun” to further the argument she is making, but with that in mind, I think there’s still space for thoughtful review of how and why “stuff” is purchased. 

The other day I was cleaning up after dinner.  As usual, the kids were performing their responsibilities of wiping the table and cleaning up the floor.  Anyone with young children will understand that keeping children focused on task, doing the job that you have asked them to do is a lot of work.  I began to think to myself, maybe I should just let the kids go outside and clean up the dinning room myself.  Why was I thinking this?  Because in reality it was easier then helping my children to do a good job.  If I had gone down this path I would have been “busy” but I think I would still be considered lazy. 

On this occasion the Lord was reminding me that laziness isn’t so much about how busy I am as about whether or not I’m taking up the responsibilities that God has given to me.  The man who lays in bed when he should be working is not lazy because he’s in bed, he’s lazy because he is ignoring his responsibility to provide for his family.  In short, laziness is about not performing your responsibilities that the Lord has given to you, NOT about your current state of activity.  If your busy, but you’re not actually fulfilling the responsibilities that God has given to you: watch you, you might actually be lazy.

I welcome you to visit the site and give feedback (use the black tab on the right side).  In the future I plan on releasing some posts on the ins and outs of the architecture of the site.

Here’s a bit of information about the site:

Simplified Safety is a company specializing in safety products and advice.  We aim to provide customers with tested, top quality safety gear and the appropriate advice to identify the products that are needed by each individual customer.  Working closely with each customer to arrive at a tailored safety solution is how we hope to set ourselves apart in the industry.  Here are a few examples of the safety products we supply: Guardrails, Skylight Protection, Lifeline Systems, Personal Protection Equipment, Harnesses, Lanyards, and more.

A couple of years back I worked for Roberts Wesleyan College, a higher educational institution that made frequent usage of the routing feature found in Excel.  One of their bright developers, Todd Andersen, has developed a plug-in to bring routing capabilities back to Excel 2007. 

I invite you to check out his routing plug-in for Excel 2007.  He offers it for reasonable price, and knowing Todd’s programming ability, I have no problem recommending it as quality plug-in that will help fix what Microsoft has broken

The function below take a datetime string (mysql formatted) and then returns the next delivery date.  The idea is that a whenever an item is submitted, it looks at the last item that was cued, get’s it’s time, and feeds it to this function to determine when the next item should be cued.  This function used the logic that items should be cued hourly between the hours of 10am and 5pm on Monday through Friday.  

This logic could easily be updated to accommodate your own needs, let me know if you find any problems or if it helps you solve a problem.

        /**
        *
        *    Description: returns the next time to cue up an item based on the logic:
        *       Every hour between 10am and 5pm, Monday - Friday
        *
        *    Example input value $latest_item = "2009-04-15 17:01:00";
        *
        *   @params $latest_item datetime string
        *
        **/

        function get_cue_time($latest_item)
        {

            $next_item = strtotime($latest_item . " + 1 hour"); 

            if ($next_item < time()) // compare to now
                $next_item = time(); // set to now

            // Before 10 am?
            if (date("H", $next_item) < 10)
            { // set to 10 am
                $next_item = mktime(10, 0, 0,
                                date("n", $next_item), date("j", $next_item), date("Y", $next_item));
            }                

            // After 5pm?
            if (date("H", $next_item) > 17)
            { // set to 10am the next day
                $next_item = mktime(10, 0, 0,
                                date("n", $next_item), date("j", $next_item) + 1, date("Y", $next_item));
            }

            // Saturday Check
            if (date("N", $next_item) == 6)
            { // set to 10am Monday
                $next_item = mktime(10, 0, 0,
                                date("n", $next_item), date("j", $next_item) + 2, date("Y", $next_item));

            }

            // Sunday Check
            if (date("N", $next_item) == 7)
            { // set to 10am Monday
                $next_item = mktime(10, 0, 0,
                                date("n", $next_item), date("j", $next_item) + 1, date("Y", $next_item));

            }

            return date('Y-m-d H:i:s', $next_item);
        }
        

EECommerce is trying to make it possible to have the entire user/developer experience defined within EE.

The goal of the module is to port everything necessary to have a seamless shopping cart experience without ever leaving Expression Engine.  While that was not necessarily what I was looking for in merging the two systems together, there is a lot of potential in this approach as it will mean that the designer/develop does not have to mess with Magento’s somewhat confusing templating system.  Their goal is to make it so that you can define your entire store in EE templates, using the plug-in tags to harness Magento’s inherent functionality.  Of course you would still access Magento’s backend (e.g. product entry, order management) directly, but the actual user experience would be defined in Expression Engine.

EECommerce will be a complete encapsulation of the Magento API.. along with several extensions.

EECommerce’s tag system will encompass everything that can be done through Magento’s API and more.  This is by no means just a subset of Magneto functionality that is being brought into EE.  Far from being a subset, they will actually be extending the API in several ways that can be used with or without Expression Engine (as a developer I like this).

PHP UK seems to have passion for the project and a desire to garner community feedback.

For my own part, these guys drove a couple of hours to meet up with me at my business headquarters.  The drove up and listened as I explained the level of user integration that I was looking for between the two systems.  I laid out my architecture and they responded with what they believed their module would be able to accomplish.  They also assured me that they would talk to their developers and give me a better idea of when I might expect to see and beta test some of the features that I need to have developed for a forthcoming web site that I’m developing.

EECommerce was a bit more undeveloped than I might have hoped

I was hoping to see EECommerce a bit more developed when I met up with PHP UK.  For sure, they showed me that the module was working “in principal” but it seems that there are many bugs to get worked through on a bridge that is this involved.  Although they are hopeful to have something a bit more polished by some of the upcoming MAGE:Camp it seems as though they will have their work cut out for them.  In short, don’t plan on using this module in your ecommerce project that needs to be deployed next month.

A Word About Price

Clearly some of the biggest reaction in the community has come at the sticker shock of the EECommerce module.  Obviously everyone loves getting something for nothing, but as you and I know there is nothing that is truly free.  Everything cost something (even if you’re not the one who has to pay).  As an ecommerce entrepreneur, not just a developer, I think there is some real business value in the module that is being developed.  If built correctly, the module could be used to rapidly deploy ecommerce micro sites.  The tool has the potential (we’ll see when we get there) to greatly speed up the development of ecommerce sites that are simple and complex.

The Jury is Out

At the end of the day, the jury is still out.  Until the beta truly gets out there and a the developer community really begins to put some pressure on the module, its hard to see what will come of EECommerce.  I for one, am willing to give it a go and am looking forward to seeing if these guys can pull together a supported tool that helps make online commerce even easier by bringing the feature richness of Magento into the flexibility of Expression Engine.

If you have questions about my meeting and what I was able to see, please post your questions in the comments and I’ll try to address them in a timely manner.

Here are the basics of wiring up the JavaScript navigation to the slide show.

In the flash document (fla) in a new key frame I placed the following:

   1:  import flash.external.*;

   2:  ExternalInterface.addCallback("sspNextImage", sspNextImage);

   3:  ExternalInterface.addCallback("sspPrevImage", sspPrevImage);

   4:  function sspNextImage() {

   5:     my_ssp.nextImage();

   6:  }

   7:  function sspPrevImage() {

   8:     my_ssp.previousImage();

   9:  }

This code basically exposes the SSP API to an external agent such as JavaScript

Then in my web page document in the HEAD tag I included the following:

   1:  <script type="text/javascript">

   2:     function sspNextImage() {

   3:        thisMovie("ssp_kg").sspNextImage();

   4:     }

   5:     function sspPrevImage() {

   6:        thisMovie("ssp_kg").sspPrevImage();

   7:     }

   8:     function thisMovie(movieName) {

   9:        if (navigator.appName.indexOf("Microsoft") != -1) {

  10:           return window[movieName]

  11:        } else {

  12:           return document[movieName]

  13:        }

  14:     }

  15:  </script>

Note that “ssp_kg” is the name of my slide show presentation.

The only thing left to do was to setup the links to call the new JavaScript functions:

<p class="gallery-nav">
<a onclick="sspPrevImage(); return false;" href="#">&laquo; Previous</a>
|
<a onclick="sspNextImage(); return false;" href="#">Next &raquo;</a>
</p>

In the end it was very straight forward and I was well satisfied with the results:

Sample Page: KeeGuard Roof Top Railing – Fall Protection System

I started by creating a basic function which passes in the data I want to capture and pushes it to the Sales force form.

    function add_to_salesforce($source, $name, $email, $company, $city, $state, $zip, $phone, $description, $street = "")

    {

        // simple way of breaking apart the name

        $names = split(" ", $name);

        //set POST variables

        $url = 'https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8';

        $fields = array(

                                'last_name'=>urlencode($names[1]),

                                'first_name'=>urlencode($names[0]),

                                'street'=>urlencode($street),

                                'city'=>urlencode($city),

                                'state'=>urlencode($state),

                                'zip'=>urlencode($zip),

                                'company'=>urlencode($company),

                                'description'=>urlencode($description),

                                'email'=>urlencode($email),

                                'phone'=>urlencode($phone),

                                'mycustomefieldid' => urlencode($source), // custom field

                                'oid' => 'youridgoeshere', // insert with your id

                                'retURL' => urlencode('http://www.yourreturnurl.com'), // sending this just in case

                                'debug' => '1',

                                'debugEmail' => urlencode("youremail@youremail.com"), // your debugging email

                        );

        //url-ify the data for the POST

        foreach($fields as $key=>$value) { $fields_string .= $key.'='.$value.'&'; }

        rtrim($fields_string,'&');

        //open connection

        $ch = curl_init();

        //set the url, number of POST vars, POST data

        curl_setopt($ch,CURLOPT_URL,$url);

        curl_setopt($ch,CURLOPT_POST,count($fields));

        curl_setopt($ch,CURLOPT_POSTFIELDS,$fields_string);

        curl_setopt($ch,CURLOPT_SSL_VERIFYPEER, FALSE);

        curl_setopt($ch,CURLOPT_RETURNTRANSFER, TRUE);

        curl_setopt($ch,CURLOPT_FOLLOWLOCATION, TRUE);

        //execute post

        $result = curl_exec($ch);

        //close connection

        curl_close($ch);

    }

Once that was setup all I had to do was call the function (which I wrapped in a class with something like this:

$myclass = new Myclass;

$myclass->add_to_salesforce("Contact Page", $name, $email_address, $company, "", "", "", $phone, $enquiry);

Works like a charm so far.  If you’ve got a slicker way of perfoming this operation, let me know, I’d love to learn how you did it.