Different galleries, different pages

[TheWookiee]

So the script line will read like this then?
<script src="highslide/highslide.config2.js" ></script>

[MisterNeutron]

Yup, that's all that's needed.

[TheWookiee]

I've done all that, Now I'm having problems with the two galleries on my exhibition page. I have followed the tutorial here:

http://forum.highcharts.com/viewtopic.php?f=4&t=4682

And for some reason the two initial thumbnails have vanished. I've gone over the code again and again but (as you said) I am stumped. HELP!

[MisterNeutron]

Once again, I can't help if all you're giving me is a vague description of the problem. Don't tell me, show me. Give me a link to the page that's giving you problems. Describe exactly what's not working - be specific.

[TheWookiee]

Yes, sorry . this page:

http://www.sentinelphotography.com/exhib.htm

Originally it had two thumbnails, one under each exhibition date. When you clicked on it, then a gallery would open and you could see more photos of each. These were the first galleries I added to the project, and I decided to change the look of them to match the gallery on my "gallery" page. I have re done all the code following the tutorial I mentioned previously, and it is all there, but it won't display anything. I've looked at the code in the tutorial so much I'm probably missing something really obvious, but I cant figure out what.

[MisterNeutron]

You haven't closed any of the anchors. First one, for example:

Code: Select all

Change this:

<a id="thumb1" href="images/NWH/NWH_poster.jpg" class="highslide" 
    onclick="return hs.expand(this, config1 )"

To this:

<a id="thumb1" href="images/NWH/NWH_poster.jpg" class="highslide" 
    onclick="return hs.expand(this, config1 )">

[TheWookiee]

Amazing. I had a feeling it would be something silly. I was rushing, and just copied the code straight from the tutorial (the anchors are missing on that) so I was comparing it to something that was wrong anyway. I had a few more niggles to sort out before it was completely fixed, but it's all good now. Thank you so much for your patience.

[MisterNeutron]

Amazing. I had a feeling it would be something silly.

It usually is. I rarely get through any coding exercise without at least one "smack my forehead" moment.

A code validator can be a big help. In this case, for example, just opening the page code in Firefox (hit CTRL-U while viewing the page) tipped me off - I was seeing a sea of red, starting with the first anchor. So, I knew exactly where to start looking.

For more rigorous code-checking, the W3 online site is good: http://validator.w3.org/. You can feed it a URL, or you can copy and paste all of your page code. And my favorite desktop tool, which checks not only the HTML, but also looks for broken links: https://www.totalvalidator.com/

CSS is usually not as much of a problem, though you'll find yourself sometimes leaving out closing curly braces, or using attributes that don't exist - something like font-color, for example, which I'm sure I've tried at least half-a-dozen times! An online checker, also from W3: http://jigsaw.w3.org/css-validator/

[TheWookiee]

Thank you so much for all the help. Just trying to put some (equally frustrating) finishing touches to the site now. You've been a life saver!

[MisterNeutron]

Glad to help out when I can.