FrontPage corrupting sites

I am being told by my Sharepoint administrative team that they have revoked
FrontPage privileges from everyone because FrontPage is corrupting Sharepoint
sites. Is there any data anywhere to validate this claim?

Thank you

DaveCohoon
Thu Jun 08 12:29:02 CDT 2006

If the user has the correct permissions, they could change the site pages. If
they didn't know what they were doing - it's possible that they could create
error when a site tries to render the html, looking as if the site was
corrupt.

This wouldn't affect the data however. I've also have seen some tools that
can strip the frontpage customizations out of sharepoint sites for that very
reason.

"Deb" wrote:

> I am being told by my Sharepoint administrative team that they have revoked
> FrontPage privileges from everyone because FrontPage is corrupting Sharepoint
> sites. Is there any data anywhere to validate this claim?
>
> Thank you

Deb
Thu Jun 08 12:38:01 CDT 2006

No. They're claiming that simple use of FrontPage like for changing the
QuickLaunch bar, etc., causes corruption. I had it happen to a site the
other day. I could view default.aspx but I could not get into design mode or
open it in FrontPage. They're using this as an example of why FrontPage use
needs to be restricted. I think it's hogwash and can find no documentation
in the MS knowledgebae or anywhere else to support their position that
FrontPage corrupts Sharepoint just with general usage.




"Dave Cohoon" wrote:

> If the user has the correct permissions, they could change the site pages. If
> they didn't know what they were doing - it's possible that they could create
> error when a site tries to render the html, looking as if the site was
> corrupt.
>
> This wouldn't affect the data however. I've also have seen some tools that
> can strip the frontpage customizations out of sharepoint sites for that very
> reason.
>
> "Deb" wrote:
>
> > I am being told by my Sharepoint administrative team that they have revoked
> > FrontPage privileges from everyone because FrontPage is corrupting Sharepoint
> > sites. Is there any data anywhere to validate this claim?
> >
> > Thank you

Todd
Thu Jun 08 15:44:00 CDT 2006

Certainly FrontPage can be used to make changes that can cause problems.
I've only seen one change that can be made with FrontPage that couldn't not
be fixed by reghosting the page. That had to do with editing the NavNodes.
I had to rebuild them by hand. Besides that, I have found reghosting the
page that has been "corrupted" unbreaks anything that has been done in
FrontPage.

tk
"Deb" <Deb@discussions.microsoft.com> wrote in message
news:5EE7044B-7669-4A7B-8EC7-3AD93AFEA624@microsoft.com...
> No. They're claiming that simple use of FrontPage like for changing the
> QuickLaunch bar, etc., causes corruption. I had it happen to a site the
> other day. I could view default.aspx but I could not get into design mode
> or
> open it in FrontPage. They're using this as an example of why FrontPage
> use
> needs to be restricted. I think it's hogwash and can find no
> documentation
> in the MS knowledgebae or anywhere else to support their position that
> FrontPage corrupts Sharepoint just with general usage.
>
>
>
>
> "Dave Cohoon" wrote:
>
>> If the user has the correct permissions, they could change the site
>> pages. If
>> they didn't know what they were doing - it's possible that they could
>> create
>> error when a site tries to render the html, looking as if the site was
>> corrupt.
>>
>> This wouldn't affect the data however. I've also have seen some tools
>> that
>> can strip the frontpage customizations out of sharepoint sites for that
>> very
>> reason.
>>
>> "Deb" wrote:
>>
>> > I am being told by my Sharepoint administrative team that they have
>> > revoked
>> > FrontPage privileges from everyone because FrontPage is corrupting
>> > Sharepoint
>> > sites. Is there any data anywhere to validate this claim?
>> >
>> > Thank you

Engelbert
Thu Jun 08 23:31:52 CDT 2006

One interesting thing in this discussion so far is that no-one has asked you
*which* version of FrontPage. If someone is using FP 2002 to amend WSS sites
then that is your reason.

Otherwise doing standard things in FP 2003 (such as sorting Quick Launch and
amending the menu bar) has never caused me any problems. Problems after
amending the code incorrectly are naturally going to happen but those have
nothing much to do with FP 2003 as such.

Engelbert

"Deb" <Deb@discussions.microsoft.com> wrote in message
news:DE3AA02D-FA35-4E09-A3F5-8E20C6322AC0@microsoft.com...
>I am being told by my Sharepoint administrative team that they have revoked
> FrontPage privileges from everyone because FrontPage is corrupting
> Sharepoint
> sites. Is there any data anywhere to validate this claim?
>
> Thank you

