ASP in 'Design View' Issues

I'm trying to add ASP includes that I created in DW using
simple HTML and saving it out as ASP into a ASP Page in DW that
originally came from FrontPage :( When I include these ASP includes
I loose the visual of all my elements when I'm working in the
Design and Code View. Which I would rather edit in Design that
Code.
FYI: When I brought the original ASP page from Frontpage in
DW I was able to VIew the html elements and had the ASP icon in the
corresponding ASP includes which is perfect.
Please any help would be great. Obviously I have been thrown
into a programmers world and I'm drowning. :)

It sounds like your includes are full HTML pages and not just
snippets. The
includes cannot have <head>, <html>, or
<body> tags anywhere.
"hairpeace65" <[email protected]> wrote in
message
news:f32bi9$i8v$[email protected]..
> I'm trying to add ASP includes that I created in DW
using simple HTML and
> saving it out as ASP into a ASP Page in DW that
originally came from
> FrontPage
> :( When I include these ASP includes I loose the visual
of all my
> elements
> when I'm working in the Design and Code View. Which I
would rather edit in
> Design that Code.
>
> FYI: When I brought the original ASP page from Frontpage
in DW I was able
> to
> VIew the html elements and had the ASP icon in the
corresponding ASP
> includes
> which is perfect.
>
> Please any help would be great. Obviously I have been
thrown into a
> programmers world and I'm drowning. :)
>
>

Similar Messages

Design View Issue Dreamweaver CS4 - Taking forever to load design view

I am having an issue where my site takes literally almost a full day to load in design view. Once it is loaded everything works seemlessly but once I close down Dreamweaver and reopen it, I have to wait another day to get to design view of my site. All files open just fine in code view.
I have deleted the Dreamweaver CS4 cache folder, completely formatted my drive and reinstalled creative suite. I have also validated my code on W3c and everything checks out fine.
The majority of my site is based off of a template, but even when I remove all the template references in the html files from Notepad I am still having the same issue. My site renders fine and quickly however on Explorer, Firefox, Chrome, and Safari.
When loading any other site off the web into Dreamweaver I do not run into the problem so there must be something wrong with how my site is set up. Either the Template file is no good or somewhere else I am falling short. Can someone, please, please, please ( I am begging) help me figure out what is going on here.
My index file is located at - http://www.thebluedot.net/index.html and the template file is located at - http://www.thebluedot.net/Templates/index.dwt
I have searched high and low and even made a post on this same topic about a month ago but never came up with a resolution to my issue. I had given up on finding a solution to this problem for some time, but I really need to figure out where I am going wrong here!
Additional Details -
I am running - Windows Vista Ultimate on a Core 2 Processor with 12 GB of Ram & Solid State Hard Drive. Everything on my system runs super smoothly except loading my site in Dreamweaver CS4 design view.
I really appreciate any help you can provide.

I have used CS2 Adobe GoLive to create and manage a website (pro-prosperity.com). Now, I have CS4 Dreamweaver. I got a new site set up on Dreamweaver using the site management facility. I then have the contents of website available locally on Dreamweaver. I can edit files. But the main home page, index.html, is not displaying on design view mode for editing, although it displays everything on live view mode. I have struggled for days and am not getting any difference in attributes of index.html and another .html that is displaying fine on design view and is editable.
I am really lost and am begging for any help. Can you, for example, copy the home page from pro-prosperity.com and display on design view and edit it? Please tell me what is in this file that is troublesome. Thanks.
The first thing you should do is to make sure that this feature is turned on (it's off by default):
View > Code View Options > Highlight Invalid Html
It's not perfect, but it will notify you of some problems. In Code View, there are many problems highlighted. Some of them don't make sense, but are triggered because of a problem with a parent tag.
Be sure to make a backup copy of your file before doing the next step. Close your page. Go to Preferences > Code Rewriting, and turn on "Fix invalidly nested and unclosed tags", "Remove extra closing tags", and "Warn when fixing or removing tags". Click OK, then re-open your page. The messages in the dialog to tell you what was changed. This allowed me to see your page in Design View (I am using CS5).
Note: I suggested that you reset your preferences to turn off those 3 settings as they can cause problems with some markup.
In the long term, I suggest that you avoid nesting tables wherever possible.
Hope this helps,
Randy

Dreamweaver CS4 Design View Issues

Hi,
I'm experiencing issues with the design view in DW CS4. It seems a little buggy to me. Sometimes I cannot seem to select any items at all, either using a single or double click. It's starting to drive me nuts. Is there an easy way to enter into this form of editing that's a little less random ?
Many thanks in advance

There are two things that could prevent you from editing a region of DW's design view:
The page is the child page of a DW template and the region you are trying to edit is in a NON-EDITABLE part of that template, and cannot be edited in the child page.
The container (i.e., the ancestor) for the region you are attempting to edit has a CSS style of "overflow:hidden" applied to it. Double clicking (or right click > Element View > View All) would open that region for editing.
If you are able to verify that one of those two possibilities is in play, then you have your answer. If neither of them applies, then we would need to see the page and its code - perhaps you could post a link to it?

Design View issue

I've imported an older Flex 3 project into Flash Builder 4 Beta 2 and have the 'Use Flex 3 compatibility mode' is turned on. All is fine until I select 'MX Only' as the Component Set. Switching from 'MX + Spark' causes the Design View to become completely grey. Literally, there is nothing but solid grey. As I don't need the Spark components (which add an extra 200k to my Export Release I want to keep using only MX for now.
Help?

The only way I'm able to use Design View with my Flex 3 project is to set the Component Set to 'MX+ Spark'. Choosing only 'MX' will result in solid grey. As I don't need the Spark components I need to switch to the 'MX' Component Set each time I want create a release build. If there is any fast patch (or technique) to resolve this under Beta 2 please let me know. I would sure like to see things like this resolved for the release of Flash Builder 4. Otherwise, however, I'm happy to see that the import process of Flex 3 projects has become more seamless. Very nice.
Jason Villmer

Design view issue - CSS and html

Hi
I was wondering if anyone can help me with this. Someone has
created a page for me using html and CSS as requested. The problem
is that whenever I try to open the index.html file in design view
or code and design view, Dreamweaver crashes and I have to restart.
I am attaching the html and CSS below. Just as an aside, I have
asked them to create the code using CSS rather than tables and have
ended up with div hell.
Cheers
Julie
@charset "utf-8";
* {padding:0; margin:0;}
body {padding:10px 0 10px 0; background-color:#fff; margin:0
auto; width: 976px; font-family:Arial, Helvetica, sans-serif;
font-size:11px; color:#333;}
#wrap {margin:0 auto; padding:0; position:relative; width:
976px;}
a:link { color:#999; text-decoration: underline; }
a:visited { color:#999; text-decoration: underline; }
a:hover{ color:#666; text-decoration: none; }
img { border:none; padding:0; margin:0;}
h1 {font-size: 36px;}
h2 {font-size: 24px;}
h3 {font-size: 18px;}
h4 {font-size: 16px;}
h5 {font-size: 14px;}
h6 {font-size: 11px;}
input { position:relative; font-weight: normal;cursor:
pointer;vertical-align: middle;padding: 0 3px;font-size:
13px;font-family: Verdana, Helvetica, Arial, sans-serif;
border:#a09f6f 1px solid;}
select {font-family: Verdana, Helvetica, Arial,
sans-serif;font-weight: normal;cursor: pointer;vertical-align:
middle;border: 1px solid #999;padding: 1px;background-color:
#FAFAFA;}
option {padding-right: 2px;}
textarea {font-family: "Lucida Grande", Verdana, Helvetica,
Arial, sans-serif; width: 60%;padding: 2px;font-size:
1em;line-height: 1.4em; border:#a09f6f 1px solid; width:390px;
height:170px;}
/* Header Part Start */
#header {margin:0; padding:0; position:relative;
background:url(../images/index_01.jpg); width:976px; height:97px; }
#header .headprt {margin:0; padding:0; position:relative }
#header .headprt .headprtr { float:right; width: 500px;
margin:0; padding:0; position:relative }
#header .headprt .headprtr .padhr { color:#fff; margin:0;
padding:16px 44px 0 0; position:relative; text-align:right;}
#header .headprt .headprtl {margin:0 500px 0 0; padding:0;
position:relative;}
#header .headprt .headprtl .padhl{ color:#fff; margin:0;
padding:40px 0 0 44px; position:relative }
.hhllb { font-size:16px;}
.hhlld { font-size:16px; font-weight:bold}
.hhllc { font-size: 20px; font-weight:bold}
.hhlls { font-size:14px}
.kulay { color:#e55b68}
/* Header Part End */
/* Main Part Start */
#maincontent {margin:0; padding:0; clear:both;
position:relative; display:block; background-color:#fff }
#maincontent .boxmainbgl {margin:0; padding:0;
position:relative; background: url(../images/index_10.jpg) repeat-y
top left; }
#maincontent .boxmainbgl .boxmainbgr {margin:0; padding:0;
position:relative; background: url(../images/index_11.jpg) repeat-y
top right; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
{margin:0; padding:0; position:relative;
background:url(../images/index_02.jpg) no-repeat top left; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr {margin:0; padding:0; position:relative;
background:url(../images/index_05.jpg) no-repeat top right; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr .boxmainbgbotl {margin:0; padding:0;
position:relative; background:url(../images/index_15.jpg) no-repeat
bottom left; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr .boxmainbgbotl .boxmainbgbotr {margin:0; padding:0;
position:relative; background:url(../images/index_16.jpg) no-repeat
bottom right; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr .boxmainbgbotl .boxmainbgbotr .boxpadzki {margin:0;
padding:8px 48px 0 49px; position:relative; height: 1340px;}
.mainconup {margin:0; padding:0; position:relative;
clear:both; display:block; overflow:hidden; height:485px }
.mainconup .mmtoprt { float: right; width:615px; margin:0;
padding:0; position:relative }
.mainconup .mmtoprt .mmrtM {margin:0; padding:0;
position:relative; background:url(../images/picpic.jpg) no-repeat
top left; height:479px; }
.mainconup .mmtoprt .mmrtM .mmrtA {margin:0; padding:200px 0
0 10px; position:relative; width:600px; }
.mainconup .mmtoprt .mmrtM .mmrtA .mmppr { float:right;
width: 195px; margin:0 0 0 -3px; padding:0; position:relative }
.mainconup .mmtoprt .mmrtM .mmrtA .mmppc {margin:0 195px 0 0;
padding:0; position:relative;}
.mainconup .mmtoprt .mmrtM .mmrtA .mmppc .mmppx {float:right;
width: 205px; margin:0; padding:0; position:relative}
.mainconup .mmtoprt .mmrtM .mmrtA .mmppc .mmppl {margin:0
205px 0 0; padding:0; position:relative; height:100px}
.bkspdC { font-size: 22px; font-weight:bold; color:#fff;
margin:0; padding:30px 0 0 0; position:relative; line-height:20px}
.bkspdB { font-size: 22px; font-weight:bold; color:#fff;
margin:0; padding:20px 0 0 0; position:relative; line-height:20px}
.bkspdA { font-size: 22px; font-weight:bold; color:#fff;
margin:0; padding:30px 0 0 10px; position:relative;
line-height:20px}
.mainconup .mmtoplt {margin:0 615px 0 0; padding:0;
position:relative }
.mainconup .mmtoplt .logo {margin:0; padding:2px 0 0 3px;
position:relative }
.mainconup .mmtoplt .linek {margin:10px 20px 7px 3px;
font-size:2px; padding:0; position:relative; border-top: #e7e7e7
2px solid }
.mainconup .mmtoplt .pargs {margin:0; padding:10px 20px 0
3px; position:relative; line-height:13px }
.hhllw { font-size: 22px; font-weight:bold; color:#23a9e8}
.maincentr { clear:both; margin:0; padding:0;
position:relative; background-color:#2774c2; display:block; }
.maincentr .mckbb {margin:0; padding:10px 10px 20px 20px;
position:relative; color:#fff; }
.maincentr .mckbb .mckrt {margin:0; padding:0;
position:relative; float:right; width:290px }
.maincentr .mckbb .mcklt {margin:0 290px 0 0; padding:0;
position:relative }
.maincentr .mckbb .mcklt .mcklrr {margin:0; padding:0;
position:relative; float:right; width:290px; height:170px;
background:url(../images/bgline.jpg) no-repeat right 10px; }
.maincentr .mckbb .mcklt .mcklcc {margin:0 290px 0 0;
padding:0; position:relative; height:170px;
background:url(../images/bgline.jpg) no-repeat right 10px; }
.maincentr .cbgc {margin:0; padding:0; position:relative;
background:url(../images/bgline2.gif) repeat-x top left;
height:2px; font-size:2px}
.customks {margin:0; padding:0; position:relative;
font-size:20px; font-weight:bold }
.quotep {margin:0; padding:20px 20px 0 0; position:relative }
.quotep .quotea {margin:0; padding:0; position:relative;
background:url(../images/qouteleft.jpg) no-repeat top left; }
.quotep .quotea .quoteb {margin:0; padding:0;
position:relative; background:url(../images/qouteright.jpg)
no-repeat bottom right }
.quotep .quotea .quoteb .quotez {margin:0; padding:28px 0 0
0; position:relative; font-size:12px; line-height:13px; }
.xquotep {margin:0; padding:20px 20px 0 20px;
position:relative }
.xquotep .xquotea {margin:0; padding:0; position:relative;
background:url(../images/qouteleft.jpg) no-repeat top left; }
.xquotep .xquotea .xquoteb {margin:0; padding:0;
position:relative; background:url(../images/qouteright.jpg)
no-repeat bottom right }
.xquotep .xquotea .xquoteb .xquotez {margin:0; padding:28px 0
0 0; position:relative; font-size:12px; line-height:13px; }
.mainbut {margin:6px 0 0 0; padding:0;
position:relative;clear:both; display:block }
.mainbut .mainbbj {margin:0; padding:0; position:relative }
.mainbut .mainbbj .mainbbrt {margin:0; padding:0;
position:relative; float: right; width: 167px }
.mainbut .mainbbj .mainbbrt .sshots {margin:0; padding:0 0
2px 0; position:relative; width: 167px }
.mainbut .mainbbj .mainbbrt .sshots .higfx {margin:0;
padding:0; position:relative; width: 167px; height:122px;
overflow:hidden }
.mainbut .mainbbj .mainbblt {margin:0 167px 0 0; padding:0;
position:relative }
.mainbut .mainbbj .mainbblt .mainbbrr {margin:0; padding:0;
position:relative; float: right; width: 425px }
.mainbut .mainbbj .mainbblt .mainbbrr .mainbbpads {margin:0;
padding:10px 26px 0 26px; position:relative; font-size:12px;
line-height:14px }
.mainbut .mainbbj .mainbblt .mainbbcc {margin:0 425px 0 0;
padding:0; position:relative; background:#3a3a3a; color:#fff }
.mainbut .mainbbj .mainbblt .mainbbcc .mainccpads {margin:0;
padding:20px 25px 25px 18px; position:relative; font-size:12px;
line-height:15px }
.hhllt { font-size: 20px; font-weight:bold; color:#23a9e8}
.hhllk { font-size: 18px; color:#23a9e8}
/* Main Part End */
/* Footer Part Start */
#footer {margin:0; padding:0; clear:both; position:relative;
display:block }
#footer .footboxbg {margin:0; padding:0; position:relative;
background: url(../images/index_18.jpg) repeat-x top left; }
#footer .footboxbg .footboxlt {margin:0; padding:0;
position:relative; background: url(../images/index_17.jpg)
no-repeat top left; }
#footer .footboxbg .footboxlt .footboxrt {margin:0;
padding:0; position:relative; background:
url(../images/index_20.jpg) no-repeat top right; height:36px }
/* Footer Part End */

Web Dynpro doesn't allow for the inclusion of custom HTML and CSS. It is far building business application in a client rendering abstracted framework.
If you need some common header, then you should consider the usage of the NetWeaver Portal.

Something's wrong...Design View issue....

OK.
I'm attempting to take an Excel purchase order form and turn it into an HTML form for a custom demo that I will be performing tomorrow. The nature of the demo isn't important; what is important is that I have no choice but to use Design View, as I need to make sure the HTML version is visually identical to the Excel version. Everything was going fine...until I glanced over into the code and noticed that instead of intuitively assuming that there should be one FORM element for multiple INPUT elements, Dreamweaver created a separate FORM element for each INPUT. So of the 15 elements I've got so far it created a separate FORM element for each. This is a problem, because the form won't submit properly in this fashion.
So I did the logical thing: Went into the code, removed the extra FORM elements, and migrated one of them to just after the BODY tag but before the actual content, then added the end tag at the tail end of it all. What happened next is my problem: Design View is all kinds of whacked out. It's not abiding by any of the table structures, background colors, anything. The code is correct - previewing the page verifies this. Firefox is about 95% accurate, and I can live with that threshold. IExplorer is about 85% accurate, and I can fix what's not correct, but it's way more accurate than Design View which just doesn't render it correctly at all. If I do Live View it's fine, but I can't edit WYSIWYG in that view. Now I'm stuck unless I "screw up" the code again, which I don't want to do.. I don't have any fancy scripts, nothing out of the ordinary...just regular tables, inputs and a few background colors rendered via CSS. I haven't even gotten halfway through the project yet.
Does anyone know why Dreamweaver does this? Why would Design View's rendering of simple tables be so astronomically different from what the browser sees? Is the Design View rendering engine too structured or something? See pics.
This is WRONG.
This is RIGHT.

I would think Design should show me what IE is seeing, at the very least.
This isn't FrontPage, you know? I'm pretty sure DW Design View uses a WebKit rendering engine, aka Safari & Chrome.
for whatever reason Dreamweaver won't allow me to apply proper styling (background colors, font sizes, etc) without going CSS. It's quite annoying.
CSS is not some arbitrary method fashioned by Adobe to make your life harder. It is in fact a web standard recommended by the W3C to make the web better for everyone.
The separation of Content (HTML) from Style (CSS) is not a brand new concept either. It's been around since the late 1990's.
To appreciate what CSS can do for you, visit the CSS Zen Garden.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Crystal 11 Design View Issue

When I select a field, the black highlight box and handles do not appear anymore for resizing etc....
I have not been able to find a solution and it is driving me nuts!
please help!

Hi Brian,
If you can't upgrade we can't help you much more. Try downloading it anyways on a separate PC and test, it will at least confirm if it's an issue or not.
Try doing a Repair install of CR XI also, it may be that some Windows Patch broke or changed Access Permissions of one of our Dependencies.
Known issues when weird things happen when viewing reports are typically due to either USP10.dll ( UNICODE interpreter ) or in GDIPlus.dll ( Windows Graphical Device Interface ). They are both tied to the PC's Video drivers.
Try updating your Video Card Drivers and USP10 must be version 1.4.2.x.
You can download [Modules |https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip]and compare your System dll list with a working one, may help determine the cause.
Thanks
Don

Design View Problems in Dreamweaver CS3

Hello folks,
I've been having design view issues in Dreamweaver CS3 on my
Windows XP 2002 SP2 computer. When placing library items in tables,
the library item will disappear from design view, and sometimes
columns or rows in disappear as well. The code remains unaffected
and the pages appear okay in all browsers, but not having preview
working correctly is definitely a disadvantage. Has anyone else
experienced this problem and, if so, do you know of any fixes?
Many thanks!
Brooke

This is nearly diagnostic for an improperly made Library
item.
Do your Library items contain <html>, <head>, or
<body> tags? Do they
contain CSS rules?
If not, can you show us a page that is doing this for you?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"brookest" <[email protected]> wrote in
message
news:fm5h9k$4k1$[email protected]..
> Hello folks,
> I've been having design view issues in Dreamweaver CS3
on my Windows XP
> 2002
> SP2 computer. When placing library items in tables, the
library item will
> disappear from design view, and sometimes columns or
rows in disappear as
> well. The code remains unaffected and the pages appear
okay in all
> browsers,
> but not having preview working correctly is definitely a
disadvantage. Has
> anyone else experienced this problem and, if so, do you
know of any fixes?
> Many thanks!
> Brooke
>

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

D8 Design view problem or setting

Hi, I think I may have unknowingly adjusted a setting or
preference for the display of design view. The thing is that while
I was working on a form page the design view display changed from
readable to some sort of garbled rendition of the page. I
understand this could be a problem with my code except that I have
the design view issue on lots of pages now…the included Page
Designs(CSS) templates don’t view properly in design view.
Attached is a screen capture, and the code used, of a basic new
html document to which I add a layer…the layer views as a
long narrow rectangular box and supposedly I should be able to
click on it and resize the layer box…but I can’t. In
these situations design view is unusable.
Please help educate me.
Thanks,
Greg
Code is attached for screen capture...btw, not my code all
autogenerated by Dreamweaver.
Screen Capture of
Design View display

VIEW | Style Rendering > Display Styles & Screen Media
Type - are both of
those enabled?
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
==================
"gpederson" <[email protected]> wrote in
message
news:[email protected]...
> Hi, I think I may have unknowingly adjusted a setting or
preference for
> the
> display of design view. The thing is that while I was
working on a form
> page
> the design view display changed from readable to some
sort of garbled
> rendition
> of the page. I understand this could be a problem with
my code except
> that I
> have the design view issue on lots of pages now?the
included Page
> Designs(CSS)
> templates don?t view properly in design view. Attached
is a screen
> capture,
> and the code used, of a basic new html document to which
I add a layer?the
> layer views as a long narrow rectangular box and
supposedly I should be
> able to
> click on it and resize the layer box?but I can?t. In
these situations
> design
> view is unusable.
> Please help educate me.
> Thanks,
> Greg
>
> Code is attached for screen capture...btw, not my code
all autogenerated
> by
> Dreamweaver.
http://nsight.us/development/dreamweaver/
>
> <!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=iso-8859-1" />
> <title>Untitled Document</title>
> <style type="text/css">
> 
> </style>
> <script type="text/javascript">
> 
> </script>
> </head>
>
> <body>
> <div id="Layer1"></div>
> </body>
> </html>
>

Dreamweaver 8 Design View render issue

I was wondering if anyone else has noticed a highly
irritating issue with DW8 that is apparently not an issue in the
Design View of DW MX 2004.
In DW 8 for some reason I'm getting an extra 150 pixels of
white space to the right of my #content container. It only appears
to happen when the content within the #content container does NOT
exceed the length of the content in my menu container (#priNav2).
In other words, if the content is longer then the menu, it renders
fine.
See here:
Dreamweaver
8
But, in DW mx2004 the exact same file shows up how it should.
Dreamweaver
MX 2004
Does anyone have any suggestions on how to resolve this issue
or have a clue as to why this is happening? It's really one of the
only bugs left preventing me from upgrading to DW 8 anymore.
Thanks,
- Paul

After some tinkering around and a call to Tech. Support I
eventually resolved this issue by pointing out a bug to Adobe.
Apparently the problem is the View / Visual Aids / Invisible
Elements option. If this is turned on, and you have a website set
up similiarly to
this one, you will
experience this sporatic, extranenous white space that shifts your
content around. It is not an issue in DW MX 2004, only DW 8.
The solution is to just simply turn OFF the "Invisible
Elements" option. Then the page will render the way it should.
A bug report has been submitted.

Path issue leaving me unable to add blog post content in design view

Hi guys,
I am unable to add blog post content in design view when a template is applied to my blog. BC support have told me they fixed the problem by making minor changes to the paths of the css and javascript files and then told me to post on here for the solution.
When I call the files using <link rel="stylesheet" href="/css/custom.css" /> everything displays perfectly but in BC I can't add blog post content in design view. I can edit in html but this isn't ideal for clients to update the blog.
If I change the paths to <link rel="stylesheet" href="css/custom.css" /> it fixes the problem and I can then edit blog content in design view but all blog pages that are in folders display incorrectly. Only the main blog page display properly.
I'm sure the answer is simple but I can't find it so any help would be greatly appreciated. Thanks
Pete

I took a look at your page URL and can't find any CSS issues or styles that would directly affect you editing/adding content to a blog post via the content editor.
Make sure you either clear your cache or try in another browser to see if the problem is localized to your current browser.
If you still have the problem can you link me to a screencast (you can use Jing if you don't have a screencast program: http://www.techsmith.com/jing.html) of what you are experiencing?

Still having issues with CSS fonts in design view

I only see the following error messages when I enter design
view for a component *other* than my main mxml component:
unable to resolve '/ProjectName/assets/JapaneseBrush.ttf' for
transcoding
Unable to transcode /ProjectName/assets/JapaneseBrush.ttf.
The resource named is the project's root directory (?), and
it refers to line 4. (Same line as the src: url() row in the CSS
file.)
These errors don't show up until after I tab to the design
view, and the font isn't used in the design view (other than this
the CSS works fine). (Even though it works perfectly when actually
running the Flex app.)
I'm using an external CSS file that looks like this:
@font-face{
src: url("/assets/JapaneseBrush.ttf");
fontFamily: JapaneseBrush;
fontStyle: regular;
I've tried actually placing the ttf file in a few different
locations, ProjectName/assets/, ProjectName/src/assets,
ProjectName/src, ... no change. My main mxml is in ProjectName/src.
Anyone have an issue like this before?

I've aleady done so before - FB-9873.
It's not *exactly* the same problem - now the example project
I gave from last time doesn't work at all. I've added a new comment
to the bug report but it's currently "closed" so it has to be
copied or re-opened or something. No time to create a new example
from scratch this time, sorry.
The extremely annoying aspect to this problem is that I have
a large, complex project where the fonts work fine in design view
(now - it wasn't when I created this thread), and I have no idea
why. It seemed to just magically decide to work one day!
This is a re-occuring problem that seems to come and go
magically, and it probably needs some serious bug testing by more
than just a developer.

Display issue in Design view

:confused; I'm working in Dreamweaver 8 (Windows XP). I'm
using the 2col_leftNav.css (tweaked somewhat) for my pages. I'm
having some problems with the display in Design view.
For quite some time, whenever I entered new text into a page,
everything in the div (content > feature) shifted to the right.
If I italicized or bolded the text, everything would shift back
into position. If I changed it back into normal font, it stayed in
place until I added more content. Quite annoying, but I managed.
Something that just started (taking over the previous issue,
with no apparent reason/causal factor): the content > feature
div has shifted to the left, overlapping the left column
navigation. I haven't found anything that will make things shift
back into place. This is very hard to read, and makes working in
design view almost impossible.
Any idea what is going on here and what I can do about
it?

quote:
Originally posted by:
bregent
>Any idea what is going on here and what I can do about
it?
You forgot to post the url so we really can't say.
This is something that presents itself ONLY in Dreamweaver.
When I look at the file in a browser, it looks fine. When I post
the page to the internet, it's fine. The issue is just in editing
the page in Dreamweaver.
However, if you'd like to see some pages where this issue
presented itself during construction, you can see them at
www.essential-vitamins.com/stemTech/index.html
www.therapeutic-grade.com.
Thanks.

ASP Corrupts my Design View

I have a site with css that I developed on a XP machine with Dreamweaver CS3. For my footer I use an asp include:

In XP I could still view my pages in design mode and they looked fine, but i recently got a new computer that runs win pro7. I have installed dreamweaver CS3 and now when I view these pages they are all messed up in design view unless I take out this code. A message came up the first time I closed dreamweaver about some windows components to working properly but I think I clicked the wrong thing and cant get that message back. Does anybody know how to make my design view work again while my asp code is on the page?
thanks,
Nick

It's just a hyper link page for he most part. Here is the code.
<!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>Untitled Document</title>
<style type="text/css">

</style>
</head>
<body>
<p><span class="style1"><a href="http://pacificsteelstructures.com/">Home</a> | <a href="http://pacificsteelstructures.com/products/">Products</a> | <a href="http://pacificsteelstructures.com/manufacturing/">Manufacturing</a> | <a href="http://pacificsteelstructures.com/engineering/">Engineering</a> | <a href="http://pacificsteelstructures.com/news/">News</a> | <a href="http://pacificsteelstructures.com/contact/">Contact Us</a></span> <span class="style1"> ©2009 Pacific Steel Structures, LLC. All Rights Reserved.</span></p>
</body>
</html>

ASP in 'Design View' Issues

Similar Messages

Maybe you are looking for