nforcer
04-01-2011, 10:34 PM
First, thanks in advance to whoever can help.
Here's my situation.
I like to keep my vB software up to date but after the 4.1.x upgrades, I've been unable to edit my Widgets....any of them.
Here's what happens.
IE 8 and 9beta - when I click the "Configure" link for the Widget I want to edit, I get the black box with the rolling sun-looking wheel and nothing else happens. It appears like it wants to load something, but its stuck in a stalemate.
FireFox 3 and 4 - I see the black box, the animated icon, then it closes having accomplished nothing.
Chrome - same as FireFox but quicker (guess that proves Chrome IS still faster than FF :P)
Now, I vaguely recall something about when you change "Point CMS default to index.php" under Content Management , that it breaks a bunch of links, but I was able to fix this via someone else's suggestion (found on this board) but I can no longer find it.
I remember having it fixed, but when I upgraded to 4.1.x to .2 (and later .3) it broke it - maybe it was a file change that became overwritten in the upgrades???
Is anyone else having this issue? Anyone have a suggestion?
Thanks in advance!
-Travis
Here's my situation.
I like to keep my vB software up to date but after the 4.1.x upgrades, I've been unable to edit my Widgets....any of them.
Here's what happens.
IE 8 and 9beta - when I click the "Configure" link for the Widget I want to edit, I get the black box with the rolling sun-looking wheel and nothing else happens. It appears like it wants to load something, but its stuck in a stalemate.
FireFox 3 and 4 - I see the black box, the animated icon, then it closes having accomplished nothing.
Chrome - same as FireFox but quicker (guess that proves Chrome IS still faster than FF :P)
Now, I vaguely recall something about when you change "Point CMS default to index.php" under Content Management , that it breaks a bunch of links, but I was able to fix this via someone else's suggestion (found on this board) but I can no longer find it.
I remember having it fixed, but when I upgraded to 4.1.x to .2 (and later .3) it broke it - maybe it was a file change that became overwritten in the upgrades???
Is anyone else having this issue? Anyone have a suggestion?
Thanks in advance!
-Travis