Deb
Fri Jun 09 07:25:02 CDT 2006

Yes, it is FP 2003 we're using and as far as we can tell there is no
justification for our group's representation that FrontPage is corrupting
sites. We have an environment with over 1500 sites and no dedicated
Sharepoint administrator. It's a very bad situation. THrough my
championing, my department has embraced Sharepoint in a big way and developed
a very large reliance on its functionality. My boss is now asking this
question:

What would it take for us to set up our own server and adminster FrontPage
ourselves? Can someonen give me a quick list of hardware and resource
requirements (skillset of person to administer?)

Thanks!

"Engelbert" wrote:

> One interesting thing in this discussion so far is that no-one has asked you
> *which* version of FrontPage. If someone is using FP 2002 to amend WSS sites
> then that is your reason.
>
> Otherwise doing standard things in FP 2003 (such as sorting Quick Launch and
> amending the menu bar) has never caused me any problems. Problems after
> amending the code incorrectly are naturally going to happen but those have
> nothing much to do with FP 2003 as such.
>
> Engelbert
>
> "Deb" <Deb@discussions.microsoft.com> wrote in message
> news:DE3AA02D-FA35-4E09-A3F5-8E20C6322AC0@microsoft.com...
> >I am being told by my Sharepoint administrative team that they have revoked
> > FrontPage privileges from everyone because FrontPage is corrupting
> > Sharepoint
> > sites. Is there any data anywhere to validate this claim?
> >
> > Thank you
>
>
>

hackerm
Fri Jun 09 09:31:03 CDT 2006

I, too, am having the same problem and I am trying to figure out why it
happened and how to fix it.

Is re-ghosting the way to go? If so, do you know of instructions on how to
accomplish it?

Many thanks!

--Heidi

"Todd Klindt" wrote:

> Certainly FrontPage can be used to make changes that can cause problems.
> I've only seen one change that can be made with FrontPage that couldn't not
> be fixed by reghosting the page. That had to do with editing the NavNodes.
> I had to rebuild them by hand. Besides that, I have found reghosting the
> page that has been "corrupted" unbreaks anything that has been done in
> FrontPage.
>
> tk
> "Deb" <Deb@discussions.microsoft.com> wrote in message
> news:5EE7044B-7669-4A7B-8EC7-3AD93AFEA624@microsoft.com...
> > No. They're claiming that simple use of FrontPage like for changing the
> > QuickLaunch bar, etc., causes corruption. I had it happen to a site the
> > other day. I could view default.aspx but I could not get into design mode
> > or
> > open it in FrontPage. They're using this as an example of why FrontPage
> > use
> > needs to be restricted. I think it's hogwash and can find no
> > documentation
> > in the MS knowledgebae or anywhere else to support their position that
> > FrontPage corrupts Sharepoint just with general usage.
> >
> >
> >
> >
> > "Dave Cohoon" wrote:
> >
> >> If the user has the correct permissions, they could change the site
> >> pages. If
> >> they didn't know what they were doing - it's possible that they could
> >> create
> >> error when a site tries to render the html, looking as if the site was
> >> corrupt.
> >>
> >> This wouldn't affect the data however. I've also have seen some tools
> >> that
> >> can strip the frontpage customizations out of sharepoint sites for that
> >> very
> >> reason.
> >>
> >> "Deb" wrote:
> >>
> >> > I am being told by my Sharepoint administrative team that they have
> >> > revoked
> >> > FrontPage privileges from everyone because FrontPage is corrupting
> >> > Sharepoint
> >> > sites. Is there any data anywhere to validate this claim?
> >> >
> >> > Thank you
>
>
>

Todd
Fri Jun 09 09:35:52 CDT 2006

I'm not sure what a server to administer FrontPage is. What did you have in
mind for that?

