Re: Problem with adding/browsing or closing Web Parts on Sharepoin

Out of the box your page is Ghosted, editing it with FrontPage may Unghost
it. Just so we're on the same page. :)

Hitting the page with FrontPage may unghost it, but if the only thing you do
is add web parts reghosting the page afterwards shouldn't be a problem. You
shouldn't lose anything.

tk
"Crockett" <Crockett@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:545C652C-07B9-4019-9987-FC88DEAF0BEC@xxxxxxxxxxxxxxxx
Thanks for your response. I have not tried using FrontPage yet. Will
this
cause my page to be Ghosted or UnGhosted(can't remember wich one) so that
later down the road any changes we have made and fixes applied might mess
up
the home page again. Or is this ok because we will be putting the home
page
back in that is supposedly shipped with SPS and then modifying it again to
resemble our current site structure.

"Cornelius J. van Dyk [MVP]" wrote:

The deafening silence tells me most would agree that something on the
site is pretty messed up.
Have you tried using FrontPage (I can't believe I'm recommending this!)
to edit the page and remove it that way?

--
Hope this helps.

Thanks
C
http://spaces.msn.com/cjvandyk



"Crockett" <Crockett@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Crockett@xxxxxxxxxxxxxxxxxxxxxxxxx:

Hello,

When I try to add a WebPart to a Sharepoint homepage (via Modify Shared
page
- Add web parts - Browse) or try to close and existing one I get an
error
"Request Timed out".

This problem occurs on our WSS production site. I have admin rights and
the
control is allowed to be closed. We are investigating a problem with
the
control taking a long time to load its data. SQL Server is running a
long
query so we want to remove the control from the main page but can not
because
of this error.

Page also times out when trying to list the controls on the page using
the
appended "?contents=1". I have also tried to extend the timeout
periods of
the webpartworkitem to an extreemly long time and the webserver timeout
period with no success.

Does anyone know what could cause this problem?
Does anyone know if I can replace the home page with the original
shipped
with SPS without losing the rest of our site structure?




.

Relevant Pages

  • Re: Lots of SharePoint stuff
    ... Open the US and Can pages in FrontPage 2003, right-click the list form ... You can also use step 4 above to add HTML controls, control visibility, etc. ... SharePoint won't maintain the web part and it's a pain to add new fields. ...
    (microsoft.public.sharepoint.windowsservices)
  • Viewing my own webparts in Frontpage
    ... Are you trying to implement a designer for the control? ... When you load a web part in via Frontpage 2003 it is ... initialized in design mode. ... listed as a safe control. ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: UnGkost a page
    ... You can't unghost. ... WEBDAV or use the WSSAPI and put it back on the filesystem. ... FrontPage is a GREAT *DEVELOPMENT* tool. ... open the file system path in development. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: ASP.NET
    ... using includes in aspx pages isn't really the best way to go. ... Firstly make your control like this ... > I think if VS was a little more user friendly the FrontPage users who are ... >> o WYSIWYG design tools like FrontPage and Dreamweaver don't ...
    (microsoft.public.frontpage.client)
  • Re: Getting REndered HTML into FrontPage Web Page
    ... Unless you name the page with .aspx, the server will not know to process the ASP.net control within ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ...
    (microsoft.public.frontpage.client)