Support Forum
Support Forum
Offline
Offline
depends when you did it... fighting another wp 3.2 vs 3.3 incompatibility... seriously thinking about punting wp 3.2 support in the alpha... definitely will be in the beta...
just commits the final fix, I think... please try an svn up again...
Visit Cruise Talk Central and Mr Papa's World
Offline
No luck with the upgrade after svn up.
I'm seeing no errors in my logs, and setting WP_DEBUG to true isn't showing me anything special.
When going to WP's dashboard is no js errors.
When clicking the "Forum" link in WP's backend (left menu) I get one js error in the Firebug console
$.widget is not a function
http://www.mydevserver.com/wp-.....?ver=3.2.1
Line 81::
Then when clicking the "Perform Upgrade" after clearing the js error it just hangs and shows "Upgrade in progress - please wait" and the throbber. At this time I see two more js errors
$.widget is not a function
http://www.mydevserver.com/wp-.....?ver=3.2.1
Line 81:
document.getElementFromId is not a function
http://www.mydevserver.com/wp-.....?ver=3.2.1
Line 144
WP_DEBUG does show some notices under the left WP menu Forum > Upgrade Simple:Press link:
Notice: Uninitialized string offset: 1 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 117 Notice: Uninitialized string offset: 2 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 142 Notice: Uninitialized string offset: 2 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 148 Notice: Uninitialized string offset: 2 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 149 Notice: Uninitialized string offset: 0 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 153 Notice: Uninitialized string offset: 2 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 155 Notice: Uninitialized string offset: 2 in /problem-with-post-edit-buttonome/leeh/public_html/wp-admin/menu-header.php on line 160
Other then that... I've no freak'n idea how to help you debug this?
Edited because my pasting destroyed forum layout 
Offline
yes, thats the error I was getting running wp 3.2... but the latest updates last night got rid of them...
are you sure you did an svn up? It should have put the file
simple-press/sp-startup/install/resources/jscript/ui.progressbar.js
back... please verify you have that file...
and make sure you had cleared your browser cache...
Visit Cruise Talk Central and Mr Papa's World
Offline
Please svn up again... just committed another change... have one hell of a time keeping sp 5.0 working with wp 3.2... It really requires wp 3.3... trying to limp through to the beta where 3.3. will be required...
Visit Cruise Talk Central and Mr Papa's World
Offline
It upgrades now 🙂
Although... since my last post I rolled back my svn to my last working version. So I could work a bit on my SP plugin.
So after reading your reply #4 I did a svn up to verify if the file existed or not. But didn't bother checking as upgrade worked.
*Shrug* Can't confirm what fixed it, your commit or my messing with svn. But I'm pleased all the same 🙂
Offline
think it was last fix... still found another way wp 3.2 js loading could fail... I didnt get it but guessing you did...
should be good now... thanks...
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)