Random Image not displaying in Live View.

My page is at:
www.andrewjamesartist.co.uk
There's a random image script on the front page.
<img src="randomimages/rotate.php" alt="A Sample Image from the work of Andrew James" />
That's how it is placed in the page.
It shows in preview in browser and it's OK live but it doesn't show in LiveView.
I use a testing server set up with virtual hosts.
Martin

Similar Messages

Div Image not showing in Live View

Why can't I see my image placed within a Div tag in Live View? Makes no sense. I've changed the z-index to 1000, also tried 1 nothing changes. Please advise if anyone can help. Thank you!

I've applied BOLD to the Div tag in question
HTML Code:
<!doctype html>
<html>
<head>
<meta charset="UTF-8">

<title>Permanent Concrete and Asphalt Repair Home Page</title>
<meta name="description" content="CeraTech's Pavemend family of high performance concrete repair products have become the choice of professionals across the country for their rapid return to service, versatility, ease of use, and superior durability.">
<style type="text/css">
#apDiv8 {
    position: absolute;
    width: 200px;
    height: 115px;
    z-index: 2;
</style>

<link href="pavmend_styles.css" rel="stylesheet" type="text/css">
<style type="text/css">
#pavemendlogo {
    background-image: url(_images/NEW%202012%20PAVEMEND%20LOGO%20WHITE.png);
    background-repeat: no-repeat;
    height: 78px;
    width: 196px;
