CSS Form Designer Support Product Page

PROBLEMS

Error when trying to use latest version

Reported 12 Aug 2009 19:37:05

has this problem

12 Aug 2009 19:37:05 David Stoltz posted:

The CSS Form Designer works, but as soon as I am finished designing my form, I click the button to insert the form, and I get:

Making this change would require changing code that is locked by a template or a translator. The changes will be discarded.

The page I am working with IS based on a template, using ASP. But like all templates you can insert stuff into the head area, etc...

Any help?

Thanks

Replies

Patrick Julicher

Replied 12 Aug 2009 20:50:50

12 Aug 2009 20:50:50 Patrick Julicher replied:

Hi David,

Are you using the updated 1.0.1 version? Could you post the code of the page you are trying to enter the form on?

Kind regards, Patrick

David Stoltz

Replied 12 Aug 2009 21:33:37

12 Aug 2009 21:33:37 David Stoltz replied:

Patrick - thanks for the quick reply. Yes, using 1.0.1 - Here's the code:

<%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%>
<% PageTitle = "Request Info" %>
<!--#include virtual="inc_breadcrumb_navigation.asp" -->
<!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"><!-- InstanceBegin template="/Templates/Column2Template.dwt.asp" codeOutsideHTMLIsLocked="false" -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>
<% = PageTitle %>
</title>
<meta name="Keywords" content="" />
<meta name="description" content="" />
<link href="shh.css" rel="stylesheet" type="text/css" />
<!-- InstanceBeginEditable name="head" -->
<!-- InstanceEndEditable -->
</head>
<body>
<div id="mainContainer">
  <!--#include virtual="inc_topNavBar.asp"-->
  <!--#include virtual="inc_header.asp"-->
  <!--#include virtual="inc_navBar.asp"-->
  <div id="contentSubPageWrapper">
    <div id="subPageNav">
      <div id="spnTop">
        <div id="spnTopText">NAVIGATION</div>
      </div>
      <div id="spnContentHolder">
        <div id="spnContent">
          <!--#include file="subnav.asp"-->
        </div>
      </div>
      <div id="spnBottom"></div>
    </div>
    <div id="mainContentWrapper2">
      <div id="breadcrumb">[img]images/dot.gif" width="3" height="28" align="bottom" />
        <% = breadcrumb_navigation(Request.ServerVariables("PATH_INFO")) %>
      </div>
      <!-- InstanceBeginEditable name="EditRegion1" -->
      [h1]Request more Information[/h1]
      <p>Form goes here</p>
      <p> </p>
      <!-- InstanceEndEditable --></div>
  </div>
  <!--#include virtual="inc_footer.asp"-->
</div>
<!--#include virtual="ga.js"-->
</body>
<!-- InstanceEnd --></html>

Patrick Julicher

Replied 12 Aug 2009 22:19:17

12 Aug 2009 22:19:17 Patrick Julicher replied:

Hi David,

I checked with one of my own template -pages and experienced the same. I'll do some more testing and will get back to you.

Kind regards, Patrick

David Stoltz

Replied 12 Aug 2009 22:20:20

12 Aug 2009 22:20:20 David Stoltz replied:

Thanks for your help.

Miroslav Zografski

Replied 13 Aug 2009 11:16:48

13 Aug 2009 11:16:48 Miroslav Zografski replied:

Hello David,

The problem is that the extension cannot find the head tag... so the whole tag should be included into the editable region.

Regards,

David Stoltz

Replied 13 Aug 2009 14:16:00

13 Aug 2009 14:16:00 David Stoltz replied:

Not sure what you mean by "the whole tag should be included in the editable region".

Please explain.

Miroslav Zografski

Replied 13 Aug 2009 14:38:55

13 Aug 2009 14:38:55 Miroslav Zografski replied:

Hello David,

The tag is defined by <head> - start, and </head> - end.
In order for extension to include its css link it needs to recognize the beginning of the tag, which in your case is excluded from Editable region "head" therefore is "invisible" for the extension.
You should Edit your template editable region "head" so it includes <head> tag from its start to its end.

Regards,

David Stoltz

Replied 13 Aug 2009 14:51:28

13 Aug 2009 14:51:28 David Stoltz replied:

I disagree....

I think it would make more sense to make the extension recognize this code:



All other extensions can "see" this editable region area - which is within the HEAD area - after all, this code is added automatically for templates so extensions can continue to use the HEAD area. I'm not sure why this extension doesn't "see" it, but it sure would make life easier.

Miroslav Zografski

Replied 13 Aug 2009 15:03:34

13 Aug 2009 15:03:34 Miroslav Zografski replied:

Hello David,

I'm not saying that you must always do this. I just say how the extension works now.
It is taken what is necessary to correct this behavior.

Regards,

David Stoltz

Replied 13 Aug 2009 15:05:17

13 Aug 2009 15:05:17 David Stoltz replied:

Oh ok....

So hopefully the next version will look for this area to insert its code....

I can live with that...

Thanks! I'll be eagerly awaiting the next release ;-)

Patrick Julicher

Replied 17 Aug 2009 23:57:32

17 Aug 2009 23:57:32 Patrick Julicher replied:

David,

This issue has been reported to the developers.

Kind regards, Patrick

Chris Sanlon

Replied 04 Sep 2010 19:36:01

04 Sep 2010 19:36:01 Chris Sanlon replied:

I have started using this extension and had the same problem as above. However I see that there has been no released update to 1.0.1 since this issue was reported to the developers over a year ago now. Is there going to be any update to this or do we just have to keep messing around with the automatically generated template code to make this extension usuable?

thanks,

chris

Miroslav Zografski

Replied 10 Sep 2010 12:29:16

10 Sep 2010 12:29:16 Miroslav Zografski replied:

Hello Chris,

The issue is addressed however not yet fixed because of some other more important updates and new products have been scheduled and released. There is still no date set for Update of CSS Form Designer.

Regards,

CSS Form Designer Support Product Page

PROBLEMS

Error when trying to use latest version

Replies

Reply to this topic