Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Seeing "Half Ghosts"

  Asked By: Adam    Date: Mar 01    Category: Sharepoint    Views: 960

Someone might verify and/or ask Microsoft about this:

I have found that in some situations you will have three different
view of the same web part page based on whether you are viewing it
with a browser, editing it with FrontPage or editing it with
Notepad! In fact, the file seems to be simultaniously ghosted for
browser and Frontpage, while unghosted for notepad.

In my experimentation to see what happens when a page is unghosted
via page edit... If you "create a web part page" based on an STS web
part page template, then view the new page in your browser you will
see any up-to-date template file edits. If you edit a page via
FrontPage 2003, you will be given a copy of the page to edit as it
was cached from the first web hit since the server was started (or
restarted). Even If the template file was edited during the interim
and a page reload showed your changes, it will look like the page
has reverted back in FrontPage 2003 to an unedited state (because
the template was modified while the site was in use).

If that same web part page is edit using Notepad from the explorer
view, the file loaded into notepad may be different. In fact, it
seems like the first time you load the page into notepad (even if
you never save it), it is THAT version of the file is used for any
further edits with notepad. If you edit the file then view the file
with frontpage afterward, get the newest one, but notepad will be
given the old one.

It appears that browser reload always uses the current ghosted
template file, editing with Frontpage uses the cached copy, and
editing with notepad probably uses a copy instantiated during the
first notepad viewing.

Feel free to verify:

Start IIS
Browse to site
Create Web Part Page
Add web part
Browse directly to new page (remove "?PageView=Shared" from
after .aspx)
Modify corresponding spstd?.aspx file (put "AB" inside BODY tag)
Reload new page in browser ("AB" appears)
Issue IISReset on server
Reload new page in browser ("AB" appears)
Modify corresponding spstd?.aspx file (put "ABCD" inside BODY tag)
Reload new page in browser ("ABCD" appears)
Choose Edit with FrontPage from Internet Explorer ("AB" appears)
Go to "Shared Documents", explorer view.
* Right click on new page, choose open with notepad ("AB" appears)
Issue IISReset on server
Reload new page in browser ("ABCD" appears)
Modify corresponding spstd?.aspx file (put "ABCDEF" inside BODY tag)
Reload new page in browser ("ABCDEF" appears)
Choose Edit with FrontPage from Internet Explorer ("ABCD" appears)
Go to "Shared Documents", explorer view.
* Right click on new page, choose open with notepad ("AB" appears)

Note: Even if you go to Shared Documents, explorer view and right
click "open with FrontPage", you'll end up with the recent changes,
where "open with notepad" from the same location will still give you
a stale file.

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Jerrod Collier     Answered On: Mar 01

I think what you are seeing are the differences between the direct mode
page in IIS cache, the unghosted page  in the database, and a mismatch
between the browser  and FrontPage that can be rectified using F5. I'll
try to step thru your example below tomorrow.

 
Answer #2    Answered By: Jacob Green     Answered On: Mar 01

This was curious behavior that I don't think it was a reload
problem, but feel free to prove me wrong.

My purpose of posting was to make the information available to the
community in case someone hit the situation at a later date. I think
this MAY eventually cause me a problem in my setup if someone plays
with aspx file in the library explorer view.

This isn't critical, just interesting... sheds a strange light on
what is happening... and potentially a bug.

 
Answer #3    Answered By: Spencer Bradley     Answered On: Mar 01

Here is a summary of my experience <my comments in angle brackets>:

Start IIS
Browse to site
Create web  Part Page
Add web part
Browse directly to new page  (remove "?PageView=Shared" from after
.aspx)
<I don't understand why is an iisreset not required, I modified a site
definition page I expected to be cached by IIS>
Modify corresponding spstd?.aspx file (put "AB" inside BODY tag)
Reload new page in browser  ("AB" appears)
Issue IISReset on server
Reload new page in browser ("AB" appears)
Modify corresponding spstd?.aspx file (put "ABCD" inside BODY tag)
<Again why is an iisreset not required?>
Reload new page in browser ("ABCD" appears)
<I cannot do the next step without an iisreset, error: "Couldn't open
file C:\Documents and Settings\tbleeker\Desktop.">
<I can't get past this error without an iisreset, I tried the above
steps three times>
<If I do an iisreset, I see ABCD in the next step>
Choose Edit with FrontPage from Internet Explorer ("AB" appears)
Go to "Shared Documents", explorer view.
<In the next step, I see ABCD, but I wager that is because I had to do
an iisreset to proceed>
* Right click on new page, choose open with notepad ("AB" appears)
Issue IISReset on server
Reload new page in browser ("ABCD" appears)
<I didn't go any further because my environment is behaving differently
than yours>
Modify corresponding spstd?.aspx file (put "ABCDEF" inside BODY tag)
Reload new page in browser ("ABCDEF" appears)
Choose Edit with FrontPage from Internet Explorer ("ABCD" appears)
Go to "Shared Documents", explorer view.
* Right click on new page, choose open with notepad ("AB" appears)


Even though I couldn't recreate your scenario, I can see your point. It
seems like these pages don't get ghosted like other direct mode pages.
They appear to be loading directly from the file system every time. Add
FrontPage unghosting and access via Web Dav to the mix and things get
even odder.

 
Didn't find what you were looking for? Find more on Seeing "Half Ghosts" Or get search suggestion and latest updates.




Tagged: