bug after updating, ProcessWire dev 3.0.116 -> 3.0.117

[slave]

I have a bug after updating ProcessWire dev 3.0.116 -> 3.0.117
Parse error: syntax error, 'unexpected' (T_NEW), expecting identifier (T_STRING) or variable (T_VARIABLE) or '{' or '$' in \ wire \ core \ WireArray.php on line 2480

public function __new($items = null) {
        $a = self::new ($items);
        $this->wire($a);
        return $a;
    }

I have this error now and can not log in anymore

[theo]

Which PHP version?

No problems here so far with PHP 7.2.11

[teppo]

If you pasted that code here as-is, the issue seems to be that there's an extra space after self::new – it should be "self::new($items)" and not "self::new ($items)".

A FileCompiler issue, perhaps? Could also try manually replacing /wire/core/WireArray.php with the one found from GitHub, just in case.

Ping @ryan ?

[slave]

5 hours ago, theo said:

Which PHP version?

No problems here so far with PHP 7.2.11

I have php 5.4.17
I'll try that with 7 now

[slave]

3 hours ago, teppo said:

If you pasted that code here as-is, the issue seems to be that there's an extra space after self::new – it should be "self::new($items)" and not "self::new ($items)".

A FileCompiler issue, perhaps? Could also try manually replacing /wire/core/WireArray.php with the one found from GitHub, just in case. 

Ping @ryan ?

I will try it
and report

[alexm]

I'm getting similar issue for this update:

PHP Parse error:  syntax error, unexpected 'new' (T_NEW) in /wire/core/WireArray.php on line 2480

PHP version: 7.2

Any thoughts? Tried replacing the WireArray.php file also I see no typo.

[alexm]

I'm not sure whether either of these modules conflicted or if it's coincidence , but I roled back and then updated FormBuilder to the latest version and likewise with ProCache and then dropped wire directory for latest release back in place and all working.

[gmclelland]

https://processwire.com/blog/posts/rebuilding-pw-website-part2/

Quote

It sounds like last week's version 3.0.117 additions to WireArray may have caused issues in PHP versions prior to 7.x. Sorry about that—it has been hopefully fixed on the dev branch.