P
Peter Ensor
I am having a data persistence problem with the SimpleUI option in IE7. The
scenario is that we use a sharepoint site that has a webpart that points to
the PWA site and has SimpleUI=127. This sharepoint site is my IE7 home page.
The webpart shows the GANTT chart from Project Centre
When I then use a link to the PWA site, the SimpleUI setting is maintained.
I have inserted a SimpleUI=0 for the first link to get to the home page but
when I then select Projects from the horizontal menu bar, the SimpleUI=127 is
applied - leaving me without the menus on that page. If I append the URL with
SimpleUI=0 and refresh then the page behaves normally.
I have tried disabling the data persistence security option but it didn't
appear to make any difference.
If I close the IE7 session and reopen it or open a new tab in IE7 and type
the URL (http://pheonix/projectserver/Views/PortfolioView.asp?_oid=-1) then
the page behaves normally. It just seems to occur if you continue on in the
same tab or open a new session from the original one.
The problem does not occur in IE6.
Any solutions?
Thanks,
Peter.
scenario is that we use a sharepoint site that has a webpart that points to
the PWA site and has SimpleUI=127. This sharepoint site is my IE7 home page.
The webpart shows the GANTT chart from Project Centre
When I then use a link to the PWA site, the SimpleUI setting is maintained.
I have inserted a SimpleUI=0 for the first link to get to the home page but
when I then select Projects from the horizontal menu bar, the SimpleUI=127 is
applied - leaving me without the menus on that page. If I append the URL with
SimpleUI=0 and refresh then the page behaves normally.
I have tried disabling the data persistence security option but it didn't
appear to make any difference.
If I close the IE7 session and reopen it or open a new tab in IE7 and type
the URL (http://pheonix/projectserver/Views/PortfolioView.asp?_oid=-1) then
the page behaves normally. It just seems to occur if you continue on in the
same tab or open a new session from the original one.
The problem does not occur in IE6.
Any solutions?
Thanks,
Peter.