Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Danger in Customizing WSS with FrontPage?

  Asked By: Jamie    Date: May 23    Category: Sharepoint    Views: 574

Customized (or unghosted) pages:

1) Break the excellent separation between presentation and data provided
by direct-mode pages, 2)
2) Decrease the performance of the page by up to 30%
3) Eliminate the ability to make global changes to existing instance
4) Will cause additional work when you upgrade from v2 to v3

I run a ghosted-only shop. One way to help make that a reality is to
disable FrontPage 2003 from editing production Webs. This can be done by
setting the DisableWebDesignFeatures attribute to wdfopensite in the
Project element of each Site Definition's ONET.XML file. This is a hot
spot so you can alter its value even after Webs have been created on it.

DisableWebDesignFeatures blocks certain editing features that are used
in Microsoft FrontPage. Other values can be added using delimited

The CEWP can be used to customize instance pages or using CSS and
JavaScript you can impact all specific pages by making changes to the
direct-mode page, all pages within a given Site Definition, or all pages
across the entire farm. I have a blog post about how to create
maintainable customizations at all these levels.

I also practice using a dummy page to create and then export DVWPs. I
much prefer using the Web Service DVWP because it can be deployed easier
than any other DVWP and it can be secured outside of the Web Part.



No Answers Found. Be the First, To Post Answer.

Didn't find what you were looking for? Find more on Danger in Customizing WSS with FrontPage? Or get search suggestion and latest updates.