Problem with foundation classes

Hi Wendell Pulsipher (waow, so many kind of names I never heard of on Treehouse ^^, where are you from?),

Your script has some spell errors. pronto -> proto, and missed a closing > after '.js.

 <script>
      document.write('<script src=' +
        ('__proto__' in {} ? 'js/vendor/zepto' : 'js/vendor/jquery') +
        '.js><\/script>')
    </script>
    <script src='js/foundation.min.js'></script>
    <script>
      $(document).foundation();
    </script>

Should work correctly now :). Hope it helped!

yes! It worked! Thank you very much... rookie mistake. I'm from the States originally. My last name comes from Ireland though as far back as I have been able to trace (early 1600s)

okay having another problem now...

<div class='row'>
      <div class='large-12 columns' data-orbit>
        <div>
          <h1>Self-destructing message app</h1>
          <p class='lead'>Learn how to build this fun little app by signing up for a
          Treehouse account today.</p>
          <p class='button-group'>
            <a href='#' class='button default'>Download the app</a>
            <a href='#' class='button success hide-for-small-only'>Text me the link</a>
          </p>
        </div>
        <div>
          <h1>Learn how to build it for iOS</h1>
          <p class='lead'>We'll teach you how to build it from scratch!</p>
          <p><a class='medium button radius' href='#'>Get started today!</a></p>
        </div>
        <div>
          <h1>Learn how to build it in Android</h1>
          <p class='lead'>We'll teach you how to build it from scratch!</p>
          <p><a class='medium button radius' href='#'>Get started today!</a></p>
        </div>
      </div>
    </div>

after adding data-orbit class where indicated in the orbit slider video (foundation framework) the slider doesn't work or look like it's supposed to in the video..

I tried your code, and it works perfectly here (testing with the code challenge app). What I would suggest if you want to debug your code, be methodic (and patient).

1. Get a "good code" (which you know is working perfectly), the best is something similar (I used the code challenge code for your code). Apply it to verify the result.
2. When done, you replace the portion of the code you need to test. See the result. If it doesn't work, you know it is your code which have a problem.
3. If not, then it's something else in your code.

I used the same process with your first question. I tested a code which I know would work well, then I replaced portions of the code with yours. When I saw that the html body was fine, I knew it was from either the head or the script. Tried to replace the head, worked fine. Tested the script: Bummer! It's quite simple, first you need to isolate the code which pose a problem, then you can fix it by comparing/testing.

Then for the last question. I checked your code with the code of the code challenge (which displayed the slider correctly), replace the slider part with your code, and it worked fine. It might come from somewhere else. Try to figure out by yourself, and if you still can't get a good result, come back here and paste your entire code ^^.

Good luck, my friend.

Hmmm... well I went and compared my code and isolated certain parts of it with no success, so I tried just overwriting the contents of the css, js and img folders in my directory with the included project files and that resolved the issue. Only problem is I don't know what the issues actually was and which files I may or may not have had or called properly (or not) in the HTML. Well.. at least the problem is solved. Looks like I'll need to do some very in depth reading on the Foundation website.

As long as it worked, you respected your contract to the client :), that's it (simulation of a professionnal project). But for you, you would want to know why it didn't work, and be able to master your code. For that, I recommend that you make a copy of your bugged version, then when you have a fixed version, you can compare them (same process as before). Well, that's for the future projects ^^, don't sweat it, it is always a good experience (now you'll know what not to do).

What you did is that you isolated, in a certain way, the problem, you know by now that it was not your assumption that it was this snippet which was wrong. It came from the other files. It is a good practice, I think, to not overwrite everything when you have a problem (it is the same thing as formating and reinstalling your computer when it doesn't work properly, it work again, but you don't know what was the problem).