Lightbox works in Dreamweaver Live View but not in browsers

I wanted to find a method of showing a larger version of an image when it is clicked on so have added Lightbox2 by Lokesh Dhakar. I have set up the code for just one image to start with - the seagull on http://www.pembrokeshirewalescoastalholidays.co.uk/Food_and_Drink_in_Pembrokeshire.html
In Live View in Dreamweaver the action works fine, but when I click on the seagull image on the web page in a browser, all I get is a white box with a small square inside it - I should be getting an image of pembroke Castle.
I would be very grateful if you could let me know where I am going wrong?

The following files are not found on your server -
closelabel.gif
loading.gif
pembroke castle 7 large 640 by 480.jpg
(DON'T USE FILE/PATHNAMES CONTAINING SPACES ON THE WEB)

Similar Messages

My Javascript works in Dreamweaver Live View, But Not On The Server

I set up a javascript function to set the focus to the first field in a form as the page loads. It works fine in Dreamweaver's Live View, but not on the local or remote servers. Here's the code:
In the heading I have the following function:
<script type="text/javascript">
function setFocus()
document.getElementById("firstname").focus();
</script>
In the <head tag, I have:
<body onload="setFocus()" ...
and the first field in the form is:
            <input name="firstname" type="text" id="firstname" style="text-align: center; color: #009; text-transform: capitalize; font-variant: normal; font-weight: bold; line-height: normal; font-style: normal; font-size: 14px; font-family: Arial, Helvetica, sans-serif;" tabindex="1" value="<?php echo $fstname; ?>" size="15" maxlength="20">
I guess I must be missing something, but don't know what.

EUREKA! (and OOOPPPPSS!) I found the problem (and I thought javascript was case sensitive - according to the tutorial, it's supposed to be).
Here's apparently wha hoppen. The first field in the form is the person's first name, but it's also a SPRY validation field. I gave the actual field the name and id of "firstname", and the SPRY validation the name "FirstName", figuring that scripts would be case sensitive. In fact, when I first inserted the SPRY object, I tried to name it "firstname" also, but it wouldn't let me, so I capitalized the first letters, and it accepted that; that made me feel that this is OK. Here's the entire field's code:          <label>First Name:
           <span id="FirstName">
            <input name="fstname" type="text" id="fstname" style="text-align: center; color: #009; text-transform: capitalize; font-variant: normal; font-weight: bold; line-height: normal; font-style: normal; font-size: 14px; font-family: Arial, Helvetica, sans-serif;" tabindex="1" value="<?php echo $fstname; ?>" size="15" maxlength="20">
            <span class="textfieldRequiredMsg">A value is required.</span><span class="textfieldMinCharsMsg">Minimum number of characters not met.</span></span></label>
I accidentally tripped over the answer when I started using the Dreamweaver's Edit>Find Next search to see if I had something else named "firstname", and I found that it located every permutation of that word (e.g. firstname, FirstName, FIRSTNAME etc.). Having seen that, I tried changing the "name=" and "id=" to "fstname, and the same corresponding change in the javascript, and VOILA! it worked. That leaves me rather curious about this alleged "case sensitivity" thing. I get the impression that it IS case sensitive, except when IT'S NOT. How does this work, and how do I know when it is and isn't?

Webpage looks good with tranparent boxes and photo background in live view but not in browsers

If anyone has time to help I would be very grateful.   I am new to dreamweaver and am trying to make a webpage with transparent colums and boxed text using styles. It looks perfect in "live view" but when I look at it in any browser all formatting is gone. It looks like the background with text on top layed out wrapped across the entire page.   I have not been able to figure out what is wrong in days of searching. Does anyone know the answer?
This first the format I want and is what it looks like in Live View, the second is what it looks like in most browsers.
Here is the code I used:
</style>
<link href="../styles/tcastyles.css" rel="stylesheet" type="text/css">
<style type="text/css">
body {
          background-image: url(bamboo.JPG);
          margin-left: 150px;
a:link {
          color: #600;
          text-decoration: none;
a:visited {
          text-decoration: none;
a:hover {
          text-decoration: none;
a:active {
          text-decoration: none;
          font-family: Verdana, Geneva, sans-serif;
          font-size: 12px;
          font-weight: bold;
a {
          font-size: 12px;
body,td,th {
          font-family: Verdana, Geneva, sans-serif;
.container .faqs h2 {
          line-height: 40px;
.container .faqs ul li {
          text-align: left;
.footer {
          padding: 5;
          position: relative;
          clear: both;
</style>
<div class="container">
<div class="header"><span class="menutable"></span><img border="0" src="navigate_projects.jpg" width="307" height="167" usemap="#FPMap0" alt="The Conservation Agency - Project Menu" align="absmiddle" />
    <map name="FPMap0">
      <area shape="rect" coords="132, 112, 172, 127" href="asia.htm" alt="Asia" />
      <area shape="rect" coords="138, 92, 286, 110" href="west.htm" alt="Western Hemisphere" />
      <area shape="rect" coords="138, 73, 279, 89" href="flamingos.htm" alt="British Virgin Islands" />
      <area shape="rect" coords="131, 55, 249, 72" href="turkscaicos.htm" alt="Turks and Caicos" />
      <area shape="rect" coords="121, 35, 244, 52" href="newengland.htm" alt="Narragansett Bay" />
      <area shape="rect" coords="103, 17, 306, 32" href="coyote.htm" alt="Narragansett Bay Coyote Study " />
      <area shape="rect" coords="121, 128, 173, 144" href="pacific.htm" alt="Pacific" />
    </map>
</div>
<div class="menu">
    <table width="100%" border="0" align="center" id="menutable">
      <tr>
        <td height="30" align="center" valign="middle"><p><strong><a href="mission.htm">Mission</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="pubs.htm">Publications</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="projects.htm">Projects</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="opps.htm">Opportunities</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="sponsors.htm">Sponsors</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="coyote.htm">NBCS</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="guana.htm">Guana</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="tca.htm">Contact us</a></strong></p></td>
        <td height="30" align="center" valign="middle"><p><strong><a href="index.htm">Home</a></strong></p></td>
      </tr>
    </table>
</div>
<div class="banner">Narragansett Bay Coyote Study</div>
<d/div>
      <div class="box739">
        <h3>What does NBCS Do?</h3>
        <p>Since 2004 The Narragansett Bay Coyote Study (NBCS) has been developing science-based coexistence and management strategies for our newest top predator. Coyotes, originally a prairie species, have successfully colonized all parts of the continental and nearshore us in the past 100 years. They reached the islands of Narragansett Bay in the mid-1990s. Since then coyotes have become increasingly abundant and problematic in some island communities.</p>
        <p>In our history of cohabitation with coyotes people consistently tried to eliminate them by hunting, trapping, and poisoning. Lethal removal worked for individual problem animals but did not work as a population control strategy. Why? Coyotes have intrinsic physiological and behavioral abilities to control their own numbers. If coyotes are removed they increase reproduction and numbers rapidly rebound. The critical population regulation trigger is competition for food. As long as coyotes are well fed (with few coyotes competing for food) their populations will grow. </p>
        <p>It is also known that opposite effect occurs if coyotes if coyotes are stressed by competition for food. If there are too many coyotes competing for the food available coyotes will drop the the level sustainable by those resources.</p>
        <p>Understanding this relationship, NBCS scientists decided to study the resource use of coyotes on two islands in Narragansett Bay, Rhode Island. We used GPS tracking collars to find out where the coyotes were spending thier time. We theorized that if we could identify important coyote food resources - and control them - the coyotes would bring their own numbers down. NBCS calls this "passive coyote management."</p>
        <p> Since 2005 when we trapped and collared our first island coyotes we have continually found that the most important food resources to our study are provided by people. That means they are within our control That means we can control coyotes. If we remove anthropogenic resources (human subsidies) coyote numbers will drop to the level sustainable by natural resources. When coyotes are sustained only by natural prey (mice, woodchucks, rabbits, geese, and deer) coyotes numbers will be lower and they will provide helpful pest control services. </p>
        <p>Based our scientific data NBCS generated a set of <a href="coyotes/Best Management Practices for Coexistence with Coyotes - Nov 8 2010.pdf" target="_new">Best Management Practices for Coexistence with Coyotes</a>- basically a toolbox for safe, sustainable, community coyote management. We are working with the towns in our study area to adopt the CBMPs and be the first community in the nation to successfully and sustainably manage coyotes. We also believe other cities and towns might be able to use our results as a template if they are experiencing coyote problems. We have only just begun to implement the CBMPs on our islands. We hope in the near future to have all our towns implementing the CBMPs - only then will we see the full impacts they make on coyote numbers and behavioral problems. You can follow our progress on this website.</p>
      </div>
      <div class="footer">
        <table width="100%" border="0" cellspacing="5">
          <tr>
            <td>Return to top</td>
            <td><a href="mailto:[email protected]">[email protected]</a></td>
          </tr>
        </table>
      </div>
    </div>
</div>
<p> </p>
</div>iv class="faqs">
    <h2>FAQs</h2>
    <ul>
      <li>How do coyotes control their own population numbers?</li>
      <li>bla bla bla</li>
    </ul>
</div>
<div class="content">
    <div class="clearbox">
      <div class="col1">
        <h3>Middletown Adopts the CBMPs and passes a No-Feeding Ordinance!</h3>
      </div>
      <div class="col2">
        <h3>Pilot, Java, and the Valley Pack</h3>
      <
And here are the styles:
.container {
          height: 1500px;
          width: 975px;
          border: 8px solid #660000;
          float: left;
.header {
          float: left;
          height: 170px;
          width: 975px;
          background-color: #033000;
.menu {
          background-color: #FFC;
          float: left;
          height: 30px;
          width: 975px;
          font-family: Verdana, Geneva, sans-serif;
          font-size: 9px;
          color: #660000;
          font-weight: bold;
          margin-bottom: 5px;
.table {
          font-family: Verdana, Geneva, sans-serif;
          font-size: 8px;
          font-weight: bold;
.banner {
          float: left;
          height: 100px;
          width: 739px;
          font-family: Verdana, Geneva, sans-serif;
          font-size: 37px;
          font-weight: bold;
          color: rgba(0,51,0,1);
          background-color: rgba(255,255,204,.7);
          text-align: center;
          line-height: 75px;
          border-radius: 5px;
          padding: 5px;
          margin: 5px;
.clearbox {
          float: left;
          height: auto;
          width: 760px;
.box739 {
          width: 739px;
          float: left;
          height: auto;
          background-color: rgba(255,255,204,.7);
          font-size: 12px;
          color: rgba(0,51,0,1);
          border-radius: 5px;
          padding: 5px;
          margin: 5px;
.faqs {
          float: right;
          height: 620px;
          width: 205px;
          font-family: Verdana, Geneva, sans-serif;
          font-size: 12px;
          font-style: normal;
          line-height: normal;
          overflow: scroll;
          background-color: rgba(255,255,204,.7);
          margin: 5px;
          border-radius: 5px;
          font-weight: bold;
          color: rgba(0,51,0,1);
          text-align: center;
.col1 {
          float: left;
          height: 500px;
          width: 359px;
          background-color: rgba(255,255,204,.7);
          font-size: 12px;
          border-radius: 5px;
          color: rgba(0,51,0,1);
          margin: 5px;
          padding: 5px;
.col2 {
          float: left;
          height: 500px;
          width: 359px;
          background-color: rgba(255,255,204,.7);
          font-size: 12px;
          border-radius: 5px 5px 5px 5px;
          color: rgba(0,0,0,1);
          padding: 5px;
          margin: 5px;
.footer {
          position:relative;
          clear: both;
          background-color: rgba(255,255,204,1);
          font-size: 12px;
          color: rgba(0,51,0,1);

Helo thanks for responding . I think it uploads... It says it does as an assocaiated file when I put to the website. But that sounds like it is the issue. Those format commands seem to be the one it is ignoring. I am not familiar with html but I see that the href command is what identifies the path to the file I call TCAStyles. I notice that dw puts all my files in a local public file and the structure is different - with no public file - at the site.
I am not sure what the 2 dots in the href command mean - there is not a full path. Is this command valid? I will try to look into the directory structure on local and remote site and will check for files.

Why my adobe lightbox gallery widget works well on "live view" and not well in the browsers?

Hi I need help with adobe lightbox gallery.I am building a website using dreamweaver cs5.
My problem is that the gallery works perfect in "live view" but when I check it in the browsers the pictures do not show at all.
What am I doing wrong .Please help.
Thank you

Hi All:
From my experience with other people having problems with the widget, here are some things you can check when it doesn't work:
Names with uppercase characters: Some servers don't see a difference between "images" and "Images" but most of them do: Check that the paths to the folders and files are correctly written. I encourage people to use always lowercase characters. Same applies to spaces (I prefer to use an underscore instead)
"scripts" folder: I've also found that some servers don't allow a folder called "scripts". You should change both the folder name and the paths in the main document.
Paths: This is the most common one: Make sure that the paths to the required files are correct. In theory, you shouldn't find this when the document is at the site root. If the document is inside a folder, sometimes files' location and related paths may vary. If you are using CS5 or above, a good trick is using the related files toolbar and check whether DW can find and open the files.
Upload all the required files: Some users forget to upload the "lightbox" folder, located inside "images". That folder contains the images used by the lightbox to work (nav and close buttons, for example). And also check that the paths to those images is correct. In this case, you can edit the paths in the parameters that you will find in the script code added to the document (names are quite self explanatory and every param is commented, so this shouldn't be a problem)
I hope this helps.

Slideshow widget works in the live view but doesnt in actual browser. help!!!!

slideshow widget works in the live view but doesnt in actual browser. help!!!!

By "doesn't work in actual browsers" do you mean while using Preview in Browser, or have you uploaded the page and it's not working?
If it's not working after being uploaded, make sure all of the supporting files have been uploaded (.js and .css) as well.
If it's not working in PIB, is it with all browsers, or just certian ones?
Can you post a link to the malfunctioning page?

Slideshow works great in "live view" but does not in "preview browser"

My slideshow looks just fine in "live view" but when I "preview in browser" it doesn't show up at all in Firefox and is a blue square with a question mark in Safari. This was created in Dreamweaver and the slideshow is "Advanced Random Images" from Dreamweaver Exchange.
It was working in the browsers, but I had to make some changes. I put the slideshow within the "content" to get it to be centered on the page.
The centering worked great, but now it's not showing up.
Here is that section of my code:
      
    </p>
    </div>
    
<div class="content">
<div id="slideShow" style="width: 600px; margin: 0 auto; padding-bottom: 15px;">
<script language="JavaScript">
// Advanced Random Images Start
// Copyright 2001-2006 All rights reserved, by Paul Davis - www.kaosweaver.com
var j,d="",l="",m="",p="",q="",z="",KW_ARI= new Array()
// KW_rs[5000]
KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/auditorium.jpg';
KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/boardrm.jpg';
KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/classroom.jpg';
KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/conference.jpg';
KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/conference2.jpg';
KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/courtrm.jpg';
j=parseInt(Math.random()*KW_ARI.length);
j=(isNaN(j))?0:j;
    document.write("<img name='randomSlideShow' src='"+KW_ARI[j]+"'>");
function rndSlideShow(t,l) { // Random Slideshow by Kaosweaver
x=document.randomSlideShow; j=l; while (l==j) {
    j=parseInt(Math.random()*KW_ARI.length); j=(isNaN(j))?0:j; }
x.src=KW_ARI[j]; setTimeout("rndSlideShow("+t+","+j+")",t);
rndSlideShow(5000,0)
// Advanced Random Images End
    </script>
        </div>

<script language="JavaScript">
      </script>
Any suggestions?
Thanks!

I haven't uploaded the page since I made the code changes, for fear that if
they won't "preview in browser", they won't work live...
Here's the link:   www.epaaudio.com

Page looks fine in live view but not fine in safari

my index.html page looks okay in live view, but when i open it in safari some of my text is unformated. My CSS page is correct so the problem lies in my code. I have attached the html file, any help will be appreciated. Thank you!

Thanks for taking the time to reply to question. Aftr taking a break. I came back realized I inserted the stylesheet before I changed site settings. I just needed to remove the forward slash from my stylesheet declaration. FYI for anyone else new to DW: if stuffs not showing in Live View and Browser Preview eg background images, Go to Manage Sites and check your site setting for Links relative to: You may have switched between document and site root. Thus breaking your links to images or in my case the entire style sheet.

Getting a local xml document to populate a listview works in "Live View", but fails in browsers

I'm am extremely new to this so if there is a link or tutorial that explains what I should be doing, please direct me there, however I was unable to locate one on this site.
Challenge:
I'm trying to build a mobile app to read a local xml file and populate a listview. Everything works perfect in the 'Live View' mode of CS5.5, but when I go to preview in Safari or Firefox all that is generated is the listview container with none of the xml loaded content.
I'm reading the xml file as text and then running it through parsexml.
I am sure there is something glaring that I am missing, but I've seen many posts on other sites (not dreamweaver specific) which have shown people struggling with how to accomplish reading a local xml file and using it in a mobile app.
Any Help, insights, suggestions or examples of how to make this work in more than just the 'Live View' will be greatly appreciated.
Many thanks in advance!
XML and Code is Below
XML:
<?xml version="1.0" encoding="utf-8"?>
<Components>
     <Component Id="1" Name="TermOne" Description="Definition of term one.">
           </Component>
        <Component Id="2" Name="Term Two" Description="Definition of term two.">
           </Component>
</Components>
CODE:
$(document).ready(function(){
           $.get( "jquery-mobile/dictionary.xml", function(xml) {
                     var xparse = $($.parseXML(xml));
                    var xlines = [];
                    xparse.find('Component').each(function(){
                              var name = $(this).attr('Name');
                              var description = $(this).attr('Description');
                              xlines.push('<li>' + name + ': ' + description + '</div></li>');
           $('#Dictionary').append(xlines.join(''));
           $('#Dictionary').listview('refresh');
           },"text");
Is there any dreamweaver expert out there who knows why this code will only render in liveview and not on the browsers?
Message was edited by: Lane Hammons

Thanks Murray! viewing the source code, copy/paste worked!
I tried to use the insert image object for the next rollover button...but then got another error message (thankfully just one). I know that I could simply copy the format that you did for the first button, but since this site will be image rollover intensive, I'd like to try to fix this error so I can use the design feature.
Here is the message from validator:
Line 73, Column 443: required attribute "alt" not specified
…me="familytrees" width="105" height="57" border="0" id="familytrees" /></a></p>
✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
I checked the document and both types have been entered - very confused. Have any recommendations?
BTW - do you think it is a good idea for me to get css/html and or javascript for dummies? Do those books really help novices, such as myself?
Your patience and help is great appreciated!

Spry Data Set visible in Live View, but not on Site.

Hi,
I've used the spry data set widget to create a dynamic table. Everything looks fine in the live view. On the site itself, however, I see only a brief flash of the unpopulated spry table, and then nothing. All necessary files, including those in the SpryAssets folder, have been uploaded.
This is particularly frustating since my first crack at a spry data set worked with ease.
I have the feeling that I missing something simple. Any ideas?
Here is the table:
http://www.ldcsb.on.ca/ntip/teachphotos/profiletable.html
Here is the spry data set:
http://www.ldcsb.on.ca/ntip/teachphotos/profiles.html
Thanks for looking,
Jim

Jim, Your page comes up fine in Firefox, but as you said it flashes and disappears in IE8.
I notice some differences in the ids and Spry:sort values. You might sort those out (make them the same) and see what happens.
This is in the profiletable:
<td id="Image">Image</td>
<td id="First">First </td>
<td wid="Last">Last </td>                                        lose the w
<td id="Sschool">School</td>                                   lose the extra s
<td id="Grade">Grade </td>
<td id="Subject1">Subject1</td>
<td id="Subject2">Subject2</td>
<td w id="Description">Description</td>                    lose the w and the extra space
And this in the Spry region:
<th spry:sort="Image">Image</th>
<th spry:sort="First">First</th>
<th spry:sort="Last">Last</th>
<th spry:sort="School">School</th>
<th spry:sort="Grade">Grade</th>
<th spry:sort="Subject1">Subject1</th>
<th spry:sort="Subject2">Subject2</th>
<th spry:sort="Description">Description</th>
It's possible that IE is pickier than Firefox that the names be the same.
Other than that, look for things to clean up, like tightening up the table...I notice several places in the data where there are blank lines between the </tr> of one line and the <tr> of the next. Make sure every entry in the table has a cell for every column.
You're right; it is an easy Widget to work with...unless some tiny thing goes wrong and it doesn't work! I have had a data set that had some of those tiny anomalies, fixed them, and now I know to look for them.
Beth

Websafe fonts changing in design view, but not in browsers

ive currently got a website with font thats extremely hard to read for my real estate company. I can change it in dreamweaver just fine and it shows in design view, but upon previewing in a browser it does not work, just reverts back to the old horrible font. Any suggestions here??
im trying to change the font family to
Tahoma, Geneva, sans-serif
thank you in advance!

There's only one h2 heading on each of those pages e.g. 2001 Update: Banks Charging....
The other subheadings (What is the payout penalty...) are a mishmash of <p> tags, <span> tags and CSS styles.
However, the font appearance and word spacing in those subheadings is controlled by the extensive use of the Cufon font replacement technique.
In the Cufon Javascript file,
http://www.definitiveinvestments.ca/js/cufon-replace.js
the <h2> font is replaced with Bebas http://www.dafont.com/bebas.font
Cufon.replace('h2, h3, .title3', { fontFamily: 'Bebas' });
By hard to read, are you referring to the word spacing?

Shows in Live view but not in Browser

Sorry if this is quite a newbie question but im new to Dreamweaver. I have changed the CSS for the navigation and slider in a free css template i have downloaded, it renders perfectly in live design view on Dreamweaver but no change is apparent on any browser i open it in? There is some Jquery script linked to the slider im not sure if this would be effecting it in any way?

You need to probably do one of the following:
1. Save the file before previewing in a browser
or
2. In your Preferences (Edit -> Preferences), scroll down to the 'Preview in Browser' option. There, check the box marked :Options Preview using temporary file.

Website works in live view but actual site it totally gone after making some edits.

I have had my website through dreamweaver for about a year now. I have been using "simple viewer" program as my gallery for images. However lately I had been having trouble updating and changing images. So yesterday I set up a gallery with the dreamweaver "lightbox" widget. Everything works fine in the dreamweaver live view but when I put the site to my domain its now totally gone. It seems that the site is still trying to link back to the simpleviewer gallery, but nothing shows up, just a white page. I am not sure what is going on here. Customer support through my web host was unhelpful. My site is
www.ryancomptonart.com

When I changed galleries (the gallery is on the index page) I just deleted the simple viewer code and added the lightbox code and resaved the same index_html file.
Here is the entire index page with the new lightbox code: warning this is very long because of the amout of images:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>The Art of Ryan J Compton</title>
<link href="styles.css" rel="stylesheet" type="text/css" />
<link href="css/lightbox.css" rel="stylesheet" type="text/css" />
<link href="css/sample_lightbox_layout.css" rel="stylesheet" type="text/css" />
<script src="scripts/jquery.js" type="text/javascript"></script>
<script src="scripts/lightbox.js" type="text/javascript"></script>
<style type="text/css">
/* BeginOAWidget_Instance_2127022: #gallery */
                    .lbGallery {
                              /*gallery container settings*/
                              background-color: transparent;
                              padding-left: 20px;
                              padding-top: 20px;
                              padding-right: 20px;
                              padding-bottom: 20px;
                              width: 600px;
                              height: auto;
                              text-align:center;
                    .lbGallery ul { list-style: none; margin:0;padding:0; }
                    .lbGallery ul li { display: inline;margin:0;padding:0; }
                    .lbGallery ul li a{text-decoration:none;}
                    .lbGallery ul li a img {
                              /*border color, width and margin for the images*/
                              border-color: #3e3e3e;
                              border-left-width: 10px;
                              border-top-width: 10px;
                              border-right-width: 10px;
                              border-bottom-width: 20px;
                              margin-left:5px;
                              margin-right:5px;
                              margin-top:5px;
                              margin-bottom:5px:
                    .lbGallery ul li a:hover img {
                              /*background color on hover*/
                              border-color: #ffffff;
                              border-left-width: 10px;
                              border-top-width: 10px;
                              border-right-width: 10px;
                              border-bottom-width: 20px;
                    #lightbox-container-image-box {
                              border-top: 0px none #ffffff;
                              border-right: 0px none #ffffff;
                              border-bottom: 0px none #ffffff;
                              border-left: 0px none #ffffff;
                    #lightbox-container-image-data-box {
                              border-top: 0px;
                              border-right: 0px none #ffffff;
                              border-bottom: 0px none #ffffff;
                              border-left: 0px none #ffffff;
/* EndOAWidget_Instance_2127022 */
</style>
<script type="text/xml">

</script>
</head>
<body>
<div id="container">
          <div id="header"> </div>
    <div id="navbar"><a href="index.html">Paintings</a> |<a href="about.html">About</a> |<a href="contact.html">Contact</a> |<a href="http://www.theopticblend.blogspot.com/">Blog </a>|<a href="Commissions.html">Commissions</a></div>
    <div id="page">
</script>
<div id="gallery" class="lbGallery">
<ul>
    <li> <a href="../../Unnamed Site 2/images/lightboximages/Backpack Officalfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/Backpack Officalthumb.jpg" width="72" height="55" alt="Flower" /></a> </li>
    <li> <a href="../../Unnamed Site 2/images/lightboximages/Officalbathfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/Officalbathtum.jpg" width="72" height="58" alt="Tree" /></a> </li>
    <li> <a href="../../Unnamed Site 2/images/lightboximages/pipefull.jpg" title=""><img src="file:///C|/Users/Ryan/Documents/Unnamed Site 2/images/lightboximages/pipetum.jpg" width="54" height="72" alt="" /></a> </li>
    <li> <a href="../../Unnamed Site 2/images/lightboximages/skinny chairfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/skinny chairtum.jpg" width="28" height="72" alt="" /></a> </li>
    <li> <a href="../../Unnamed Site 2/images/lightboximages/water jugfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/sinktum.jpg" width="54" height="72" alt="" /> <img src="../../Unnamed Site 2/images/lightboximages/water jugthum.jpg" width="54" height="72" alt="" /></a></li>
    <li><a href="../../Unnamed Site 2/images/lightboximages/lampfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/lamptum.jpg" width="72" height="58" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/italyfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/italytum.jpg" width="56" height="72" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/hangerfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/hangertum.jpg" width="72" height="50" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/fireexfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/fireextum.jpg" width="58" height="72" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/memboxfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/memboxtum.jpg" width="62" height="72" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/buwrapfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/buwraptum.jpg" width="66" height="72" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/dbathfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/dbathtum.jpg" width="64" height="72" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/messkitfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/messkitthumb.jpg" width="72" height="87" alt="" /></a></li>
    <li><a href="../../Unnamed Site 2/images/lightboximages/orangefull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/orangetum.jpg" width="72" height="58" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/waitfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/waittum.jpg" width="72" height="56" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/xmas ballsfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/xmas ballsthum.jpg" width="58" height="72" alt="" /></a><a href="../../Unnamed Site 2/images/lightboximages/fanfull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/fantum.jpg" width="72" height="51" alt="" /></a></li>
    <a href="../../Unnamed Site 2/images/lightboximages/cupsaucefull.jpg" title=""><img src="../../Unnamed Site 2/images/lightboximages/cupsaucetum.jpg" width="72" height="53" alt="" /></a>
</ul>
</div>
<script type="text/javascript">
// BeginOAWidget_Instance_2127022: #gallery
                    $(function(){
                              $('#gallery a').lightBox({
                                        imageLoading:                              '/images/lightbox/lightbox-ico-loading.gif',                    // (string) Path and the name of the loading icon
                                        imageBtnPrev:                              '/images/lightbox/lightbox-btn-prev.gif',                              // (string) Path and the name of the prev button image
                                        imageBtnNext:                              '/images/lightbox/lightbox-btn-next.gif',                              // (string) Path and the name of the next button image
                                        imageBtnClose:                              '/images/lightbox/lightbox-btn-close.gif',                    // (string) Path and the name of the close btn
                                        imageBlank:                                        '/images/lightbox/lightbox-blank.gif',                              // (string) Path and the name of a blank image (one pixel)
                                        fixedNavigation:                    false,                    // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
                                        containerResizeSpeed:          400,                               // Specify the resize duration of container image. These number are miliseconds. 400 is default.
                                        overlayBgColor:                     "#999999",                    // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
                                        overlayOpacity:                              .6,                    // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
                                        txtImage:                                        'Image',                                        //Default text of image
                                        txtOf:                                                  'of'
// EndOAWidget_Instance_2127022
</script>
</script>
<div id="sv-container"></div>
</div>
    <div id="footer"></div>
</div>
</body>
</html>

How come I can see my div in design view but not in live view

Hi,
I have a div ID called "portfolio" that I can see in design view but not live view or on a browser. It's a little pink square and I want that square round also.
I ran it through validator. It picked up some things in the style.css which I changed and the boilerplate.css that I did not. Because I thought DW auto creates code for boilerplate because I don't enter that code myself.
It's also rejecting a lot of webkit code but this seems like standard webkit code that works elsewhere on the page.
BTW: at what point does this brutal hand coding pay off in money and less heartache when Wordpress looks cleaner and is so much easier to use? I feel like I barely know HTML or CSS in terms of translating vision to reality and with all-browser functionality after months and months of on-line classes. How long are the pros at it till they reach a watershed point?
here's my address: http://www.adjacentdimensionsmedia.com/home.html
Here's my html:
<body>
<div class="gridContainer clearfix">
    <div id="div1" class="fluid"><img src="adtitle2.png" width="700" height="80" alt=""/></div>
<div class="fluid"><div class="box-shad"><a href="index.html"></a></div>
</div>
    <div id="portfolio">Portfolio</div>
</body>
Here's my CSS:
.box-shad {
margin-top: 200px;
margin-left: 100px;
width: 900px;
height: 700px;
display: block;
background-image: url("images/Big-tree-trans1.png");
background-size: 900px 700px;
-webkit-box-shadow: 15px 15px 15px #000000 inset;
box-shadow: 15px 15px 15px #000000 inset;
-webkit-border-radius: 50%;
border-radius: 50%;
position: fixed;
.box-shad a {
    display:block;
    width:900px;
    height:700px;
#portfolio {
width: 100px;
height: 100px;
margin-top: 0px;
margin-right: 200px;
margin-left: 200px;
margin-bottom: 0px;
border-radius: 75%;
-webkit-border-radius: 75% 75%;
background: pink;
top: -300px;
position: relative;

The top:-300 is putting that div above the top of the browser viewport. Fix that and you'll see the div.

Since moving to iCloud, my mobileme email works ONLY on my iPhone, but not on my PC with Outlook. I get an error message indicating the authentication is not accepted. any suggestions?

since moving to iCloud, my mobileme email works ONLY on my iPhone, but not on my PC with Outlook. I get an error message indicating the authentication is not accepted.

To anyone who has viewed this post and is having similar difficulties, the answer came on a different forum: I dragged & dropped the files from Mail to iCloud Drive. Opened them on my MB Air, they were saved in Templates and are now accessible across all my devices.
Answer came from SGIll: Numbers templateshttps://discussions.apple.com/message/27505880#27505880Numbers templates

IPod nano works with USB 1.1 but not USB 2.0

Anyone using an iPod nano that works with USB 1.1 but not with USB 2.0? I am using Windows XP and when installing the iPod software from CD it recognizes the iPod and am able to transfer songs using iTunes but when installing SP1 or SP2 to enable USB 2.0 transfers, Windows XP only recognizes the iPod nano as a USB Mass Storage Device. This is the same with iPod Updater.

I have a similar problem with the following configuration:
- Dell Dimension 4100 Desktop with 2 integrated USB 1.1 ports, Windows 2000 SP 4
- PCI 6-Ports USB 2.0 Card ("Mentor" resp. www.bona.com.tw), Model USB20-PCI/6P
What works well?
- All my USB add-ons (1.1 and 2.0) on the internal 1.1 ports as well as on the USB2.0 PCI card
- iPod Nano 4GB on internal 1.1 ports (external drive in windows 2000 as well as iPod in iTunes)
- iPod Nano works as well as on the USB 2.0 card ONLY WHEN my old 4-port USB1.1 hub is connected between Nano and USB card
What doesn't works?
My iPod Nano directly connected to the USB 2.0 card. Symptoms when connecting:
- Windows is very slow, process "scvhost.exe" or "system.exe" using 99% of CPU for some minutes
- iPod is recognised as external drive, but when I click on it, it is empty and copying files to it results in "I/O error"
- iTunes doesn't recognise the iPod (of course, if even windows itself cannot read from it...)
I removed all USB drivers, reinstalled iTunes, iPod (by the way, I still don't understand what "iPod update" is good for, except for updating the iPod's firmware), deactivate the internal USB1.1 ports, no result.
Help!!!!!!!!!!!!!!!!

Lightbox works in Dreamweaver Live View but not in browsers

Similar Messages

Maybe you are looking for