| Stefan [MSFT] 2004-10-16, 5:52 pm |
| Hi Charles,
this is also documented here but your problem description seemed to point to
a different problem:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#FBCAE7EE-AE3F-4F1E-B017-2ECD03749FA3
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Charles Bell" <charlie@bang.co.uk> wrote in message
news:#zRq3FtsEHA.636@TK2MSFTNGP09.phx.gbl...
> Stefan,
>
> Thanks for the reply. We were using the Add method to populate the list,
but
> it still wasn't working.
>
> In fact, further investigation showed that ALL of the placeholders were
> losing the data entered into them. After a lot of investigation we found
the
> following situtation was causing the problem:
>
> 1) The page template (in VS.net) was made up of a number of UserControls
> (not CMS controls - standard web user controls) that we'd used to hold
> common data, the site navigation block, common site footer, etc.
>
> 2) The web-designer had recently supplied an updated version of the page
> layout - at the top of the page is a textbox used for site searches. This
> block of code was extracted out into our "Page Header" user control, thus
> updating all of the templates that used this UserControl.
>
> 3) What we'd missed was that the HTML editor program used by the designer
> (Dreamweaver in this case) had added a standard HTML <form> block around
the
> search box. Note: this wasn't a runat=server form, just a straight <form>
> tag. If it HAD been a runat=server form, then it would have caused a
runtime
> exception because it would have conflicted with our outer runat=server
form
> in the CMS Template.
>
> 4) It seems that the standard form was somehow tripping up CMS when it was
> trying to process the data entered by the user. We could easily spot this
> with the dropdown lists because they kept coming back with the wrong data.
> Then we noticed that checkboxes within our CMS Custom Controls were doing
> the same, and then we noticed the HTML controls were doing it too etc,
etc.
>
> So, in short, the resolution was to remove the <form> from the header
> UserControl and that fixed the problem!!
>
> A cautionary tale (with a nice resolution) for anyone else who finds that
> CMS is suddenly saving none of their data and don't know why.
>
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:eu7oL8qsEHA.904@TK2MSFTNGP11.phx.gbl...
using[vbcol=seagreen]
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm[vbcol=seagreen]
http://www.gotdotnet.com/community/...t+S
erver[vbcol=seagreen]
n[vbcol=seagreen]
DateTime[vbcol=seagreen]
evaluates[vbcol=seagreen]
>
>
|