I believe this only applies to sites that were created after the entry was added … and you need to do an IISRESET.

I don’t think the part about only affecting new sites is correct as I have turned it on and off in the past to temporarily allow people access via FrontPage (DVWP development needs) and haven’t experienced that limitation.

when the user tries to open the site in FrontPage 2003, they just receive a friendly error message that it is not allowed. Note this ONET change will not stop previous versions of FrontPage to be used to open sites.

The DisableWebDesignFeatures attribute of the Project element is a
hotspot in the ONET.XML file. The current settings will always be read
from the cached ONET.XML file for each site definition. Changes to this
attribute take effect the next time the application pool is recycled
(overnight by default).

Interesting, I don't think we have ever altered application pool
recycling times (if that is how you would refer to that)... when I
update this in ONET and do an IIS reset, the changes are active then and
there.

didn't know that an IIS Reset was needed either since I was under the impression that ONET was always read from in some manner when a page  was accessed.

Nonetheless, a little clarification. If a site has been "Frontpaged", i.e. unghosted (aye tis a sad day to remove the linens for us ghosts), it will cease to be able to be edited in FrontPage once the 'wdfopensite' attribute has been added to the ONET.xml.

Just wanted to make that clear so that anyone reading wouldn't think that if a site had been unghosted and wdfopensite was added that they'd continue to be able to edit it. If as a system administrator you wanted to then go in and start reghosting so that sites would adhere to the standard template you'd go and pull down something like ReGhost.NET or Ghost Hunter available at the following respectively:

www.gotdotnet.com/.../workspace.aspx

http://www.bluedoglimited.com/Downloads/pages/Web%20Part%20Toolkit.aspx

Please note that both of these utilities will touch the database and are not supported by Microsoft -- use at your own risk. Typically I'll download a copy of a site via smigrate with a usermap generated using the WSS User Util (thanks Keith Richie!) and then reghost it on a separate development server  and then push it back up.

another is that you can control what is and isn’t allowed to be done with FrontPage. For example backup, restore, import, theme application, etc.

For a full list of what you can disable and the values for each, go to this article and search on “Feature to Disable”. You will find a table about midway through the article with an explanation of the all the possible values.

www.microsoft.com/.../fp03sps.mspx

Most things cached by SharePoint can be cleared using the following
command (if you have Windows Server 2003):
C:\WINDOWS\system32\cscript.exe C:\WINDOWS\system32\iisapp.vbs /a
MSSharePointPortalAppPool /r

I don't remember is recycling the application pool
(MSSharePointPortalAppPool in my example above) will reset the ONET but
I think it will. You can also stop and start the application pool in the
IIS snap in or set it up to recycle on a cycle other than once every 24
hours.