The first one we just need to remove the lines of code that reference get_magic_quotes_gpc().... at the top of the file easy peasy like so:

       /* DEPRECATED
        if ( get_magic_quotes_gpc() )
        {
            $_GET = $this->stripSlashesRecursive($_GET);
            $_POST = $this->stripSlashesRecursive($_POST);
        }
        */

==========================

the second one  deals with setting a priority for execution when using long php ternary commands...  so in this case (if i am correct) we just have to sort this out. The objective is to use parenthesese to let the server know what we want to execute first and so on..

So in this case:

Original code:

 $status = empty($actionData['data']['status'])
            ? $actionData['string']
            : empty($actionData['data']['status']) ? null : $actionData['data']['status'];

New code (untested)

$status = (empty($actionData['data']['status'])
            ? $actionData['string']
            : empty($actionData['data']['status'])) ? null : $actionData['data']['status'];

So we want to execute this part first - here is a breakdown

(empty($actionData['data']['status']) ? $actionData['string'] : empty($actionData['data']['status']))

notice i added the parenthesese in the first and last position

then we can execute the rest of the long ternary

? null : $actionData['data']['status'];

=======================

And the last one has to do with using {} to pull individual characters from a string in the jevix class.  You can no longer use {}, you have to change them to []

for example: 

original code

return ($h & 0x0F) << 18 | (ord($c{1}) & 0x3F) << 12 | (ord($c{2}) & 0x3F) << 6 | (ord($c{3}) & 0x3F);

we would just replace {number} with [number] like so

new code

return ($h & 0x0F) << 18 | (ord($c[1]) & 0x3F) << 12 | (ord($c[2]) & 0x3F) << 6 | (ord($c[3]) & 0x3F);

patricia, SD, artmedia,  does this look about right, i think i got it...

Here is another concern, jevix is no longer being developed (youll have to translate the site to read it)

https://code.google.com/archive/p/jevix/

so there is no update for it.  So it would have to be edited and if we are lucky it will work. Or we may have to find a new html filter script to use.

The first two corrections are tested and seem to work fine. The last one i am still working on.

here is the jevix changed code... it did not blow up on me so thats good... :) 

its the last function in the file

function uniord( $c )
{
    $h = ord($c[0]);
   
    if ( $h <= 0x7F )
    {
        return $h;
    }
    else if ( $h < 0xC2 )
    {
        return false;
    }
    else if ( $h <= 0xDF )
    {
        return ($h & 0x1F) << 6 | (ord($c[1]) & 0x3F);
    }
    else if ( $h <= 0xEF )
    {
        return ($h & 0x0F) << 12 | (ord($c[1]) & 0x3F) << 6 | (ord($c[2]) & 0x3F);
    }
    else if ( $h <= 0xF4 )
    {
        return ($h & 0x0F) << 18 | (ord($c[1]) & 0x3F) << 12 | (ord($c[2]) & 0x3F) << 6 | (ord($c[3]) & 0x3F);
    }
    else
    {
        return false;
    }
}

If i for example add a android app i need follow googles new standard if not they will reject my app. And they standard changes every year.

I not sure what rules you have about php and plugins that they submit to store year 2020 where we have now php 7.4 available ?

If there is no rules theer should bee, it is like developers working with old languages and that is not good at all.

Like a refuse speak new words because i learned old words already and not need learn new words. It is a school thing. Tell you student learn new words and you need bee hard teach you student new words if not they will give you old language and old words back

For me you are the teacher and they need follow the teacher or have the projects rejected to they pass school teachers test

anyways...you the boss ...keep the old 5.6 forever to it sinks to bottom...im out from the discussion you would not agree with me even payed you 10000000000000 usd ....so fine do what you want....i will ask developers who created the plugin if they support php version 7.4 if not i will not buy 

i take action on my own and recommend others do that to...support future ...i will never again buy a plugin that support only php 5.6 ....hope other will follow me so things will bee better

wow you are so aggressive for no reason.  All i said is that when oxwall is updated we can then require more current versions for the plugins as well.   I did not shoot down your idea, we just have to wait. 

 Drift Boss