Support Forum
Support Forum
Offline
This is the error msg from the WP dashboard/Simple Press upgrade page:
Upgrade Aborted
current build: 12017
{"status":"success","type":"upgrade","section":12020,"response":"Build upgrade section 12020 executing. Status: success
","error":""}
Offline
The interesting thing here is that there were no upgrade commands or actions between the close of 5.5.2 (12017) and 5.5.3 (12020). So the problem came along when nothing was actually being done except updating the version number.
When we see this it is always a scripting conflict - or - something, somewhere is hijacking the upgrade AJAX call and adding requests to it. If you have been through a successful uprgade process before then you should look closely at what might have been installed and made active since then as that is probably going to be the cause of the issue. Or what has also been updated - like the WP theme.
I would guess that if you witched to the default Wp theme briefly and deactivated any recent plugin additions then the upgrade would be processed quite normally.
 |
YELLOW
SWORDFISH
|
Offline
The other odd thing is that when I look at the code (dashboard > plugins > simple:press > edit link > source code) the plugin seems to be updated to 5.5.6, but the "$LastChangedDate" shows the last change in April of this year...odd! Here is the beggining of the code:
<?php
/*
Plugin Name: Simple:Press
Version: 5.5.6
Plugin URI: https://simple-press.com
Description: Fully featured but simple page-based forum
Author: Andy Staines & Steve Klasen
Author URI: https://simple-press.com
WordPress Versions: 4.2 and above
For full acknowledgements click on the copyright/version strip at the bottom of forum pages
$LastChangedDate: 2015-04-22 18:07:43 -0700 (Wed, 22 Apr 2015) $
$Rev: 12749 $
Offline
that is updated as it goes...
so did you try what Andy asked you to do?
Visit Cruise Talk Central and Mr Papa's World
Offline
No, I didn't try what Andy suggested, mostly because I'm not tech-savy enough to know how to switch over to the WP theme, other than switching over completely on my production site (no staging/dev site currently - but I'm working on getting one) and the only good time to mess around with production in my experience, is in the wee hours of the morning --
Would I still need to do that since the upgrade has already occurred? I would think not, but that is why I'm on this side of the keyboard and you are on the other side 🙂 The forum isn't working at all and is beginning to impact our revenue, so I am hoping to find a solution sooner than later :/
Offline
The only other way to find the issue is to use the web console tool and monitor activity when the upgrade is run. The script console will show (a) if there are any obvious errors causing the issue and (b) the request and return values from the AJAX call - often more revealing.
But you have not really responded to my questions. I.e., have you been through a successful upgrade before and, if so, what has been changed/added in the interim?
We have found over the years that this behaviour quite genuinely is most usually, if not always, caused by such a conflict and most often by a theme or plugin that does not strictly adhere to the WP API. Sometimes just looking at what is being loaded by other resources can suggest a culprit. Bit generally - for the less tech-savvy, changing he theme and then possibly plugins is usually easier and quicker to deal with.
|
YELLOW
SWORDFISH
|
All RSS1 Guest(s)