tk
"Deb" <Deb@discussions.microsoft.com> wrote in message
news:B8CD66B6-3E21-411D-B29E-831C84CA2EF7@microsoft.com...
> Yes, it is FP 2003 we're using and as far as we can tell there is no
> justification for our group's representation that FrontPage is corrupting
> sites. We have an environment with over 1500 sites and no dedicated
> Sharepoint administrator. It's a very bad situation. THrough my
> championing, my department has embraced Sharepoint in a big way and
> developed
> a very large reliance on its functionality. My boss is now asking this
> question:
>
> What would it take for us to set up our own server and adminster FrontPage
> ourselves? Can someonen give me a quick list of hardware and resource
> requirements (skillset of person to administer?)
>
> Thanks!
>
> "Engelbert" wrote:
>
>> One interesting thing in this discussion so far is that no-one has asked
>> you
>> *which* version of FrontPage. If someone is using FP 2002 to amend WSS
>> sites
>> then that is your reason.
>>
>> Otherwise doing standard things in FP 2003 (such as sorting Quick Launch
>> and
>> amending the menu bar) has never caused me any problems. Problems after
>> amending the code incorrectly are naturally going to happen but those
>> have
>> nothing much to do with FP 2003 as such.
>>
>> Engelbert
>>
>> "Deb" <Deb@discussions.microsoft.com> wrote in message
>> news:DE3AA02D-FA35-4E09-A3F5-8E20C6322AC0@microsoft.com...
>> >I am being told by my Sharepoint administrative team that they have
>> >revoked
>> > FrontPage privileges from everyone because FrontPage is corrupting
>> > Sharepoint
>> > sites. Is there any data anywhere to validate this claim?
>> >
>> > Thank you
>>
>>
>>

Deb
Fri Jun 09 10:08:01 CDT 2006

Sorry. I was asking what the hardware requirements are for a FrontPage
install. Can you have it all on one server; i.e., IIS for the Web service
and the WSS database?

"Todd Klindt" wrote:

> I'm not sure what a server to administer FrontPage is. What did you have in
> mind for that?
>
> tk
> "Deb" <Deb@discussions.microsoft.com> wrote in message
> news:B8CD66B6-3E21-411D-B29E-831C84CA2EF7@microsoft.com...
> > Yes, it is FP 2003 we're using and as far as we can tell there is no
> > justification for our group's representation that FrontPage is corrupting
> > sites. We have an environment with over 1500 sites and no dedicated
> > Sharepoint administrator. It's a very bad situation. THrough my
> > championing, my department has embraced Sharepoint in a big way and
> > developed
> > a very large reliance on its functionality. My boss is now asking this
> > question:
> >
> > What would it take for us to set up our own server and adminster FrontPage
> > ourselves? Can someonen give me a quick list of hardware and resource
> > requirements (skillset of person to administer?)
> >
> > Thanks!
> >
> > "Engelbert" wrote:
> >
> >> One interesting thing in this discussion so far is that no-one has asked
> >> you
> >> *which* version of FrontPage. If someone is using FP 2002 to amend WSS
> >> sites
> >> then that is your reason.
> >>
> >> Otherwise doing standard things in FP 2003 (such as sorting Quick Launch
> >> and
> >> amending the menu bar) has never caused me any problems. Problems after
> >> amending the code incorrectly are naturally going to happen but those
> >> have
> >> nothing much to do with FP 2003 as such.
> >>
> >> Engelbert
> >>
> >> "Deb" <Deb@discussions.microsoft.com> wrote in message
> >> news:DE3AA02D-FA35-4E09-A3F5-8E20C6322AC0@microsoft.com...
> >> >I am being told by my Sharepoint administrative team that they have
> >> >revoked
> >> > FrontPage privileges from everyone because FrontPage is corrupting
> >> > Sharepoint
> >> > sites. Is there any data anywhere to validate this claim?
> >> >
> >> > Thank you
> >>
> >>
> >>
>
>
>

Todd
Fri Jun 09 15:30:51 CDT 2006

I would think so. I don't think FrontPage is very intensive at all. I'm
sure if you poke around on Microsoft's site there will be a list of
requirements. I'm guessing any machine that can run WSS will be able to
handle FrontPage.

