|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 172
Location: Pittsburgh, Pennsylvania, USA
|
Using Umbraco v3, in the content section of the admin module, when creating a new content item the dialog window that opens is too small to see the all the content. It looks like it is the correct size for the v2 new content dialog but not for the new v3 presentation. The first couple times the window is opened it is the correct size but then it gets small and will not return to the correct size until logging out and back in.
Any suggestions on how to fix this? It is a known issue?
thanks...
Jason
|
|
Rank: Fanatic
Joined: 10/9/2006
Posts: 333
|
i have experienced this same situation -- i am interested to know what the issue/solution is.
bootnumlock - aka bob baty-barr [ http://www.baty-barr.com] Level 1 Certified!
|
|
Rank: Addict
Joined: 7/19/2006
Posts: 702
Location: Århus, Denmark
|
Does this happen when upgrading an existing 2.x site, or from a clean 3.x install? It happened to me once, but it turned out it was some cached .js and .css files from the old v2.x site. try clearing the browsers temp files and see if that helps?
Morten Bock - Level 2 certified - My danish blog with a few english posts | CodeGarden on Facebook
|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 172
Location: Pittsburgh, Pennsylvania, USA
|
It was an upgraded site. I've cleared all the cache as of this morning so we'll see what the content editor reports. Hopefully it is a cached file issue.
Jason
|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 172
Location: Pittsburgh, Pennsylvania, USA
|
so far it appears that clearing the cache has resolved the issue. Thanks for the suggestion Bob.
Jason
|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 172
Location: Pittsburgh, Pennsylvania, USA
|
well that wasn't the solution. We've cleared the cache and on some machines it seems to resolve the issue but not on others. Anyone else experiencing this?
Jason
|
|
Rank: Devotee
Joined: 1/10/2008
Posts: 55
Location: London
|
Hi,
I'm experiencing the same problem. The only workaround I found is to log out and log back in.
The problem has been experienced on different PC's, using IE6 (SP1 or 2)
we're using 3.0.5
any solution for this ?
thanks,
seb
Bingo maniak
|
|
|
Guest |