Wow – that fell at the very first step in the upgrade which involves changes to the database structure.

Every now and then we can trace an upgrade failure to external factors such as what other scripts are active. Is there a chance you could start by switching the site to use the wp default theme and then trying the upgrade again? if it still fails the same way then it might be a plugin.

the alternative is that you donlt have access to make these changes to the database but that is usually unlikely.

No luck.

Swithed to Twenty Eleven and run the upgrade. Same error msg

Should I try to upgrade to 5.1.3 instead since that worked just fine on the other server (with same theme installed as this server)? Just deactivate 5.1.4, delete plugin and then install 5.1.3? Not sure if I still got the zip file, but maybe you guys could give me a link?

Thanks for quick repsons btw

It really shouldn’t make any difference byt just in case there is no harm in trying!
You can get 5.1.3 zip here:
https://simple-press.com/download-manager.php?id=653

Same errormsg with 5.1.3. Any suggestion what to do next?
You meantion that I might miss some permissions in the database?

The problem we have, to some extent, is determining what goes wrong. It would be most unusual for your host not to allow you to change database structures. At the same time is it also not unheard of. I am just doubtful that this is the reason based simply on probability. But you could ask them.

Are you familiar with Firebug? If not what browser are you using for the upgrade attempts? And one last question 0 do you know how to check your php error log and if so is anything reported?

Hi again!
I’m using Firefox and firebug.

Could this be the issue here ?
request:
https://internt.dnb.no/labs/index.php?sp_ahah=upgrade&sfnonce=d24e3e99de&start=6401

resonse:

6624<SCRIPT language=”JavaScript”>
<!–
document.cookie = “IV_JCT=%2Flabs; path=/”;
//–>
</SCRIPT>

I know this javascript code in response have ruined things for us in the past on other plugins.
Is a webseal solution the server is located behind that ad this js-crap on every respons not ‘tagged’ as json

That’s a little above my pay-grade to be honest!

I understand basically what webseal is and more or less how it works but what effect it might have on the mechanics is an unknown to me and not something I can easily set up and test for.

i CAN tell you that the correct HTML response at this stage of the upgrade IS 6624 and hopefully that also received an http response of 200.

I would have thought that if it were not authenticating then it would have stopped earlier although – this IS pretty early. The upgrade is performed as a series of AJAX calls, each with a unique section number. The first is 6624 which seems to be reporting a success. The second section and AJAX call is 6637 which seems to be where your upgrade fails. Commands in this section are all ‘ALTER TABLE’ SQL statements.

is this all that comes up in the firebug console?

Hehe, I’m not excpecting you to know anything about webseal.
But if your only expect ‘6624’ as respons from your ajax call but recive 6624 plus some garbage from webseal. What happens then? Could this be the reason why u ‘stop upgrading’ ?

This is the only XHR call in my firebug and it get a 200 respons, the respons however is ‘polluted’ with a script tag.

Good question and yes i should have picked this up before – now I have looked at the code. We ONLY expect a numeric response. That is enough to abort the process.

So – can this be temporarily turned off or do we need to find a workaround?

Heyhey! At least we maybe know why this crash

Is there some place in your php code I could set responsheader as ‘type json’  ? Then webseal wil not alter the respons.

I can do some research although I can explain how it works and maybe you will get there before me!

We handle these requests using the jQuery .load() method which is technically AHAH not AJAX. The response is the section number in the upgrade script just processed which is inserted into a hidden element on the page and keeps track of where in the script we are up to. The script then loops to the next iteration sending the response number back as the next starting place in the script.

Without doing some research I can’t answer your question off the top of my head but I am going to start reading…

Hi again!

Located sp-upgrad.php and added this line on line 35

header(‘Content-type: application/json; charset=utf-8’);

Then the upgrade worked

Maybe a permanent ‘improvement suggestion’ for you guys?

Thank you for quick and helpful feedback (as always), I’m off to play with my new forum now

not sure its a general improvement despite that fact that it helped you…  but we will certainly look into it and see if any downside…  thanks for the info…