#prochoicetype {
    background-image: url(_images/pro_choice_concrete_type.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 521px;
    margin-left: 200px;
    margin-top: -40px;
#prochoicetype {
    background-image: url(_images/pro_choice_concrete_type.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 521px;
    margin-left: 200px;
    margin-top: -40px;
</style>


</head>
<body>
<div id="wrapper">
<div class="container">
<div id="apDiv1"><a href="pavemend_home_page.html"><img src="_images/NEW 2012 PAVEMEND LOGO WHITE.png" width="197" height="79" class="fltlft" /></a>
    <div id="resources"></div>

<div class="headerResources"></div>

<nav>
<ul id="menu">
    <li><a href="pavemend_home_page.html">OUR PRODUCTS ▼</a>
      <ul>
        <li><a href="slq_product_page.html">SLQ<sup>®</sup></a></li>
        <li><a href="sl_product_page.html">SL<sup>®</sup></a></li>
        <li><a href="dotline_product_page.html">DOTLine™</a></li>
        <li><a href="15.0_product_page.html">Pavemend 15.0<sup>®</sup></a></li>
        <li><a href="TR_product_page.html">Pavemend TR<sup>®</sup></a></li>
        <li><a href="VR_product_page.html">Pavemend VR<sup>®</sup></a></li>
        <li><a href="IA_product_page.html">Instant Asphalt™</a></li>
        <li><a href="kemrok_product_page.html">KEMROK™</a></li>
        <li><a href="kemrokVR_product_page.html">KEMROK VR™</a></li>
        <li><a href="firerok_product_page.html">FIREROK™</a></li>
        <li><a href="antiwear_product_page.html">Anti-Wear™</a></li>
        <li><a href="antiscale_product_page.html">Anti-Scale™</a></li>
      </ul>
    </li>
    <li><a href="resources_page.html">RESOURCES</a></li>
    <li><a href="technical_support.html">TECHNICAL SUPPORT</a></li>
    <li><a href="contact_page.html">CONTACT US</a></li>
</ul>
</nav>
    </section>

<div class="sidebarleftlong">
<nav>
    <ul>
      <li><a href="#">PAVEMEND PRODUCT <br>    BROCHURE</a></li>
      <p><li><a href="#">KEEP TRAFFIC MOVING <br>    BROCHURE</a></li></p>
      <p><li><a href="#">CASE STUDIES</a></li></p>
      <p><li><a href="#">INSTANT ASPHALT REPAIR</a></li></p>
      <p><li><a href="#">SL PRODUCT VIDEO</a></li></p>
      <p><li><a href="#">SLQ PRODUCT VIDEO</a></li></p>
      <p><li><a href="#">DOTLINE FIELD <br>    APPICATION VIDEO</a></li></p>
    </ul>
    </nav>
   <div id=""></div>
    </div>


<div class="content">
<p> </p>
<img src="_images/resources_header.png" alt="slheader" width="553" height="31" class="productlogos" />
</section>
<p> </p>
      <section>
        <p><strong>Pavemend</strong><sup>®</sup> Rapid, Permanent Concrete and Asphalt repair products are quickly becoming the choice for Turnpike, State DOT Bridge Crews and discriminating engineers who value superior, permanent repairs and reduced traffic disruptions.</p>
<p>Typical repair applications include full and partial depth bridge deck repairs, bridge header joints, approach slabs, form & pour repairs, dowel bar retrofits, joint nosings and more. <strong>Pavemend</strong><sup>®</sup> products require only the addition of water, with no bonding agents or curing requirements and offer all season rapid repair capability.</p>
<p>Featuring technology developed here in the USA, <strong>Pavemend</strong><sup>®</sup> (by CeraTech Inc) products are easier to use, offer greater durability, provide superior return on investment, and are by far the most sustainable repair products available today.</p>
        <p><img src="_images/Done Smart Logo.png" width="150" height="17" alt="donesmartlogo" />
      </section>
</div>
        
<div class="footer"><img src="_images/NEW 2012 PAVEMEND LOGO WHITE.png" width="160" height="64" class="flt_rgt" />
    <table width="510" summary="footer material">
<tr>
    <td width="210"><strong><em>Manufactured by</em></strong></td>
<tr>
    <td><img src="_images/CTI_logo_white.png" width="200" height="47" alt=""/>
    <td width="50" align="center"><a href="#../twitter.com/Pavemend">Twitter</a>
<div id="apDiv7"></div>
<td><strong><em>Planet Friendly Technology</em></strong></td>
   </tr>
</table>
    <div id="apDivPFT1"></div>
    </div>
</div>
</body>
</html>
CSS:
@charset "UTF-8";
/* BEGIN HORIZONTAL DROP-MENU */
#menu {
    clear: left;
    position: relative;
    width: 100%; /**adjust width as needed**/
    margin: 0;
    padding: 0;
    background-image: url(_images/topnavpanel.png);
    color: #FFFFFF;
#menu ul {
    margin: 0;
    padding: 0
#menu li {
    list-style: none;
    float: left;
    text-align: center;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    color: #000000;
/**top level menu**/
#menu li a {
    display: inline-block;
    text-decoration: none;
    /* adjust width as needed or use auto */
    width: 13em;
    padding: 8px;
    font-weight: bold;
    line-height: 12px;
    color: #000;
    border-top-style: none;
    font-size: 90%;
    margin-bottom: 0;
    margin-left: 2%;
    margin-right: 2%;
    margin-top: 0;
    border-bottom-style: none;
/**top menu style on mouse over**/
#menu li:hover > a {
    color: #FFF;
    width: 13em;
/**sub-menu**/
#menu li ul {
    display: none;
    text-align: center;
    padding: 0;
    margin-bottom: 0;
    margin-left: 40px;
    margin-right: 0;
    margin-top: 0;
    border-bottom-style: none;
/**sub-menu, help for older IE**/
#menu li:hover ul, #menu li.hover ul {
    display: block;
    position: absolute;
    z-index:1000;
    padding: 0;
#menu li:hover li, #menu li.hover li {
    float: none;
    background-color: #E1D5BB;
/**drop-menu style**/
#menu li:hover li a, nav li.hover li a {
    width: 14em; /* adjust width as needed or use auto */
    margin-top: 0;
/**drop-menu style on mouse over**/
#menu li li a:hover {
    color: #FFF;
    background-color: #03C;
/* Clear floated elements at the end*/
#menu:after {
    visibility: hidden;
    display: block;
    font-size: 0;
    content: " ";
    clear: both;
    height: 0;
/**END HORIZONTAL DROP-MENUS STYLES**/
#apDiv11 {
    position: absolute;
    width: 190px;
    height: 180px;
    z-index: 2;
    background-image: url(_images/WomanPhone.png);
    background-position: 10px;
    background-repeat: no-repeat;
    margin-top: 240px;
#apDivSustainability {
    position: absolute;
    width: 200px;
    height: 420px;
    z-index: 3;
    background-image: url(_images/sustainabilitySB2.png);
    background-repeat: no-repeat;
#apDiv10 {
    position: absolute;
    width: 75px;
    height: 73px;
    z-index: 2;
    background-image: url(_images/PFTLogo.png);
    float: right;
    margin-left: 650px;
    margin-top: -110px;
#apDiv9 {
    position: absolute;
    width: 200px;
    height: 207px;
    z-index: 3;
    background-image: url(_images/slphoto1.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivslqphoto {
    position: absolute;
    width: 200px;
    height: 267px;
    z-index: 3;
    background-image: url(_images/slqphoto.jpg);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivdotlinephoto {
    position: absolute;
    width: 200px;
    height: 267px;
    z-index: 3;
    background-image: url(_images/dotlinephoto.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDiv15photo {
    position: absolute;
    width: 200px;
    height: 179px;
    z-index: 3;
    background-image: url(_images/15.0_photo.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivTRphoto {
    position: absolute;
    width: 200px;
    height: 267px;
    z-index: 3;
    background-image: url(_images/TR_photo.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivAWphoto {
    position: absolute;
    width: 200px;
    height: 150px;
    z-index: 3;
    background-image: url(_images/AWPhoto.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivASphoto {
    position: absolute;
    width: 200px;
    height: 134px;
    z-index: 3;
    background-image: url(_images/ASphoto.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivVRphoto {
    position: absolute;
    width: 200px;
    height: 150px;
    z-index: 3;
    background-image: url(_images/VR_photo.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivIAphoto {
    position: absolute;
    width: 200px;
    height: 162px;
    z-index: 3;
    background-image: url(_images/IA_photo.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivKemrokphoto {
    position: absolute;
    width: 200px;
    height: 207px;
    z-index: 3;
    background-image: url(_images/KEMROK%20pic.jpg);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivFirerokphoto {
    position: absolute;
    width: 200px;
    height: 248px;
    z-index: 3;
    background-image: url(_images/Firerok_photo.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivtechsupportphoto {
    position: absolute;
    width: 200px;
    height: 248px;
    z-index: 3;
    background-image: url(_images/techsupport_photo.png);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDivKemrokVRphoto {
    position: absolute;
    width: 200px;
    height: 207px;
    z-index: 3;
    background-image: url(_images/Kemrok%20VR%20pic.jpg);
    background-repeat: no-repeat;
    margin-top: 30px;
    margin-left: -5px;
#apDiv8 {
    position: absolute;
    width: 180px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/SLbktandbag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -160px;
    margin-left: 520px;
#apDivslq {
    position: absolute;
    width: 80px;
    height: 105px;
    z-index: 2;
    background-image: url(_images/SLQbucket.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -125px;
    margin-left: 515px;
#apDivdotlinebag {
    position: absolute;
    width: 88px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/dotlinebag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -165px;
    margin-left: 280px;
#apDivkemrokbag {
    position: absolute;
    width: 121px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/kemrok_bag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -165px;
    margin-left: 570px;
#apDivPFT1 {
    position: absolute;
    width: 121px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/PFTLogo.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -75px;
    margin-left: 470px;
#apDivkemrokVRbag {
    position: absolute;
    width: 121px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/kemrokvr_bag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -160px;
    margin-left: 590px;
#apDivFirerokbag {
    position: absolute;
    width: 90px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/firerok_bag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -160px;
    margin-left: 570px;
#apDivAWbucket {
    position: absolute;
    width: 90px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/firerok_bag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -160px;
    margin-left: 590px;
#apDivAWbucket {
    position: absolute;
    width: 90px;
    height: 167px;
    z-index: 2;
    background-image: url(_images/firerok_bag.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -160px;
    margin-left: 590px;
#apDivAWbucket {
    position: absolute;
    width: 80px;
    height: 96px;
    z-index: 2;
    background-image: url(_images/AWbucket.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -160px;
    margin-left: 590px;
#apDiv15bag {
    position: absolute;
    width: 88px;
    height: 111px;
    z-index: 2;
    background-image: url(_images/15.0bucket.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -115px;
    margin-left: 260px;
#apDivTRbucket {
    position: absolute;
    width: 80px;
    height: 106px;
    z-index: 2;
    background-image: url(_images/TRbucket.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -120px;
    margin-left: 370px;
#apDivAWbucket {
    position: absolute;
    width: 205px;
    height: 150px;
    z-index: 2;
    background-image: url(_images/AWArt.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -140px;
    margin-left: 420px;
    font-size: 120%;
    -webkit-box-shadow: 0px 0px;
    box-shadow: 0px 0px;
#apDivASArt {
    position: absolute;
    width: 205px;
    height: 150px;
    z-index: 2;
    background-image: url(_images/ASArt.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -140px;
    margin-left: 420px;
    font-size: 120%;
    -webkit-box-shadow: 0px 0px;
    box-shadow: 0px 0px;
#apDivVRbucket {
    position: absolute;
    width: 80px;
    height: 87px;
    z-index: 2;
    background-image: url(_images/VRbucket.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -105px;
    margin-left: 470px;
#apDivIAbucket {
    position: absolute;
    width: 251px;
    height: 106px;
    z-index: 2;
    background-image: url(_images/IAbuckets.png);
    background-repeat: no-repeat;
    float: right;
    margin-top: -120px;
    margin-left: 400px;
body {
    background-color: #666;
    color: #000;
    text-align: center;
    background-image: url(_images/roadblurred.png);
    background-repeat: no-repeat;
    background-attachment: fixed;
    background-position: center;
    padding-top: 60px;
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 100%;
    line-height: 1.4;
.formtext {
    font-size: 100%;
    text-align: left;
.bodyfootnote {
    font-size: 70%;
    margin-left: 20px;
    font-family: Verdana, Arial, Helvetica, sans-serif;
.red {
    font-size: 70%;
    color: #F00;
.popups {
/* ~~ Element/tag selectors ~~ */
ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
    padding: 0;
    margin: 0;
    text-transform: capitalize;
    text-decoration: none;
    list-style: none;
h1, h2, h3, h4, h5, h6, p {
    /* [disabled]margin-top: 0; */     /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
    padding-right: 15px;
    padding-left: 23px;
    line-height: 25px;
a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
    border: none;
/* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
a:link {
    color: #FFFFFF;
    text-decoration: none;
    font-size: 100%;
    padding: 5px;
a:visited {
    color: #FFFFFF;
    text-decoration: underline;
a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
    text-decoration: none;
    background-color: #03C;
    color: #FFF;
    height: 12px;
    alignment-baseline: text-after-edge;
/* ~~this fixed width container surrounds the other divs~~ */
.container {
    width: 960px;
    background-color: #FFF; /* the auto value on the sides, coupled with the width, centers the layout */
    background-image: url(_images/Bridge4WebScreened.png);
    background-repeat: no-repeat;
    margin-bottom: 0;
    margin-left: 0px;
    margin-right: 0px;
    margin-top: 0;
    text-align: left;
.containerTS {
    width: 960px;
    background-color: #FFF;
    margin: 0 0px; /* the auto value on the sides, coupled with the width, centers the layout */
    background-image: url(_images/US_Map.png);
    background-repeat: no-repeat;
    text-align: left;
/* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
.header {
    background-color: #000;
    background-image: url(_images/BannerBlured960.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerSL {
    background-color: #000;
    background-image: url(_images/PMND%20SL%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerPurchase {
    background-color: #000;
    background-image: url(_images/contact%20us%20pavemend%20header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerSLQ {
    background-color: #000;
    background-image: url(_images/PMND%20SLQ%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerDOTline {
    background-color: #000;
    background-image: url(_images/DOTLINE%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.header15 {
    background-color: #000;
    background-image: url(_images/PMND%2015.0%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerTR {
    background-color: #000;
    background-image: url(_images/PMND%20TR%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerAW {
    background-color: #000;
    background-image: url(_images/anti_wear_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerAS {
    background-color: #000;
    background-image: url(_images/anti%20scale%20pavemend%20header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerVR {
    background-color: #000;
    background-image: url(_images/PMND%20VR%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerIA {
    background-color: #000;
    background-image: url(_images/Instant%20asphalt%20packaged%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerKemrok {
    background-color: #000;
    background-image: url(_images/KEMROK%20packaged%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerKemrokVR {
    background-color: #000;
    background-image: url(_images/KEMROK%20VR%20packaged%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerFirerok {
    background-color: #000;
    background-image: url(_images/FIREROK%20packaged%20Header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerAntiWear {
    background-color: #000;
    background-image: url(_images/anti_wear_pavemend_header.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerTechSupport {
    background-color: #000;
    background-image: url(_images/FEBlurred.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.headerResources {
    background-color: #000;
    background-image: url(_images/ResourceBanner.png);
    height: 229px;
    background-repeat: no-repeat;
    width: 960px;
.header h1 {
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 20pt;
    font-style: normal;
    font-weight: bolder;
    color: #FFF;
    padding-top: 150px;
    padding-left: 30px;
/* ~~ These are the columns for the layout. ~~
1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
.sidebar1 {
    float: right;
    width: 180px;
    margin-left: 0px;
    margin-right: 30px;
    clear: none;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 100%;
    font-style: italic;
    background-image: url(_images/Testimonialb.gif);
    background-repeat: no-repeat;
    height: 456px;
    text-decoration: none;
    z-index: 1000;
.sidebarPurchase {
    float: right;
    width: 200px;
    margin-left: 0px;
    margin-right: 20px;
    clear: none;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 100%;
    font-style: italic;
    background-image: url(_images/purchaseSB.png);
    background-repeat: no-repeat;
    height: 420px;
    margin-top: 0px;
    text-decoration: none;
    background-color: #217CC0;
    background-position: 10px 10px;
.sidebarleft {
    float: left;
    width: 195px;
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 85%;
    font-style: oblique;
    height: 200px;
    text-decoration: none;
    padding-top: 8px;
    padding-left: 10px;
    margin-right: 5px;
    background-color: #217CC0;
    vertical-align: bottom;
    line-height: 30px;
    font-weight: bold;
    border-bottom-style: groove;
    border-bottom-width: 10px;
    margin-top: -4px;
.sidebarleftlong {
    float: left;
    width: 195px;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    font-style: oblique;
    height: 280px;
    text-decoration: none;
    padding-top: 20px;
    margin-right: 5px;
    background-color: #217CC0;
    vertical-align: bottom;
    line-height: 17px;
    font-weight: bold;
    border-bottom-style: groove;
    border-bottom-width: 10px;
    margin-top: -4px;
    color: #FFF;
    font-size: 85%;
    text-align: left;
    padding-left: 10px;
.sidebargreen {
    float: left;
    width: 195px;
    height: 410px;
    text-decoration: none;
    padding-top: 20px;
    margin-right: 5px;
    background-color: #8CC63F;
    border-bottom-style: groove;
    border-bottom-width: 10px;
    margin-top: -4px;
    padding-left: 10px;
.nav2 {
    font-family: bebas-neue;
    font-style: normal;
    font-weight: 400;
    color: #FFF;
.sidebarleft nav ul li a {
    text-decoration: none;
    color: #FFF;
.sidebarleftlong nav ul li a {
    text-decoration: none;
    color: #FFF;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    font-weight: bold;
.content {
    width: 730px;
    float: left;
    background-image: none;
    background-repeat: no-repeat;
    background-position: left;
    font-family: "Gill Sans", "Gill Sans MT", "Myriad Pro", "DejaVu Sans Condensed", Helvetica, Arial, sans-serif;
    padding: 10px 0;
    text-align: left;
    font-size: 100%;
/* ~~ This grouped selector gives the lists in the .content area space ~~ */
.content ul, .content ol {
    padding: 0 15px 15px 40px;
    text-decoration: none;
/* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
ul.nav {
    list-style: none; /* this removes the list marker */
    border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
    margin-bottom: 15px; /* this creates the space between the navigation on the content below */
    text-decoration: none;
ul.nav li {
    border-bottom: 1px solid #666;
ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
    padding: 5px 5px 5px 15px;
    display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
    width: 160px; /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
    text-decoration: none;
    background-color: #C6D580;
ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
    background-color: #DFEBF3;
    color: #FFF;
    text-decoration: none;
/* ~~ The footer ~~ */
.footer {
    padding: 10px 0;
    position: relative;/* this gives IE6 hasLayout to properly clear */
    clear: both;
    background-color: #000000;
/* ~~ miscellaneous float/clear classes ~~ */
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: left;
    margin-left: 760px;
.fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
    float: left;
    margin-right: 8px;
.clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
    clear:both;
    height:0;
    font-size: 1px;
    line-height: 0px;
#apDiv1 {
    position: absolute;
    width: 900px;
    height: 94px;
    z-index: 1;
    margin-top: 80px;
    margin-left: 30px;
    white-space: 3;
    font-size: 100%;
    text-align: left;
sllogo {
    background-image: url(_images/SLwhitelogo.png);
    background-repeat: no-repeat;
.slLogo {
    background-image: url(_images/SLwhitelogo.png);
    background-repeat: no-repeat;
    height: 100px;
    width: 240px;
.productlogos {
    margin-left: 23px;
    margin-top: 10px;
.Bold {
    font-weight: bold;
.inherent {
    font-style: inherit;
sup {
    position: relative;
    top: -1ex;
    vertical-align:baseline;
    font-size: 75%;
#apDiv2 {
    position: absolute;
    width: 650px;
    height: 31px;
    z-index: 2;
    background-repeat: no-repeat;
    padding-right: 15px;
    padding-left: 15px;
    margin-right: 15px;
    margin-left: 15px;
    top: 369px;
    background-image: url(_images/homeheader.png);
.footer table tr td {
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 75%;
    color: #FFF;
    height: 8px;
    width: 160px;
    margin-left: 10px;
    padding-left: 15px;
    border-collapse: collapse;
    padding-top: 0px;
    padding-right: 0px;
    padding-bottom: 5px;
.footer p {
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 80%;
    color: #FFF;
    margin-top: 20px;
    margin-bottom: 20px;
    margin-right: 30px;
.footer table tr th h4 {
    font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;
    font-size: 75%;
    color: #FFF;
    float: left;
    padding-left: 15px;
    height: 0px;
.footer table tbody tr td a {
    color: #FFF;
#wrapper {
     width:970px; /**adjust as needed**/
     margin:0 auto; /**centers page on screen**/
.flt_rgt {
    float: right;
    margin-top: 15px;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
.title {
    /* [disabled]margin-right: 30px; */
    margin-top: 35px;
    margin-left: 10px;
    background-image: ;
    background-repeat: no-repeat;
    /* [disabled]margin-left: 20px; */
    top: 30px;
    /* [disabled]margin-top: 30px; */
    left: 30px;
.flt_products {
    float: right;
    margin-right: 30px;
    background-image: ;
    background-repeat: no-repeat;
.container section nav {
    background-image: url(_images/topnavpanel.png);
    background-repeat: no-repeat;
    height: 30px;
    width: 960px;
    padding-top: 3px;
#apDiv3 {
    position: absolute;
    width: 468px;
    height: 41px;
    z-index: 2;
    background-image: url(_images/savetimetext.png);
    background-repeat: no-repeat;
    margin-left: 15px;
#apDiv4 {
    position: absolute;
    width: 400px;
    height: 41px;
    z-index: 3;
    background-image: url(_images/ULTRAFLOR.png);
    background-repeat: no-repeat;
    margin-left: 10px;
    margin-top: 45px;
#apDiv5 {
    position: absolute;
    width: 250px;
    height: 103px;
    z-index: 4;
    background-image: url(_images/HI%20RES%20PRODUCT%20FAMILY%20w%20IA.png);
    background-repeat: no-repeat;
    float: right;
    right: auto;
    margin-left: 675px;
    margin-top: -22px;
#apDiv6 {
    position: absolute;
    width: 40px;
    height: 38px;
    z-index: 5;
    background-image: url(_images/PFT%20No%20Text%20No%20Flip.png);
    margin-top: -25px;
    margin-left: 83px;
#apDiv7 {
    position: absolute;
    width: 20px;
    height: 17px;
    z-index: 5;
    background-image: url(_images/twitter-bird-dark-bgs.png);
    margin-top: -15px;
    margin-left: 85px;
nav ul {
    list-style: none; /* this removes the list marker */
    border-top: 1px solid #666; /* this creates the space between the navigation on the content below */
    font-size: 90%;
nav ul li {
    text-decoration: none;
    color: #FFF;
nav ul a:link , nav ul a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
    padding: 5px 5px 5px 15px;
    display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
    width: 160px; /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
    text-decoration: none;
    text-align: left;
    color: #FFF;
nav ul a:hover, nav ul a:active, nav ul a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
    color: #FFF;
    text-decoration: none;
.orange {
    color: #FAA634;
.white {
    color: #FFFFFF;
.red {
    color: #F00;
.red1 {
    color: #F00;
.toppanel {
    background-image: url(_images/topnavpanel.png);
    background-repeat: no-repeat;
    height: 30px;
    width: 960px;
#apDiv12 {
    position: fixed;
    width: 960px;
    height: 30px;
    z-index: 5;
    background-image: url(_images/topnavpanel.png);
    background-repeat: no-repeat;
    float: left;
    top: 229px;
.white {
.CeraTechLogo {
    background-image: url(_images/CTI_logo_white.png);
    background-repeat: no-repeat;
    width: 200px;
    height: 60px;
.apDivPFT {
    background-repeat: no-repeat;
    padding-left: px;
    padding-top: 0px;
#prochoicetype {
    background-image: url(_images/pro_choice_concrete_type.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 521px;
    margin-left: 200px;
    margin-top: -40px;
#resources {
    background-image: url(_images/ResourcesType.png);
    background-repeat: no-repeat;
    height: 25px;
    width: 521px;
    margin-left: 200px;
    margin-top: -40px;

Certain images not appearing in Live View?

Hello,
I recently upgraded my Dreamweaver CS5 and have noticed that certain images are no longer appearing in Live View. When Live View is unclicked, both of the images appear in both Design View and Preview in Browser; however, when Live View is clicked, the question mark appears for new images that were not used in Dreamweaver previous to the update. Does anyone know a fix to this? I have already tried to uninstall/re-install the software. Thanks for your help.

What is the exact code path to images?
How big are your images (filesize)? Did you optimize them for the web in your graphics editor before inserting them into your web page? Are they saved as RGB and not CMYK?
Nancy O.

Background image is not displaying in all views

I'm developing a site where in one particular page a background image displays in Live View, but not in IExplore. This image is used in other pages with no problem. In Browser Lab the page displays correctly in IE8, FF and Safari. Should I be concerned? The whole site isn't working in IE6 & 7 but that I'll have to address that later. Here's the css:
#mainImage{
    background: url(images/main_bkgrnd_blk.jpg);
    background-position: center top;
    background-repeat: repeat-y;
    width: 875px;
    height:788px;
    margin: 0 auto;
    position: relative;

jalynoble wrote:
I'm developing a site where in one particular page a background image displays in Live View, but not in IExplore. This image is used in other pages with no problem. In Browser Lab the page displays correctly in IE8, FF and Safari. Should I be concerned? The whole site isn't working in IE6 & 7 but that I'll have to address that later. Here's the css:
#mainImage{
    background: url(images/main_bkgrnd_blk.jpg);
    background-position: center top;
    background-repeat: repeat-y;
    width: 875px;
    height:788px;
    margin: 0 auto;
    position: relative;
When you say it does not display in IExplore where are you checking that, on your computer and which version of IE?
If you have checked the page in Browser Lab and it displays ok then I would not worry, but it slightly concerns me that it's not showing in your local version of IE?
For what's its worth I would'nt bother with IE6 (it's practically dead) but you must address the issues in IE7.

Code not displaying in code view

When searching for a particular feature, I may have clicked on something by accident. Now, my site looks and works fine in the browser and in design and live view, but the code is not displaying in code view. See attached image.
Anyone know how to fix this??? Thank you in advance!

Have you tried restarting everything?

OBIEE 10G Embedded Image not displayed on PDF

Hi
We have some embedded images (source on network share or on the webserver) on a dashboard. On the screen the images are displayed without problems.
But if we want to print the dashboard (f.e. PDF) the images are not printed. In html-view the images would be displayed.
Is there a known bug that images can't be printed on dashboard pages or do we have to embed them different?
Thank you

Hi Team,
I do face the same issue of image not displayed in only pdf output format. Our client has deployed OBIEE 10.1.3.4.1 using Weblogic application server and is accesible through a secured url access.
I have followed the fmap syntax to locate the image, also made sure the image is getting accessed through url, tried with different images of different sizes . In all cases the image display is appearing fine in HTML & Excel output. But not getting displayed only for pdf output.
Can you please help me with this regard if am missing any specific setup for pdf output. Is there is any pointers or documentation available to get around this issue.
Thanks in advance.

OBIEE 11G Embedded Image not displayed on PDF

Hi
I have some embedded images on a dashboard. On the screen the images are displayed without problems.
But if we want to print the dashboard (f.e. PDF) the images are not printed. In html-view the images would be displayed.
All the images are referenced with the fmap path.
Any way to print the images in the pdf ?
Thank you
obiee 11.1.1.5
O.S : Oracle Linux 5.6 x64

Hi Team,
I do face the same issue of image not displayed in only pdf output format. Our client has deployed OBIEE 10.1.3.4.1 using Weblogic application server and is accesible through a secured url access.
I have followed the fmap syntax to locate the image, also made sure the image is getting accessed through url, tried with different images of different sizes . In all cases the image display is appearing fine in HTML & Excel output. But not getting displayed only for pdf output.
Can you please help me with this regard if am missing any specific setup for pdf output. Is there is any pointers or documentation available to get around this issue.
Thanks in advance.

PreE V8: Clips not displaying in project view

I have a clip in the my timeline/sceneline that is not displaying in Project view. It also does not have the "P" in the bottom corner of the thumbnail in Organizer view. Why isn't the clip considered part of the project?

I have been shooting in XP+ mode and have been for the past year.
I haven't tried using the Premier Elements Get Media function. I usually import both still images from one camera and the video from this camera at the same time into the same Photoshop album and use Organizer. Also there are some training videos and books that tell you to use Organizer.
I tried importing a video file using the Get Media function and was able to use the set in/out points and have them saved correctly.
Then in the project that I am working on I took one of video files that I imported through the Organizer and deleted it from the catalog. Then I imported it using the Get Media function and put it in the album with the other files. Then I used Preview to set in/out points. Those points were saved correctly.
So know I will delete all the remaining video files from the catalog that I haven't yet used in my project and then remote them through Premiere's Get Media.
So it appears that as you thought, I need to use Get Media to import video files. But that is not emphasized in any documentation. I think there should be a warning when importing video files in Organizer saying that if you intend to use Premier Elements to edit them that they should be imported via that product.
Thank you for your assistance.

Some images not displayed on localhost

I just recently installed CF on my own computer as localhost with Apache. When I call a Coldfusion page in http://localhost/main.cfm it will show the text and some images. However, it will not show all the images. All the images are stored under the local htdoc/images, which should be http://localhost/images/myimage.jpg. The weirdest thing is that some small images are being displayed while the larger images are not being display in the main.cfm They are all being called the same way e.g. <IMG SRC="images/myimage.jpg"> or <IMG SRC="images/myimage2.jpg"> etc. Does anyone know why this is happening?
Also if I reference it directly http://localhost/images/myimage.jpg etc on the browser, it will display an error message that says "The image http://localhost/images/myimage.jpg" cannot be displayed because it contains errors". This happens to most images. The images will display on live site when I uploaded. So I am totally puzzled.

Since you’re using Apache, are you also using Linux (or OS X)? If so, note that those are case-sensitive. Make sure that’s not what’s tripping you up. Also, you can check your apache access logs to see what’s happening to the requests that it received, whether for image or other files. It will show the status code. Maybe they will show being 404 errors. You may also want to tight-click on an image, and choose to copy the image link, then past that in your browser and see what it may show. You may see errors there that you are NOT shown when the image is requested from within a page.
/charlie

JPG images not displayed correctly in Bridge and Photoshop (Mac OS)

(Note: I have copied the content of this query from the Creative Suites forum where I originally opened it.)
I am using CS4 under OSX 10.4.11 on a PowerMac G5 Quad with 23" Apple cinema display. Images which have been captured as JPG are displayed fine by Preview, but when opened in Bridge, Camera Raw or Photoshop. the colours are all "washed out". The attached screen capture should give an idea of the difference, with the upper being Camera Raw (image settings) and the lower being Preview. My monitor has been calibrated and I'm using sRGB IEC61966-2.1 colour space in Camera Raw and Photoshop. The colours displayed by Preview are pretty close to "real life". I find it virtually impossible to adjust the colours in Photoshop to get back to anything similar.
After opening the image in Photoshop without adjustment, and Save As JPEG with embedded color profile, Preview displays the new image the same as Photoshop. Save As JPEG without embedded color profile, and Preview displays this copy just like the original. It seems that Photoshop is making different (incorrect) assumptions about what color space to use when there is no embedded color profile. Shouldn't it assume sRGB like virtually everything else (http://en.wikipedia.org/wiki/SRGB)? Or is its interpretation of sRGB incorrect? How can I fix this?
Re: JPG images not displayed correctly in Bridge and Photoshop

xxxxyyyyz wrote:
…If there is someone out there who has experience of obtaining decent colour management in CS4 on a Power PC, I would really like to know how you achieved it.
That would be yours truly, and I hasten to reply because I may have some insights that can help you too.
Just get it it out of the way, here's my setup:
Photoshop 11.0.2 ("CS4"); VersionCue disabled and uninstalled.—2.5 GHz Power Mac (PPC) G5-Quad; 16GB RAM; mutant, flashed 550MHz nVidia GeForce 7800GTX 1,700MHz 512MB VRAM; ATTO ExpressPCI UL5D LP SCSI card; Mac OS X Tiger 10.4.11 and Leopard 10.5.8 boot drives; Spotblight, Dashboard and Time Machine permanently disabled; dual 22" CRT monitors; USB wireless 'n' available but connected to the Internet via wired Ethernet; 1 FW flatbed scanner; 2 SCSI scanners (one tabloid-size transparency scanner and a film scanner); various internal & external HDs; FW Epson 2200 and Ethernet Samsung ML-2850ND printers; 2 X Back-UPS RS 1500 XS units.
I can unambiguously and in good faith represent to you that my color management, from capture to print, is as spot-on as anyone with any kind of setup can hope to achieve. Unequivocally and without qualifications.
Now, first things first: Forget about trying to synchronize color management across the point applications lumped together only by Adobe marketing fiat into a variety of meaningless "creative suites". Concentrate on Photoshop. Do not try to use Bridge to synchronize anything.
The "suites" are a totally artificial construct created by Adobe bean counters and marketing types. The point applications (i.e. the individual programs clumsily bundled together, e.g. Photoshop, Illustrator, InDesign, etc.) are developed independently by separate engineering teams that are not only not in the same building, but in different cities, different states of the American Union, and even in different countries. They have very little communication among them, if any, as evidenced by repeated posts in these forums by Photoshop engineering staff urging us, the end users, to let the other teams know in their own forums that a given problem exists and is actually affecting our work.
Enough said about the cause of the problem. The end result is that Color Management is at very, very different levels of progress and sophistication in each individual point application, with only Photoshop fully entitled to be considered state of the art.
Secondly, a disclaimer: I have been hanging on to my CRT monitors and take care of them as Jascha Heifetz used to take care of his Stradivarius. I don't know what I will do if I manage to outlive the usefulness and accuracy of my CRTs (unlikely at this point). I have despaired in futile efforts to bring the luminosity of any LCD monitor down to where I would feel comfortable calibrating and profiling it. I believe my monitors are the foundation of my color management efforts.
Especially if you have one of the extreme wide-gamut LCD or LED monitors, you'll face an uphill battle.
Be careful to avoid any version 4 icc profiles, whether canned or generated by your calibration software. Stick to version2 icc profiles. Ask the manufacturer of your calibration software/hardware if in doubt.
Here are some not-too-recent, but thoroughly representative screen shots of the calibration results I obtain with my monitors, which I calibrate and profile often and regularly (I validate the calibration at least several times per month).
In a nutshell, my color management practices and settings mirror those described by Bruce Fraser, Jeff Schewe, Andrew Rodney and Gary Ballard's site. I have learned from all of them.
My working color space is ProPhoto RGB. I choose to work with PSD and PSB files. As a long-time, rabid JPEG hater, I only rarely deal with JPEGs, using them sporadically to illustrate a point in this forum or elsewhere in the web. My main output consists of prints.
I only deal with tagged image files (files with an embedded color profile) and often recommend beating up with a baseball bat any moron that hands you an untagged file—figuratively of course, but I find the expression gets my point across unambiguously.
Following is a screen shot of some of my pertinent settings:
Note that I have never bought into the "suite" concept myself. I do have and routinely use Adobe Illustrator 10.x, InDesign 2.x and Acrobat Professional 8.x, but they are all older, independent versions of each point application, licensed at different times.
Be further advised, that the answer to many problems offered by Adobe engineers often is not to install VersionCue, or uninstall it, or at least disable it.
Also, as outlined at the beginning of this post, concentrate on Photoshop, not on synchronizing applications that can't really communicate with each other, despite the claims of Adobe marketing hacks to the contrary.
One big caveat, do not fall into this trap:
xxxxyyyyz wrote:
…I believe my problem has nothing to do with my monitor profile, for several reasons, but…
…It seems extremely unlikely to me that…
You either want to learn, or you don't. You either want to solve your problems, or you don't.
When you start arguing instead of studying, questioning advice instead of following it and detecting where you went wrong, you're on the right track to nowhere. That attitude will get you there fast. Remember you are the one with the problem, and only you can acquire the discipline to learn how to solve it.
Go ahead and ask me anything that is not clear, just don't argue with me please, and don't tell me why you think Fraser, Rodney, Ballard and I are wrong. You see, I am not experiencing any problem that needs fixing. I have an interest in helping you, but not in hearing about your speculations, theories or conclusions.
Good luck.
Wo Tai Lao Le
我太老了

CF slows down to a halt ... images not displaying

My primary laptop on which I do all coding ...
- less than 1 year old
- Dell (cough) XPS M1730
- Windows XP (latest)
- ColdFusion Ver 8, developer edition.
- No other issues with laptop
Also running
- SQL 2000
- Synergy
- Anti virus etc. changed Norton daily scan and unaware that I have picked up any viruses - I was my hands very well and often
Over 6 months gradually CF has been slowly not display internal referenced <img src> tags. External work fine.
To the point now where most in our app do not display.
Then in the past 3-4 days a lot of pages when called give Firefox or IE errors:
Page will not display with too may users error.
But there aren't any others.
I go to all other web site, no issues with speed.
I just cold warm booted the machine and now while page 1 appears, page 2, login, takes minutes to appear. But on a beta server (also developer edition) it's instant.
When I go straight into the browser, it works fine, albeit no images, crashes with a known bug (missing application variable), fix it, then resume, then just sits there forever.
And there's no difference between the two machines ... well, not in "that" way.
Adding to my confusion is ... I cannot get into the CF Admin panel.
I can see it approve me, then it just spins.
Nothing has changed on machine in past weeks EXCEPT traveling when I sign in to the usual plethora of wifi and other networks but never had a problem - except luggability
I am thinking of, UGH, reinstalling Windows ... but why bother if it's working perfectly and only ColdFusion has an issue.
Now COLD booted machine for 5 minutes.
Everything seems better except CF still a BIT sluggish and still not "drawing" most images. Able to access Admin panel. Even if there images not displaying.
Anyone any ideas?

Thanks for your prompt reply ...
We scoured for a folder like that and found none.
What we DID find is that over the years of coding, we have a template count of 3,500 files in 130 folders, but the root where we start is about 1,500 files. 144 megs total size though.
That shouldn't be too much? Esp as our beta and production servers are using the same amount with no issues.
Admittedly production is CF 7.X.
Much more powerful machines but still.
It would have made sense as that is the only thing on the machine that has "grown" ... but no luck.
Does remind me of the day when our mail server got hacked and we had 100,000 outbound in the spool. That was fun.: :)

Image not displaying in the Task Sequence Wizard. SCCM2012

This is my question, so I will post the link here.
http://community.spiceworks.com/topic/925727-image-not-displaying-in-the-task-sequence-wizard-sccm2012
Bryan
I captured an image from a PC that I am preparing to be deployed with Office 365. Once I captured
the image, I went to the software library to add the operating system image. That seemed to go on without any issue, but when I look at the summary, I see the big yellow globe saying "in progress" it has not changed since yesterday afternoon.
I then created the task sequence for this image
to be deployed under Software Library, Task Sequences. When I selected the references tab, everything seemed to be in order with the exception of the "operating system image" under type. It was/is showing 0.0% Compliance.

So, the problem described in the other forum post does not match the title of this thread. Are you trying to address two different things? These are unrelated btw.
For the issue in the other thread, you'll have to troubleshoot your content distribution to the selected DP. The distmgr.log and pkgxfermgr.log (assuming you chose to distribute the image to a DP directly attached to your primary site) are the places to
start and will show you exactly what's going on.
As for the title of this thread, we'll need a lot more info to help you there.
Finally, I would suggest you copy your questions from other sources into the thread -- this will help other folks in the future that may stumble upon this thread and will prevent any confusion.
Jason | http://blog.configmgrftw.com | @jasonsandys

Design Window is not displaying the correct view

Hi
For some reason the Design View on my CS3 is not displaying
the correct view.
It used to show how the web page would look but it is simply
showing up the wording and pictures surrounded by dotted black
lines.
I am using a template as a bases for all the pages and all
the pages are showing like this.
My other sites are showing up OK though.
When I Preview in Browser, it all shows up OK.
Can anyone help?
Bezz

VIEW | Style Rendering > Display Styles
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Bezz333" <[email protected]> wrote in
message
news:fttdsr$394$[email protected]..
> Hi
>
> For some reason the Design View on my CS3 is not
displaying the correct
> view.
>
> It used to show how the web page would look but it is
simply showing up
> the
> wording and pictures surrounded by dotted black lines.
>
> I am using a template as a bases for all the pages and
all the pages are
> showing like this.
>
> My other sites are showing up OK though.
>
> When I Preview in Browser, it all shows up OK.
>
> Can anyone help?
>
> Bezz
>

BT Cloud - images not displaying in BT Cloud View

I have had an issue several times now with image thumbnails not displaying in BT Cloud View. All I get is a green or grey icon/tile. It is not all the images - just some of them - and they will open OK and display in a photo viewer.
Images display OK on the web version of BT Cloud - just not in BT Cloud View.
Any ideas how to force a refresh to get the thumbnails to show?

I used to see quite a lot of thumbnails/photos not showing correctly in the web interface, and now all that I have just checked seem to be OK.
Unfortunately, due to another BT Cloud bug I can't see most of my photos in the PC client. (see http://community.bt.com/t5/Other-BB-Queries/BT-Cloud-another-curious-bug/m-p/830660#U830660 )
Maybe (???) there was a parallel bug in both web and client versions which they have fixed on the web side, but not yet deployed into a new version of the client? In which case the problem will go away when they do update.

Images not displayed at all in Lightroom 1.4.1

Hi,
I have recently had a problem with Lightroom where all the images are not displayed. The grey tiles are displayed with the filename and the keywords all show up in the right menu however I cannot see any of the images in any module. Also the grid view is random (i.e. not a grid) just shows a blank tile whereever the mouse is. The original image files are OK and can be read in Windows and other applications. The lightroom edits are obviously missing.
This happens with my live database, with a previous backup so I am thinking it is not a corrupt catalog. Unless opening backup catalogs causes them to be corrupted.
I have uninstalled and re-installed, tried version 1.3.1, 1.4 and 1.4.1 with the same results.
The only recent change to the setup was that I imported all my historical images to lightroom. These are archived as DNG and this took me to >10000 images.
The problem occurs with CR2 (Canon 400D and 40D) JPG and DNG images. I have not tried any other formats.
This is causing me a major problem as I have clients waiting for their images so a fast response would be great. For Adobe's benefit - I was going to purchase LR2 but the reviews said it was slower and now I have this issue I am seriously considering using another application.
Thanks
Alex

Are you on Windows? If so,
try this.

Random Image not displaying in Live View.

Similar Messages

Maybe you are looking for