Editing disabled in Live View
I've been scouring the web trying to figure out why I'm unable to edit thing in Live View with Dreamweaver CC. When I click the Live button everything in Properties and Insert etc. is disabled. All the tutorials I've seen for Dreamweaver CC everyone is adding/subtracting elements in the Live View but for me it's all greyed out and not possible. I've looked for options to enable editing in live view, but I can't find it anywhere in dreamweaver. Please help!
Live View editing is only available in CC 2014.1 (October release).
If you have an earlier version, CC 2014 or CC 13, you won't have that option.
New Features in CC 2014 June Release
http://helpx.adobe.com/dreamweaver/using/whats-new-2014.html
New Features in CC 2014.1 October Release
http://helpx.adobe.com/dreamweaver/using/whats-new.html
Nancy O.
Similar Messages
-
Page not displaying - cannot edit - ok in live view
I have jsut upgraded to Dreamweaver CS 5.5 - Windows 7 - My site used to work fine in Dreamweaver CS4 - I have a template with editable regions and lots of divs - wehn I ope the page in CS 5.5 - it shows the backgroudn [which repeats ] but none of the editable text
teh page can be found at www.fcrsafield.com/list.hmtl
The page displays correclty in live view - I've tried turning off"style renderign" and that allowed me to see my content and to edit it - but as soon as I saved teh file - it all disappears again - but it is there in live view .
Any help is apreciated as I have more than 100 pages built on this template.I'm surprised the page shows up at all in any browsers. You've got some very whacky CSS rules. I cleaned up the obvious stuff and removed what didn't seem to belong.
@import url("../p7pm/p7pmh11.css");
body {
font-family: Geneva, Arial, Helvetica, sans-serif;
font-size: 16px;
text-align: left;
background: url(../images/patternDetailsMax401.jpg) fixed;
#pagecontainer {
width: 1000px;
margin:0 auto;
overflow:hidden; /**to contain floats**/
#top {
background-color: #cdc9a5;
border: thick outset #b1a999;
#middle {
background-color: #b1a999;
width: 1000px;
margin:0 auto;
#navbar {
text-align: center;
padding-top: 1%;
margin-top: 10px;
#content {
clear:both;
background-color: #FFFFFF;
margin:25px 0 0 0;
padding-right: 2%;
padding-left: 2%;
border: thick outset b1a999;
#footer {
background-color: #Cdc9a5;
margin-right: 4%;
margin-left: 4%;
border: thick outset #b1a999;
margin-bottom: 6%;
/**use meaningful names, no idea what this is for**/
.style16 {color: #FF0033}
.style17 {
font-family: Georgia, "Times New Roman", Times, serif;
font-size: 4em;
font-weight: bold;
font-style: italic;
color: #000000;
text-align: center;
margin-bottom: 10px;
.style18 {font-size: 10px}
A must read:
How to Develop with CSS?
http://phrogz.net/css/HowToDevelopWithCSS.html
Finally, I highly recommend using one external CSS file in your Template.dwt. It's much easier to manage and creates less code on your HTML pages.
http://alt-web.com/DEMOS/DW-Link-Stylesheet.shtml
Good luck.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com/ -
I am teaching a course in Dreamweaver 2014.1.1
We are setting up templates in fluid grids.
We need to make regions editable.
The LIVE view replaced the DESIGN view and does not have certain options accessible anymore.
I can't find the command to access the dropdown panel to make a region editable.
The Template tab at top, and the make editable options subtab, will not come open in fluid grid template mode.
Does anyone have a way to do this?I was under the impression that the February update (2014.1.1) released a few days ago had fixed these problems. I urge you to file an official bug report below.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
My advice for now is to stay away from Fluid Grid Layouts. But if that's not an option, I'll show you a trick for getting Design View back. Open the Fluid Grid CSS file and add an X as shown below. This tricks DW into thinking it's a normal layout.
Dreamweaver Fluid Grid Properties
dw-num-cols-mobile: X 4;
dw-num-cols-tablet: 8;
dw-num-cols-desktop: 12;
dw-gutter-percentage: 25;
=====================================
Once saved, you should see Design View as an option.
Nancy O. -
According to a web and support forum search, myself and another person, Chloe in the Dreamweaver Club forum, have ever reported this. Trying to follow along a Lynda.com tutorial, and the instructor isn't getting this error. Can't imagine why it's happening. I'd be very grateful for any help. I'm also getting an error dialog message:
DIALOG BOX:
While executing onClick in InsertFGDiv.htm, the following JavaScript error(s) occurred:
At line 687 of file "Macintosh HD:Applications:Adobe Dreamweaver CC 2014.1:Configuration:Commands:InsertFGElement.js": The object is not currently contained in a document.
This appears at the top of the screen:
Couldn't commit the changes made in Live View. Refresh the Live View and try editing again. [Refresh doesn't do anything.]Try the suggestions here -
Index to Dreamweaver FAQ
The solution for Javascript errors is likely the one. -
Cannot edit using DW in live view.
Normally I write exclusively using an IDE in plain code, but have to deal with some HTML email designing and it is easier to develop these in a GUI editor. This is a plain HTML document, no javascript, no attached CSS even. It's all structurally correct to the declared doctype as well.
Whenever I make any edit in live view, even something as trivial as adding a space or a comma, I get an error: "Couldn't commit the changes made in live view. Refresh the live view and try editing again." No matter what I do, the same error occurs.
I am able to edit in the code section of split view or just plain code. This error only happens in live view.
I searched all over and can't find any help on this error. There's no further information in DW, just the above error message, which is more or less worthless from a debugging perspective. What's equally frustrating is Adobe decided that in the event of this error, they would just revert any changes that I've made to the document. I found this out after typing around 800 words which were irrecoverably erased, absolutely ridiculous error handling.
Anyway, this is a brand new installation of Dreamweaver CC. This is the only document I've ever loaded into it. I've also tried restarting and have made sure the document wasn't open in another program or locked or something similar.
System info.
Win 7 _64
Ton of RAM
i7 3.6 Ghz processor
All of my other creative suite apps work fine.I haven't seen that error yet (Live View Editing is still pretty new in DW), I don't really like the Live View Editor though due to all of the functionality Adobe forgot to add.
Does it work in Design View?
Click the triangle next to the Live View button and choose Design View from the drop-down. -
Pages which base on a Business Catalyst template are not editable in Live-View?
As long as the page is not a template, all these neat new edit-features of Dreamweaver work without problems. But as soon as I create a template and define an editable region with the Business Catalyst Tag {tag_pagecontent}, the content put inside this regions is no longer editable in Live-View. Is this a bug or has it just been forgotten to implement?
Pleaes restate your problem's symptoms, and include some code
to
demonstrate.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Cole_Marie" <[email protected]> wrote in
message
news:en3lqg$3jk$[email protected]..
> Did you ever resolve this issue. I'm having the same
problem. Using DW8
> , XP. -
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.comWhen 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">
<!--
<oa:widgets>
<oa:widget wid="2127022" binding="#gallery" />
</oa:widgets>
-->
</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> -
Design view problem, live view fine
I'm having a design view issue in Dreamweaver CS4. If you look at the images here:
http://www.honestcontractors.net/temp/index.html
You can see that design view (top image) cuts off the bottom CSS and the right area. But everything looks just fine in live view (lower image). Anyone have any ideas why this is going on?
Thanks!Me too! I also have upgraded from DW8 to CS5 and have this problem and it is driving me crazy. I have run my pages through the W3C validator and they passed, so I know there is nothing wrong with my code. But the XHTML pages are all displaying flush left in Design View, and intermittently so are some of the HTML pages. They display fine in Live View, but of course, you can't do any editing in Live View. This to me disables one of the key features of Dreamweaver since it was launched by Macromedia years ago -- the ability to switch seamlessly back and forth between Code View and Design View! I've been working with it like this for several years and this has thrown a monkey wrench into my workflow and I'm really depressed. The Adobe phone tech in India was trying to tell me it was my fault! I showed him that the pages passed the W3C validator test and displays just fine in Firefox and Safari when uploaded to the server.
Meanwhile, there are other bugs the Adobe phone tech basically threw up his hands about: browser preview works with Safari but not Firefox (it just doesn't open at all, nothing happens). Also, sometimes after interacting with the server, the dialog box doesn't close on its own, so you go to open a file a minute or two later, and you are told that "Dreamweaver is currently interacting with a server." Since the dialog box is hidden, this has also been driving me nuts for the past week until I realized what the cause was.
I am SO frustrated right now. This is a very, very expensive program, and it should be working better than DW8 not lacking key features. Any other suggestions? And what's with Adobe's current phone techs? I've talked with 3 of them about this issue. The first one spoke fractured English, the second one seemed competent to a point, the third one had decent language skills but I felt as if I had better reasoning skills and knew more than he did -- and he was the one who punted and said "Must be the fault of your design," even though he could see my screens and I showed him that the design passed validation.
By the way Tech # 2 had me delete the configuration files and preferences and uninstall and reinstall DW CS5 to no avail. And I'm running the latest update of Snow Leopard on a Mac Mini purchased in November 2009.
--Helen -
How do I use Dreamweaver CC 2014.1 Live View to copy complex formatted text into web page?
Since Design View has been removed from Fluid Grid Layouts, and could be removed completely in next upgrade, I cannot use Live View to place complex text into my web pages.
Our business requires the listing of complex job descriptions on our web pages. Design View worked fine, Live View does not. Both examples are noted below.
Using Design View the web page rendered this way:
Research & Analytics Director
Position# 2469
Location: Midwest
Education Requirements: MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS.
Other Requirements: Include:
Job Competencies:
Achieve Results.
Be Accountable.
Lead Change.
Lead Corp Vision & Strategy.
Lead People.
Maximize Customer Experience.
Specialized Knowledge and Skills Requirements:
Demonstrated ability to develop strategic partnerships.
Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues.
Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners.
Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets.
Demonstrated experience in public speaking and use of appropriate presentation skills.
Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders.
Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models.
Demonstrated experience with statistical and modeling software tools, such as SAS or R.
Demonstrated management or leadership experience.
Solid knowledge and understanding of mathematical modeling and research.
Salary Range: $146,300 to $243,800+
Description: This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives. Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects. Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques. Monitors industry trends in analytics and investigates new concepts, ideas, and data sources. Primary accountabilities include:
Advanced Analytics Oversight (40%):
Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions.
Directs the most complex and vital analytics work critical to the organization.
Oversees advanced exploratory analytics that produce a variety of business solutions.
Conducts peer review on technical aspects of projects.
Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation.
Portfolio Strategy and Management (25%):
Collaborates with Strategic Data & Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio.
Leverages business acumen and domain expertise in directing advanced analytics strategy and application.
Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle.
Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives.
Works with divisional management to improve work processes that impact work environment and divisional resources.
Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project. Oversees measurement, monitoring and reporting of project progress and resource utilization. Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives.
Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business. Ensures rapid delivery and execution of insights derived from data analytics into the organization.
Analytic Tools and Techniques Research Oversight (15%):
Sets the vision for the use of new and innovative tools and technology.
Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department.
Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements.
Strategies Linked to the Division's Business Goals/Results (10%):
Establishes, communicates, and implements departmental plans, objectives, and strategies.
Participates as a member of the Management Team.
Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making.
Management/Leadership for Department or Unit (10%):
Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices.
Prepares and analyzes department/unit plans and reports.
Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area.
Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications.
Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance & development plans.
Using Live View the web page rendered this way:
Research & Analytics Director Position# 2469 Location: Midwest Education Requirements: MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS. Other Requirements: Include: • Job Competencies: o Achieve Results. o Be Accountable. o Lead Change. o Lead Corp Vision & Strategy. o Lead People. o Maximize Customer Experience. • Specialized Knowledge and Skills Requirements: o Demonstrated ability to develop strategic partnerships. o Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues. o Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners. o Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets. o Demonstrated experience in public speaking and use of appropriate presentation skills. o Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders. o Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models. o Demonstrated experience with statistical and modeling software tools, such as SAS or R. o Demonstrated management or leadership experience. o Solid knowledge and understanding of mathematical modeling and research. Salary Range: $146,300 to $243,800+ Description: This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives. Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects. Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques. Monitors industry trends in analytics and investigates new concepts, ideas, and data sources. Primary accountabilities include: • Advanced Analytics Oversight (40%): o Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions. o Directs the most complex and vital analytics work critical to the organization. o Oversees advanced exploratory analytics that produce a variety of business solutions. o Conducts peer review on technical aspects of projects. o Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation. • Portfolio Strategy and Management (25%): o Collaborates with Strategic Data & Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio. o Leverages business acumen and domain expertise in directing advanced analytics strategy and application. o Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle. o Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives. o Works with divisional management to improve work processes that impact work environment and divisional resources. o Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project. Oversees measurement, monitoring and reporting of project progress and resource utilization. Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives. o Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business. Ensures rapid delivery and execution of insights derived from data analytics into the organization. • Analytic Tools and Techniques Research Oversight (15%): o Sets the vision for the use of new and innovative tools and technology. o Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department. o Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements. • Strategies Linked to the Division's Business Goals/Results (10%): o Establishes, communicates, and implements departmental plans, objectives, and strategies. o Participates as a member of the Management Team. o Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making. • Management/Leadership for Department or Unit (10%): o Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices. o Prepares and analyzes department/unit plans and reports. o Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area. o Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications. o Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance & development plans.
Obviously, as seen above, I'm doing something wrong or Live View does not do all the functions that Design View use to do. I realize I can still access Design View in non-Fluid Grid Layout documents and that is my current work-around. I copy from my Word file into Design View available in non-Fluid, then copy that code into my Fluid Grid Layout document, not real efficient use of my time. And, even that work-around may not be available after the next upgrade.Hans thank you for your reply and attention to this matter. Moreover, with your steeped expertise I do not, in any fashion, intend to be flippant or capricious.
However, I do not believe the reply is on point since I'm not discussing the insertion of an HTML tag/element; but rather, the placing of complex formatted text into my various web pages.
Design View and 2014.1 Live View seem to serve different functions. That is, Design View, for us, serves as a highly sophisticated HTML5 code generator that allows us to properly display complex formatted text that originally is created as a Word docx file. As I noted in my original post, the complex formatted text from the Word file is then pasted into Design View and thus properly renders on the web page. I invite you to try this yourself. Simply copy my properly formatted text in my original post (that can be found at "Using Design View the web page rendered this way:") to a Word file, and it will retain the complex formatting, then copy that Word file text to both Design View and 2014.1 Live View files. Please apprise me of your results.
Discussion has been had in at least two separate threads on the Design View disappearance in Fluid Grid. In https://forums.adobe.com/thread/1597260 staff member Lalita wrote "It would be helpful for us if you list the issues you are seeing with fluid grid live view editing." And in https://forums.adobe.com/message/6807088#6807088 staff member Subhadeep wrote "If you can list down the workflows you are trying while editing in Live View & the issues you are facing in doing so, it will help us understand what is amiss & suggest alternative workflows to do the same." I believe I've pointed out issues when attempting to use Live View for functions or work flow that customarily had been done in Design View.
Being a CC subscriber, if someone can provide me with a workflow using other additional Adobe products to get my complex formatted text from Word ultimately to my Dreamweaver web page, be it an image insert or whatever, I would take the suggestions.
The difference in the coding of my example in my original post is as follows.
Code when using Design View is:
<p><strong>Research & Analytics Director</strong><br>
<strong>Position# 2469</strong><br>
<strong>Location:</strong> Midwest<br>
<strong>Education Requirements:</strong> MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS.<br>
<strong>Other Requirements:</strong> Include:</p>
<ul type="disc">
<li>Job Competencies:</li>
<ul type="circle">
<li>Achieve Results.</li>
<li>Be Accountable.</li>
<li>Lead Change.</li>
<li>Lead Corp Vision & Strategy.</li>
<li>Lead People.</li>
<li>Maximize Customer Experience.</li>
</ul>
<li>Specialized Knowledge and Skills Requirements:</li>
<ul type="circle">
<li>Demonstrated ability to develop strategic partnerships.</li>
<li>Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues.</li>
<li>Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners.</li>
<li>Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets.</li>
<li>Demonstrated experience in public speaking and use of appropriate presentation skills.</li>
<li>Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders.</li>
<li>Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models.</li>
<li>Demonstrated experience with statistical and modeling software tools, such as SAS or R.</li>
<li>Demonstrated management or leadership experience.</li>
<li>Solid knowledge and understanding of mathematical modeling and research.</li>
</ul>
</ul>
<p><strong>Salary Range:</strong> $146,300 to $243,800+<br>
<strong>Description:</strong> This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives. Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects. Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques. Monitors industry trends in analytics and investigates new concepts, ideas, and data sources. Primary accountabilities include:</p>
<ul type="disc">
<li>Advanced Analytics Oversight (40%):</li>
<ul type="circle">
<li>Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions.</li>
<li>Directs the most complex and vital analytics work critical to the organization.</li>
<li>Oversees advanced exploratory analytics that produce a variety of business solutions.</li>
<li>Conducts peer review on technical aspects of projects.</li>
<li>Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation.</li>
</ul>
<li>Portfolio Strategy and Management (25%):</li>
<ul type="circle">
<li>Collaborates with Strategic Data & Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio.</li>
<li>Leverages business acumen and domain expertise in directing advanced analytics strategy and application.</li>
<li>Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle.</li>
<li>Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives.</li>
<li>Works with divisional management to improve work processes that impact work environment and divisional resources.</li>
<li>Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project. Oversees measurement, monitoring and reporting of project progress and resource utilization. Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives.</li>
<li>Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business. Ensures rapid delivery and execution of insights derived from data analytics into the organization.</li>
</ul>
<li>Analytic Tools and Techniques Research Oversight (15%):</li>
<ul type="circle">
<li>Sets the vision for the use of new and innovative tools and technology.</li>
<li>Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department.</li>
<li>Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements.</li>
</ul>
<li>Strategies Linked to the Division's Business Goals/Results (10%):</li>
<ul type="circle">
<li>Establishes, communicates, and implements departmental plans, objectives, and strategies.</li>
<li>Participates as a member of the Management Team.</li>
<li>Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making.</li>
</ul>
<li>Management/Leadership for Department or Unit (10%):</li>
<ul type="circle">
<li>Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices.</li>
<li>Prepares and analyzes department/unit plans and reports.</li>
<li>Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area.</li>
<li>Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications.</li>
<li>Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance & development plans.</li>
</ul>
</ul>
Code when using Live View is:
<div id="liveview" class="fluid">Research & Analytics Director Position# 2469 Location: Midwest Education Requirements: MS degree in Mathematics, Statistics, Economics, Engineering, Actuarial Science or related field or equivalent designation, such as FCAS. Other Requirements: Include: • Job Competencies: o Achieve Results. o Be Accountable. o Lead Change. o Lead Corp Vision & Strategy. o Lead People. o Maximize Customer Experience. • Specialized Knowledge and Skills Requirements: o Demonstrated ability to develop strategic partnerships. o Demonstrated ability to identify potential issues, and to proactively work to the mitigation of those issues. o Demonstrated experience communicating business implications of complex data relationships and results of statistical models to multiple business partners. o Demonstrated experience formulating, approaching, and solving problems in massive, complex datasets. o Demonstrated experience in public speaking and use of appropriate presentation skills. o Demonstrated experience interfacing with business clients and driving solution discussions with both IT and business stakeholders. o Demonstrated experience performing advanced statistical analysis, including generalized linear models, decision trees, neural networks, etc., to discover business insights and develop predictive models. o Demonstrated experience with statistical and modeling software tools, such as SAS or R. o Demonstrated management or leadership experience. o Solid knowledge and understanding of mathematical modeling and research. Salary Range: $146,300 to $243,800+ Description: This position is responsible for oversight and strategic direction of advanced analytics, including predictive modeling, that drive business performance consistent with company goals and objectives. Works with internal business partners to understand and validate scope of advanced analytics projects and directs projects teams to support those projects. Collaborates within the division and cross-divisionally to develop and integrate statistical models into various processes. Oversees research of new and innovative analytic tools and techniques. Monitors industry trends in analytics and investigates new concepts, ideas, and data sources. Primary accountabilities include: • Advanced Analytics Oversight (40%): o Provides oversight and direction for the design, development, and evaluation of predictive models and advanced algorithms that lead to business solutions. o Directs the most complex and vital analytics work critical to the organization. o Oversees advanced exploratory analytics that produce a variety of business solutions. o Conducts peer review on technical aspects of projects. o Partners with business areas (Commercial Lab, EDM, IS, etc.) on data innovation. • Portfolio Strategy and Management (25%): o Collaborates with Strategic Data & Analytics Vice President as well as business partners internal and external to the division to develop and execute advanced analytics strategy and project portfolio. o Leverages business acumen and domain expertise in directing advanced analytics strategy and application. o Aligns plans to divisional and corporate objectives/goals and integrates within the corporate planning cycle. o Monitors and analyzes advanced analytics resources. Assesses needs and appropriately allocates resources to priorities and initiatives. o Works with divisional management to improve work processes that impact work environment and divisional resources. o Provides overall portfolio/project management oversight and direction for a variety of advanced analytics project. Oversees measurement, monitoring and reporting of project progress and resource utilization. Manages project resources to ensure timely delivery of projects consistent with divisional goals and objectives. o Coordinates with business partners (Analytics Strategy, etc.) on knowledge management and participates in business area meetings. Maintains holistic view of the business. Ensures rapid delivery and execution of insights derived from data analytics into the organization. • Analytic Tools and Techniques Research Oversight (15%): o Sets the vision for the use of new and innovative tools and technology. o Maintains and fosters an industry awareness of new developments in analytics techniques and tools, and ensures quick execution in their use within the department. o Interfaces with Enterprise Data Management (EDM) and Information Services (IS) on evolving technological and data needs and requirements. • Strategies Linked to the Division's Business Goals/Results (10%): o Establishes, communicates, and implements departmental plans, objectives, and strategies. o Participates as a member of the Management Team. o Maintains an active awareness of our Client's business environments, corporate culture, and structure to support key decision-making. • Management/Leadership for Department or Unit (10%): o Manages direct reports, systems, and projects to achieve department/unit goals in accordance with Company policies and practices. o Prepares and analyzes department/unit plans and reports. o Provides leadership by exhibiting influence and expertise, thus affecting the results of the operating area. o Creates an effective work environment by developing a common vision, setting clear objectives, expecting teamwork, recognizing outstanding performance, and maintaining open communications. o Develops staff through coaching, providing performance feedback, providing effective performance assessments, and establishing performance & development plans. </div>
It is readily apparent that Design View is a much needed code generator in the Dreamweaver product. Live View serves completely other, and needed, purposes. Therefore, I still, after all the forum discussions, do not understand why Design View has been removed from Fluid Grid.
Again Hans thank you for your reply. But unless I'm missing something, citation to the links you provided does not solve my problem. And that problem is this: If Design View is on its way out and thus will be completely removed from Dreamweaver at some point, then how do I provide my information (i.e. complex executive job descriptions) on my website?
Apparently a vote is taking place https://forums.adobe.com/ideas/3922 on the issue of placing Design View back into Fluid Grid. I do not understand why the need for two rather disjunctive functionalities are at the mercy of the democratic process. These are matters of engineering principles not "town hall gatherings". -
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><!-- InstanceBegin template="/Templates/pavemend_website1.dwt" codeOutsideHTMLIsLocked="false" -->
<head>
<meta charset="UTF-8">
<!-- InstanceBeginEditable name="doctitle" -->
<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>
<!-- InstanceEndEditable -->
<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>
<!-- InstanceBeginEditable name="head" -->
<!-- InstanceEndEditable -->
</head>
<body>
<div id="wrapper">
<div class="container">
<div id="apDiv1"><!-- InstanceBeginEditable name="HeaderLogo" --><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>
<!-- InstanceBeginEditable name="Header" -->
<div class="headerResources"></div>
<!-- InstanceEndEditable -->
<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>
<!-- InstanceBeginEditable name="Sidebar" -->
<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>
<!-- end .sidebar1 --> </div>
<!-- InstanceEndEditable -->
<!-- InstanceBeginEditable name="Content" -->
<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>
<!-- end .content --></div>
<!-- InstanceEndEditable -->
<div class="footer"><!-- InstanceBeginEditable name="Footer Logo" --><img src="_images/NEW 2012 PAVEMEND LOGO WHITE.png" width="160" height="64" class="flt_rgt" /><!-- InstanceEndEditable -->
<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>
<!-- end .footer --></div>
<!-- end .container --></div>
</body>
<!-- InstanceEnd --></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; -
Internal Server Error; Live View not working...please help:)
I am a beginner doing a tutorial through David Sawyer McFarlands' "CS5: The Missisng Manual. I have MAMP set up and working fine. I just got through doing a tutorial on editing a recordset and linking to a Detail page. I have used Live View just a few minutes ago and it was working fine. However I just tried to click live view again after completing this part of the tutorial and a pop up box says "dynamically-related files could not be resolved because of an internal server error". I have no idea what this error could be. When I type http://localhost/ in my browser it shows a file on the dynamic website we are working on called cosmo_shop. But when I type http://localhost/cosmo_shop the screen goes blank....Can someone help me with this???
frankieb83 wrote:
I have no idea what this error could be. When I type http://localhost/ in my browser it shows a file on the dynamic website we are working on called cosmo_shop. But when I type http://localhost/cosmo_shop the screen goes blank....Can someone help me with this???
Nobody else is likely to have any idea what the error is without seeing the code of the page you're working on. However, you might find Why is my PHP page blank? in the Dreamweaver FAQ points you in the right direction.
Since you're new to these forums, you might also like to take a look at How to get help quickly. -
When using Live View, site looks great, browser testing goes crazy
I am creating a new website (and I am really unexperienced with Dreamwaver CS5). But when I check my site using "Live View" everything looks great, the way it is supposed to. Then when I go to test it in my browswer (Primary browser is Chrome) it goes crazy: I at first noticed that I had saved one copy as an .asp but then resaved it to .xhtml I did delete the first line of code already that the .asp file created as it kept giving me an error on line 1.
Then I tried to do a spry drop-down menu bar, which I have deleted since I thought I was doing something wrong with that and I should just stick to what I half-way know.
If I were to preview the template page it gives me this error:
This page contains the following errors:
error on line 150 at column 76: error parsing attribute name
Below is a rendering of the page up to the first error.
Here is line 150:
if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
If I were to test the index.xhtml page in the browser, it ignores most images (all but one), and the first nav-bar (an editable region) appears to the left instead of under the header. The layout is totally ignored and everything is on the left-hand side of the screen instead of in a two column layout.
I am not testing this on a server just off of my computer.
I am assuming that the error has something to do with the .asp file I first did and when I resaved it, since I don't know what I would be looking for, is still in there screwing it up.
Here is the code from the template page:
<!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" />
<!-- TemplateBeginEditable name="doctitle" -->
<title>Midwest Window Brokers | Page</title>
<!-- TemplateEndEditable -->
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
<style type="text/css">
<!--
body {
font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
margin: 0;
padding: 0;
color: #000;
background-image: url(/images/bkg.jpg);
background-repeat: repeat;
/* ~~ 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;
h1, h2, h3, h4, h5, h6, p {
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: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
text-align: left;
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: #060;
text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
a:visited {
color: #666;
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;
/* ~~this fixed width container surrounds the other divs~~ */
.container {
width: 960px;
background: #FFF;
margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
/* ~~ 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: #FFF;
/* ~~ 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: 300px;
background: #ffffff;
padding-bottom: 10px;
.content {
padding: 10px 0;
width: 650px;
float: right;
/* ~~ This grouped selector gives the lists in the .content area space ~~ */
.content ul, .content ol {
padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
/* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
ul.nav {
list-style: none; /* this creates the space between the navigation on the content below */
ul.nav li {
border-bottom: 1px solid #666; /* this creates the button separation */
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: #DDDECB;
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: #ADB96E;
color: #FFF;
/* ~~ The footer ~~ */
.footer {
padding: 10px 0;
position: relative;/* this gives IE6 hasLayout to properly clear */
clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
background-color: #DDDECB;
font-size: small;
/* ~~ 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: right;
margin-left: 8px;
.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;
#h-navbar {
font-weight: bold;
height: auto;
font-size: 18px;
line-height: 50px;
background-image: url(/images/navbar2.jpg);
#h-navbar1 {
background-image: none;
background-repeat: repeat-x;
-->
</style>
<script type="text/javascript">
function MM_preloadImages() { //v3.0
var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
function MM_swapImgRestore() { //v3.0
var i,x,a=document.MM_sr; for(i=0;a&&i<a.length&&(x=a[i])&&x.oSrc;i++) x.src=x.oSrc;
function MM_findObj(n, d) { //v4.01
var p,i,x; if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
if(!x && d.getElementById) x=d.getElementById(n); return x;
function MM_swapImage() { //v3.0
var i,j=0,x,a=MM_swapImage.arguments; document.MM_sr=new Array; for(i=0;i<(a.length-2);i+=3)
if ((x=MM_findObj(a[i]))!=null){document.MM_sr[j++]=x; if(!x.oSrc) x.oSrc=x.src; x.src=a[i+2];}
</script>
</head>
<body onload="MM_preloadImages('/images/home2.jpg')">
<div class="container">
<div class="header"><a href="/index.xhtml"><img src="../images/heading.jpg" alt="Midwest Window Brokers, Windows, Siding, Roofing, 605-791-5352" name="Insert_logo" width="950" height="200" align="right" id="Insert_logo" style="background: #FFFFFF; display:block;" /></a>
<div id="h-navbar1"><a href="/index.xhtml"><img src="/images/home.jpg" alt="home" width="159" height="51" id="Image1" onmouseover="MM_swapImage('Image1','','/images/home2.jpg',1)" onmouseout="MM_swapImgRestore()" /></a><a href="/windows.html"><img src="/images/services.jpg" width="151" height="51" alt="services" /></a><a href="/freebay.xhtml"><img src="/images/specials.jpg" width="153" height="51" alt="specials" /></a><a href="/gallery.html"><img src="/images/gallery.jpg" width="152" height="51" alt="gallery" /></a><a href="/roofing.xhtml"><img src="/images/order.jpg" width="152" height="51" alt="order" /></a><img src="/images/blank.jpg" width="75" height="51" /><img src="/images/facebook.jpg" width="38" height="51" alt="facebook" longdesc="http://facebook.com/midwestwindowbrokers" /><img src="/images/twitter.jpg" width="37" height="51" alt="twitter" longdesc="http://twitter.com/midwestwindow" /><img src="/images/google.jpg" width="42" height="51" alt="google+" longdesc="http://https://plus.google.com/u/0/b/108071947231835835141/108071947231835835141/posts" /></div>
<!-- end .header --></div>
<!-- TemplateBeginEditable name="navbar" -->
<div id="h-navbar">
<div id="h-navbar2"> Content for id "h-navbar2" Goes Here</div>
</div>
<!-- TemplateEndEditable -->
<div class="sidebar1">
<ul class="nav">
</ul>
<p> <div id="wufoo-z7x3k1">
Fill out my <a href="http://midwestwindow.wufoo.com/forms/z7x3k1">online form</a>.
</div>
<script type="text/javascript">var z7x3k1;(function(d, t) {
var s = d.createElement(t), options = {
'userName':'midwestwindow',
'formHash':'z7x3k1',
'autoResize':true,
'height':'601',
'async':true,
'header':'show'};
s.src = ('https:' == d.location.protocol ? 'https://' : 'http://') + 'wufoo.com/scripts/embed/form.js';
s.onload = s.onreadystatechange = function() {
var rs = this.readyState; if (rs) if (rs != 'complete') if (rs != 'loaded') return;
try { z7x3k1 = new WufooForm();z7x3k1.initialize(options);z7x3k1.display(); } catch (e) {}};
var scr = d.getElementsByTagName(t)[0], par = scr.parentNode; par.insertBefore(s, scr);
})(document, 'script');</script></p>
<!-- end .sidebar1 --></div>
<!-- TemplateBeginEditable name="Body" -->
<div class="content">
<h1>Instructions</h1>
<p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
<h2>Clearing Method</h2>
<p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule. This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a <br class="clearfloat" /> or <div class="clearfloat"></div> after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
<h3>Logo Replacement</h3>
<p>An image placeholder was used in this layout in the .header where you'll likely want to place a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
<p><span style="font-size: 18px; color: #C00; font-weight: bold; font-style: italic;">Logo Replacement</span></p>
<p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
<p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
<h4>Backgrounds</h4>
<p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
<!-- end .content -->
</div>
<!-- TemplateEndEditable -->
<div class="footer">
<p class="footer"><strong> <em>References Available!</em> We accept cash, check, Visa, Discover, MasterCard</strong></p>
Copyright 2012 Midwest Window Brokers Inc. All Rights Reserved.
<!-- end .footer --></div>
<!-- end .container --></div>
</body>
</html>I had saved one copy as an .asp but then resaved it to .xhtml
I'm assuming this is a static web site. Rename (F2) all your pages with .html or .htm extension.
.xhtml is not a valid extension.
Nancy O. -
Help with Wordpress in Live View
I have recently started attempting to use Dreamweaver to customise Wordpress themes, following the guidance given in this article:
http://www.adobe.com/devnet/dreamweaver/articles/dw_wordpress_pt1.html
However, despite following the advice precisely, I've encountered a problem. When I add an image to the header (following the method described on page 3 of the article), it does not display in Live View, nor does it appear in my web browser. Instead, as you can see (circled in red) it simply displays the icon for a missing image. In my browser, the alternate text is shown instead. So, in short, the image is missing.
The open file is index.php, opened from the root (htdocs) as specified in the article. I note from the comments on page 3 of the article that several people have experienced the same thing. One user reports solving it by placing the image in the images folder in the root directory, instead of within the theme directory. However, this seems odd for two reasons - one, as I understand it, it's not how Wordpress themes generally work (though I can understand having another 'images' folder in the root for working purposes), and two there is no images folder in my root directory. So, I have a few questions - the general one of what's going on and how do I fix, plus the specific question of whether or not there should be an images folder in my root directory? If so, why isn't it there? Any help greatly appreciated.
Regards,
MattI'm sure it is a path issue - the code in the header file supplies a path of images/banner_logo.gif as you can see. This is obviously causing the problem in some way because the set-up with Dreamweaver demands I open the index.php file from the root, but my quandary is that the path as it stands is sort of 'correct' in terms of how Wordpress should usually work, is it not? I obviously don't want to be creating absolute links for the sake of Dreamweaver that create additional problems (or simple redundancy) when I upload the theme.
The image is where it should be, relative to header.php:
Here's the Live Code - will supply CSS if needed but not sure it's the issue:
<!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>
blog</title>
<link rel="Shortcut Icon" href="http://localhost/wp-content/themes/MyTheme/favicon.ico" type="image/x-icon">
<link rel="stylesheet" href="http://localhost/wp-content/themes/MyTheme/style.css" type="text/css" media="screen">
<link rel="pingback" href="http://localhost/xmlrpc.php">
<meta name="robots" content="noindex,nofollow">
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://localhost/xmlrpc.php?rsd">
<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://localhost/wp-includes/wlwmanifest.xml">
<link rel="index" title="blog" href="http://localhost">
<meta name="generator" content="WordPress 3.2.1">
<style type="text/css">.recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}</style>
</head><body>
<div class="bannerArea">
<div class="container">
<div class="bannernav"><a href="#">Privacy Policy</a> • <a href="#">Contact Us</a> • <a href="#">Site Map</a></div>
<!--Title and description start-->
<img src="images/banner_logo.gif" width="223" height="51">
<!--Title and description end-->
<div style="clear:both;"></div>
</div>
</div>
<!--Navbar start-->
<div class="topnavigationArea">
<div class="container">
<div class="topnavigationgroup">
navigation goes here
</div>
<div style="clear:both;"></div>
</div>
</div>
<!--Navbar end-->
<div class="contentArea">
<div class="container">
<div class="contentleft">
<!--Here's where the loop starts-->
<!--Post box begin-->
<div class="box">
<h2 class="posttitle"><a href="http://localhost/?p=1">
Hello world! </a></h2>
<p class="metablock"><span class="meta">Posted on
October 11, 2011 by
<a href="http://localhost/?author=1" title="Posts by Matt Keefe" rel="author">Matt Keefe</a> </span><span class="postcomments">
<a href="http://localhost/?p=1#comments" title="Comment on Hello world!">1 Comment</a> </span></p>
<div class="entry">
<p>Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!</p>
</div>
<!--<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
<rdf:Description rdf:about="http://localhost/?p=1"
dc:identifier="http://localhost/?p=1"
dc:title="Hello world!"
trackback:ping="http://localhost/wp-trackback.php?p=1" />
</rdf:RDF>-->
</div>
<!--Post box end-->
<!--Next is what happens if no posts are found-->
<p>
</p>
</div>
<!--sidebar start-->
<div class="contentright">
<div id="search">
<!-- Search form in sidebar. Alternatively you can save the search form code as search.php and use a PHP include. -->
<form method="get" id="searchform" action="http://localhost/">
<input type="text" value="Search our site..." name="s" id="searchbox" onfocus="if (this.value == 'Search our site...') {this.value = '';}" onblur="if (this.value == '') {this.value = 'Search our site...';}" size="15">
<input type="submit" value="search" id="searchbutton">
</form>
<!-- Close search form -->
</div>
<h2>About My Blog</h2>
<p>This is a sample region where you can tell your blog visitors a little about you.</p>
<h2>Archives</h2>
<li><a href="http://localhost/?m=201110" title="October 2011">October 2011</a></li>
<h2>Categories</h2>
<li class="cat-item cat-item-1"><a href="http://localhost/?cat=1" title="View all posts filed under Uncategorized">Uncategorized</a>
</li>
<div class="clearer"><!-- Clear floats--></div>
</div>
<!--sidebar end-->
<div style="clear:both;"></div>
</div>
</div>
<!--Footer start-->
<div class="footerArea">
<div class="container">
<div class="copyright">
Copyright © 2010 <a href="http://localhost/">
blog </a> <a href="#">Terms of Use</a> | <a href="#">Privacy</a> | <a href="#">Contact</a></div></div></div>
<!--Footer end-->
</body></html> -
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 HammonsThanks 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! -
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 youHi 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.
Maybe you are looking for
-
Drag and drop a URL from IE's address bar
I have a Processing application written (by others) that uses [Andreas Schlagel's sDrop library|http://www.sojamo.de/libraries/drop/] to accept URLs dragged and dropped from the users' browsers' address bar. The application works fine for Chrome and
-
Hi All, i have got one requirement from client. he wants the report in mail. for that i configured ibots. but they want conditional ibot . i have seen it but not able to understand since they want condition on the value of rows not on count of rows.
-
Wish List for Future Releases of FME
First, I want to sincerely thank the Adobe team responsible for FME. Great job! Great application! We use FMS for 24/7 live cams and live TV streams. We have some suggestions for what might help FME be a more flexible tool for us and others in our si
-
ADF-Mobile app will not rotate in iOS simulator or device
We have been coding an ADF-Mobile app in JDeveloper and testing on both a Motorola tablet and an iPad. Both our application, as well as the demo "Deployment Successful" (found here: http://docs.oracle.com/cd/E18941_01/tutorials/MobileTutorial/jdtut_1
-
BAPI_PR_CREATE and Hold fonctionnalities
Hi, I would like to create a PR through BAPI_PR_CREATE and when I obtain an error, I would like to hold the PR. I activate MEMORY and MEMORYTYPE field (also in X structure) but it doesn't work. Do somebody have an idea. In advance a big thanks. Patri