tk
"Deb" <Deb@discussions.microsoft.com> wrote in message
news:93AF0C6E-6BCC-4806-9D91-584E6108E896@microsoft.com...
> Sorry. I was asking what the hardware requirements are for a FrontPage
> install. Can you have it all on one server; i.e., IIS for the Web service
> and the WSS database?
>
> "Todd Klindt" wrote:
>
>> I'm not sure what a server to administer FrontPage is. What did you have
>> in
>> mind for that?
>>
>> tk
>> "Deb" <Deb@discussions.microsoft.com> wrote in message
>> news:B8CD66B6-3E21-411D-B29E-831C84CA2EF7@microsoft.com...
>> > Yes, it is FP 2003 we're using and as far as we can tell there is no
>> > justification for our group's representation that FrontPage is
>> > corrupting
>> > sites. We have an environment with over 1500 sites and no dedicated
>> > Sharepoint administrator. It's a very bad situation. THrough my
>> > championing, my department has embraced Sharepoint in a big way and
>> > developed
>> > a very large reliance on its functionality. My boss is now asking this
>> > question:
>> >
>> > What would it take for us to set up our own server and adminster
>> > FrontPage
>> > ourselves? Can someonen give me a quick list of hardware and resource
>> > requirements (skillset of person to administer?)
>> >
>> > Thanks!
>> >
>> > "Engelbert" wrote:
>> >
>> >> One interesting thing in this discussion so far is that no-one has
>> >> asked
>> >> you
>> >> *which* version of FrontPage. If someone is using FP 2002 to amend WSS
>> >> sites
>> >> then that is your reason.
>> >>
>> >> Otherwise doing standard things in FP 2003 (such as sorting Quick
>> >> Launch
>> >> and
>> >> amending the menu bar) has never caused me any problems. Problems
>> >> after
>> >> amending the code incorrectly are naturally going to happen but those
>> >> have
>> >> nothing much to do with FP 2003 as such.
>> >>
>> >> Engelbert
>> >>
>> >> "Deb" <Deb@discussions.microsoft.com> wrote in message
>> >> news:DE3AA02D-FA35-4E09-A3F5-8E20C6322AC0@microsoft.com...
>> >> >I am being told by my Sharepoint administrative team that they have
>> >> >revoked
>> >> > FrontPage privileges from everyone because FrontPage is corrupting
>> >> > Sharepoint
>> >> > sites. Is there any data anywhere to validate this claim?
>> >> >
>> >> > Thank you
>> >>
>> >>
>> >>
>>
>>
>>

Todd
Fri Jun 09 15:29:58 CDT 2006

I would start with reghosting the page. Google for the "Ghost Hunter" web
part. That's the easiest way I know to reghost a page. There's a newer,
better web part that does it too, but the name escapes me.

tk
"hackerm" <hackerm@discussions.microsoft.com> wrote in message
news:84F400CF-81A7-4C15-9AD8-14E839677286@microsoft.com...
> I, too, am having the same problem and I am trying to figure out why it
> happened and how to fix it.
>
> Is re-ghosting the way to go? If so, do you know of instructions on how to
> accomplish it?
>
> Many thanks!
>
> --Heidi
>
> "Todd Klindt" wrote:
>
>> Certainly FrontPage can be used to make changes that can cause problems.
>> I've only seen one change that can be made with FrontPage that couldn't
>> not
>> be fixed by reghosting the page. That had to do with editing the
>> NavNodes.
>> I had to rebuild them by hand. Besides that, I have found reghosting the
>> page that has been "corrupted" unbreaks anything that has been done in
>> FrontPage.
>>
>> tk
>> "Deb" <Deb@discussions.microsoft.com> wrote in message
>> news:5EE7044B-7669-4A7B-8EC7-3AD93AFEA624@microsoft.com...
>> > No. They're claiming that simple use of FrontPage like for changing
>> > the
>> > QuickLaunch bar, etc., causes corruption. I had it happen to a site
>> > the
>> > other day. I could view default.aspx but I could not get into design
>> > mode
>> > or
>> > open it in FrontPage. They're using this as an example of why
>> > FrontPage
>> > use
>> > needs to be restricted. I think it's hogwash and can find no
>> > documentation
>> > in the MS knowledgebae or anywhere else to support their position that
>> > FrontPage corrupts Sharepoint just with general usage.
>> >
>> >
>> >
>> >
>> > "Dave Cohoon" wrote:
>> >
>> >> If the user has the correct permissions, they could change the site
>> >> pages. If
>> >> they didn't know what they were doing - it's possible that they could
>> >> create
>> >> error when a site tries to render the html, looking as if the site was
>> >> corrupt.
>> >>
>> >> This wouldn't affect the data however. I've also have seen some tools
>> >> that
>> >> can strip the frontpage customizations out of sharepoint sites for
>> >> that
>> >> very
>> >> reason.
>> >>
>> >> "Deb" wrote:
>> >>
>> >> > I am being told by my Sharepoint administrative team that they have
>> >> > revoked
>> >> > FrontPage privileges from everyone because FrontPage is corrupting
>> >> > Sharepoint
>> >> > sites. Is there any data anywhere to validate this claim?
>> >> >
>> >> > Thank you
>>
>>
>>