so what does your debug.log say on that site ?

>Could this caused it?
that’s the wrong way to look at it as it happens.

Your change of postcodes actually fixed the error of the way the json is generated
(without actual access to your setup it’s admittedly just an educated guess though but I’m 99% sure)

>Hmmm the Jason file could be Created by the Winorder WPpizza Plugin.
That’s very much likely and the problem is that it’s wrong the way it is generated and not accounting for / ignoring indexes

>So the WInOrder Ssupport says it must be something server side
If my suspicions are correct than “Yes” in so far that it’s server side, but it’s still their issue

In other words. Your update /change of the postcodes fixed the symptoms but not the cause and it will happen again unless the json generated accounts for indexes correctly

and – out of curiosity – did the available options change ? (i.e the list of postcodes selectable )

furthermore , your first json has “value”: “5”,
not only is there generally no corresponding index in options , there is also no corresponding option with an index of 5 in your second json data (but that could be because it’s from a different system /site . I cannot know)

in other words, the ‘value’ must be present in the ‘options'(index)

the 405 is fine here – it’s just old documentation that has been amended over the years as paypal changed their integrations.
Note to self: I need to update this sooner rather than later to avoid further confusions

(the 405 relates to the fact nothing is being posted to this url when you go there directly in your browser, whereas an ipn response will – and must have – post data)

I’ll see if I can make this more elegant too if one simply wants to see if this script is working without actually sending any data.

At the end of the day what really counts is this:
Set the mode in the paypal plugin to test and make a test. if it works it’s all good , if not check the debug.log
If it works in test , it will work in live (as it’s the same) provided you are using the right credentials – i.e email address and/or REST credentials

>…. what happened to these
They are not needed as now globally implemented for all gateways and basically automatic

A few observations.
a) the debug log you sent me has none of these warnings you are referring to above in it
b) it does however have several hundred entries per day of PHP Warning: session_start(): Cannot start session when headers already sent in . PLease refer to https://docs.wp-pizza.com/troubleshooting/?section=headers-already-sent.
That said, I also believe this is more of the symptom than the cause
c) when trying to to verify the order at paypal, paypal respondes with a 403 error – i.e access forbidden (again, I think this is also only a symptom , not the cause)

What is definitely a problem – which may or may not be the root cause for everything but certainly one of it – is that you are caching you order page. Or more accurately, you are putting the checkout (widget) onto your article pages which are cached.
You must not cache any pages that have the checkout ‘widget’ on them or take steps to work around this (see also https://docs.wp-pizza.com/getting-started/?section=setup)
This is definitely something that needs fixing first. Once you have done that, see if you still have issues and report back

most (if not all) of these are symptoms not the cause.
if “ordervars” does not exist there is something severely wrong elsewhere
so , yet again, I need the (full) debug log
Your “suggested fix” would cause more harm than good

> for the past 5 days with several customers
As nothing has changed for month in the wppizza plugin and indeed the paypal one, the first question really would be what it is that changed your end about 5 days ago ?

that aside, have you enabled debug (https://docs.wp-pizza.com/troubleshooting/) and checked your debug.log ?

Are all of your other plugins/themes up to date ?

First of all, although possible, I would suggest you do not make any changes to those files directly anyway. If you do that , you will have to apply your changes every time there is an update.
See here: https://docs.wp-pizza.com/advanced/?section=modify-css-styles-layout

Secondly, it sounds more like you have a permission issue of some sort. WPPizza does not handle anything that would allow you – or disallow you – to edit its files. This would be server side or some “security” plugin or some other wordpress constant perhaps that is blocking yo from saving
In other words, this has nothing to do with wppizza and I cannot help you there I’m afraid .