7 Replies Latest reply on Aug 26, 2006 4:57 PM by Newsgroup_User

    Template Bug? Not sure where to post. I have a sample.

    fred_sl
      It seems that Dreamweaver 2004 MX (version 7.0.1 on Windows XP) gets confused if you create a page with invalid HTML. I've seen some other posts on this, but I'm not sure if it's been fixed.

      If you do the following, you'll get the popup warning "You have made changes to code that is not marked as editable.. blah blah blah" even though you did not make changes to uneditable regions.

      1. Make a remote site with a local web directory. On my machine, I run Apache ( http://localhost), treat it as a remote site, and copy files to Apache's local directory.
      2. Create a template with 1 editable region: EditRegion3
      3. Create a page using the template.
      4. Enter in a <form> </form>tag and some text.
      5. Select Put for the file.

      Works fine at this point.

      To invoke the bug:
      1. Remove the </form> tag.
      2. Select put.
      3. The InstanceBeginEditable name="EditRegion3" tag turns color: from gray to black.
      4. Close and reopen the file.
      5. Make a minor edit.
      6. Select Put.
      7. Presto - warning dialogue shows.

      I attached both versions. By the way, I was able to "fix" the broken edit region by closing (not saving changes) and reopening the file, adding back the missing </form> and saving. Then Put works with no error message.

        • 1. Re: Template Bug? Not sure where to post. I have a sample.
          Level 7
          So lemme understand this. If you hack a page so that it contains invalid
          code, you get a template error? Is that a surprise?

          Anyhow, there are several workarounds, and I see that you have found one.

          --
          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
          ==================


          "fred_sl" <webforumsuser@macromedia.com> wrote in message
          news:ebdo69$l8g$1@forums.macromedia.com...
          > It seems that Dreamweaver 2004 MX (version 7.0.1 on Windows XP) gets
          > confused
          > if you create a page with invalid HTML. I've seen some other posts on
          > this, but
          > I'm not sure if it's been fixed.
          >
          > If you do the following, you'll get the popup warning "You have made
          > changes
          > to code that is not marked as editable.. blah blah blah" even though you
          > did
          > not make changes to uneditable regions.
          >
          > 1. Make a remote site with a local web directory. On my machine, I run
          > Apache
          > ( http://localhost), treat it as a remote site, and copy files to Apache's
          > local
          > directory.
          > 2. Create a template with 1 editable region: EditRegion3
          > 3. Create a page using the template.
          > 4. Enter in a <form> </form>tag and some text.
          > 5. Select Put for the file.
          >
          > Works fine at this point.
          >
          > To invoke the bug:
          > 1. Remove the </form> tag.
          > 2. Select put.
          > 3. The InstanceBeginEditable name="EditRegion3" tag turns color: from gray
          > to
          > black.
          > 4. Close and reopen the file.
          > 5. Make a minor edit.
          > 6. Select Put.
          > 7. Presto - warning dialogue shows.
          >
          > I attached both versions. By the way, I was able to "fix" the broken edit
          > region by closing (not saving changes) and reopening the file, adding back
          > the
          > missing </form> and saving. Then Put works with no error message.
          >
          >
          >
          > // VALID HTML
          > ////////////////////////////////////////////////////////////////////////////////
          > //////////////////////
          >
          > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
          > " http://www.w3.org/TR/html4/loose.dtd">
          > <html><!-- InstanceBegin template="/Templates/Test.dwt.php"
          > codeOutsideHTMLIsLocked="false" -->
          > <head>
          > <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
          > <!-- InstanceBeginEditable name="doctitle" -->
          > <title>Admin - Image Upload</title>
          > <!-- InstanceEndEditable -->
          > <!-- InstanceBeginEditable name="head" -->
          > <!-- InstanceEndEditable -->
          > </head>
          >
          > <body>
          > <!-- InstanceBeginEditable name="EditRegion3" -->
          >
          > <form method="POST" enctype="multipart/form-data">
          > <table>
          > <tr><td>Image File</td><td><input type="file" name="FileName"></td></tr>
          > <tr><td colspan="2"><input type="submit" name="Submit"></td></tr>
          > </table>
          > </form>
          >
          > <!-- InstanceEndEditable --></body>
          > <!-- InstanceEnd --></html>
          >
          > // INVALID HTML
          > ////////////////////////////////////////////////////////////////////////////////
          > //////////////////
          >
          > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
          > " http://www.w3.org/TR/html4/loose.dtd">
          > <html><!-- InstanceBegin template="/Templates/Test.dwt.php"
          > codeOutsideHTMLIsLocked="false" -->
          > <head>
          > <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
          > <!-- InstanceBeginEditable name="doctitle" -->
          > <title>Admin - Image Upload</title>
          > <!-- InstanceEndEditable -->
          > <!-- InstanceBeginEditable name="head" -->
          > <!-- InstanceEndEditable -->
          > </head>
          >
          > <body>
          > <!-- InstanceBeginEditable name="EditRegion3" -->
          >
          > <form method="POST" enctype="multipart/form-data">
          > <table>
          > <tr><td>Image File</td><td><input type="file" name="FileName"></td></tr>
          > <tr><td colspan="2"><input type="submit" name="Submit"></td></tr>
          > </table>
          >
          > <!-- InstanceEndEditable --></body>
          > <!-- InstanceEnd --></html>
          >


          • 2. Re: Template Bug? Not sure where to post. I have a sample.
            fred_sl Level 1
            quote:

            So lemme understand this. If you hack a page so that it contains invalid
            code, you get a template error? Is that a surprise?

            1. You fail to understand this is a bug in the application, not a simple "template error". The Dreamweaver app mistakenly believes I made a change to an uneditable region when I DID NOT. Do you understand now?


            2. I wasn't "hacking" anything. Your characterization of such is ridiculous. I was using a feature of Dreamweaver, the template, and writing code and previewing the results on the server, since it's a PHP page after all. I had problems on the missing </form> tag because I was testing as I went because my page pulls data from a database. I don't care what is entered into the page, Dreamweaver should not behave this way, nor should it corrupt the template tags that it locks and manages.


            3. I shouldn't have to explain #2. Having to do so is patronizing to other readers.


            4. I don't appreciate your contemptuous tone.


            quote:

            Anyhow, there are several workarounds, and I see that you have found one.

            That's not good enough. Dreamweaver is an expensive application. FIX THE BUG.
            • 3. Re: Template Bug? Not sure where to post. I have a sample.
              Level 7
              > Do you understand now?

              Of course. I have understood all along. The bug is the fact that DW throws
              an error message with a generic content. But come on - to expect any HTML
              authoring system not to complain when you *break* the code on the page is
              silly.

              > 2. I wasn't "hacking" anything.

              You hacked the code on your page by removing the </form> tag.

              --
              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
              ==================


              "fred_sl" <webforumsuser@macromedia.com> wrote in message
              news:ebe2la$37c$1@forums.macromedia.com...
              >
              quote:

              So lemme understand this. If you hack a page so that it contains
              > invalid
              > code, you get a template error? Is that a surprise?

              > 1. You fail to understand this is a bug in the application, not a simple
              > "template error". The Dreamweaver app mistakenly believes I made a change
              > to an
              > uneditable region when I DID NOT. >
              >
              > 2. I wasn't "hacking" anything. Your characterization of such is
              > ridiculous. I
              > was using a feature of Dreamweaver, the template, and writing code and
              > previewing the results on the server, since it's a PHP page after all. I
              > had
              > problems on the missing </form> tag because I was testing as I went
              > because my
              > page pulls data from a database. I don't care what is entered into the
              > page,
              > Dreamweaver should not behave this way, nor should it corrupt the template
              > tags
              > that it locks and manages.
              >
              >
              > 3. I shouldn't have to explain #2. Having to do so is patronizing to other
              > readers.
              >
              >
              > 4. I don't appreciate your contemptuous tone.
              >
              >
              >
              quote:

              Anyhow, there are several workarounds, and I see that you have found
              > one.

              > That's not good enough. Dreamweaver is an expensive application. FIX THE
              > BUG.
              >
              >


              • 4. Re: Template Bug? Not sure where to post. I have a sample.
                fred_sl Level 1
                [Q}Of course. I have understood all along. The bug is the fact that DW throws
                an error message with a generic content. But come on - to expect any HTML
                authoring system not to complain when you *break* the code on the page is
                silly.


                I am a software developer. Over the last 12 years, I have developed many applications on many platforms. Windows, Linux, C, C++, Perl, PHP, UNIX shell, Java, x86 ASM. I have a long history of experience with Perl and PHP web development. I have developed GUI applications, custom multi-threaded web servers, a micro-kernel operating system, batch processing analytics programs that processed 100's of billions of records a day. I tell you, this bug is unacceptable. There's no reason it could not be fixed.

                Dreamweaver manages the non-editable template regions and it, itself, corrupts those regions. What you assume is that Dreamweaver would implement a standard HTML parsing engine for managing HTML pages so "obviously" invalid code would cause problems. NO. Dreamweaver has a more sophisticated engine compared to your standared rendering engine such as IE or gecko. It has to to implement its authoring and templating features. With sophisticated features, comes a requirement for more sophisticated error checking.

                For some reason, you accept certain bugs as "the fact of life" and you learn to "deal with it". You're just like one of those Bill Gates dogmatists who excused away all the bugs in Windows 95 by offering annoying workarounds.



                quote:

                You hacked the code on your page by removing the </form> tag.


                You actually believe hand-coding HTML is hacking? Do you realize Dreamweaver is designed for hand-coding HTML? Did you ever notice the little "Code" tab on the document frame? I bet you don't know what that does. You're probably afraid of all that mysterious "code" inside there.

                Secondly. I did not originally remove the tag. I left it out, which subsequently caused Dreamweaver to corrupt the template regions.



                quote:

                Adobe Community Expert


                A joke. You're a certifiable imbecile who thinks hand HTML coding is "hacking". You're not an Adobe representative, even though you probably think you are. You're a big fish in a very SMALL pond. So much for your "ACE" calling card. When it comes to development, you're a ZERO. This is my last correspondence with you. You're a waste of my time.
                • 5. Re: Template Bug? Not sure where to post. I have a sample.
                  fred_sl Level 1
                  For anyone still using Dreamweaver 2004 MX, this BUG has been fixed in Dreamweaver 8, so I highly recommend upgrading.

                  To the chagrin of a certain community "expert" (I prefer idiot) who shall remain unnamed.
                  • 6. Re: Template Bug? Not sure where to post. I have a   sample.
                    Level 7
                    fred_sl wrote:
                    > For anyone still using Dreamweaver 2004 MX, this BUG has been fixed in
                    > Dreamweaver 8, so I highly recommend upgrading.

                    Obviously you have found the answer to your template problem. To answer
                    the question about where to post when you have details of a suspected
                    bug, there is an official channel for posting bugs/feature requests at
                    the following URL:

                    http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

                    I don't normally use templates, so am not in a position to judge the
                    issue in question. However, what the development team values above all
                    are bug reports with reproduceable steps.

                    This is a user-to-user forum, so it's not the best place to file bug
                    reports. Even if you get the help that you want, it doesn't necessarily
                    filter through to the development team, so may not be corrected in
                    future versions.

                    --
                    David Powers
                    Adobe Community Expert
                    Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
                    http://foundationphp.com/
                    • 7. Re: Template Bug? Not sure where to post. I have a sample.
                      Level 7
                      I'm glad you feel like you have the answer. Using your method will come
                      back to bite you.

                      --
                      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
                      ==================


                      "fred_sl" <webforumsuser@macromedia.com> wrote in message
                      news:ecqedu$dpo$1@forums.macromedia.com...
                      > For anyone still using Dreamweaver 2004 MX, this BUG has been fixed in
                      > Dreamweaver 8, so I highly recommend upgrading.
                      >
                      > To the chagrin of a certain community "expert" (I prefer idiot) who shall
                      > remain unnamed.
                      >