Parse error in 3.0 (wrong comma) | ww.wp.xz.cn

Resolved Anonymous User 17880307
(@anonymized-17880307)

5 years, 6 months ago
It seems there is a small bug in 3.0 that causes a parse error due to a comma. See the screenshots:

https://user-images.githubusercontent.com/827205/98219766-bedc8d00-1f4d-11eb-9359-38fdf36dbf9a.png

https://user-images.githubusercontent.com/827205/98219993-ff3c0b00-1f4d-11eb-881d-87bfcbf25e66.png

https://user-images.githubusercontent.com/827205/98219768-bf752380-1f4d-11eb-98fb-d13ff0c607c7.png
- This topic was modified 5 years, 6 months ago by Anonymous User 17880307.

Viewing 4 replies - 1 through 4 (of 4 total)

Plugin Author nintechnet
(@nintechnet)

5 years, 6 months ago

Thanks for reporting the issue.
I just released 3.0.1

Which PHP version are you running?
Thread Starter Anonymous User 17880307
(@anonymized-17880307)

5 years, 6 months ago
Many thanks for the fast reaction.
According to the RFC https://wiki.php.net/rfc/trailing-comma-function-calls and https://3v4l.org/Wm1YP the issue affected PHP < 7.3 as support for trailing comma in function calls was implemented in PHP 7.3.
- This reply was modified 5 years, 6 months ago by Anonymous User 17880307.
- This reply was modified 5 years, 6 months ago by Anonymous User 17880307.
Plugin Author nintechnet
(@nintechnet)

5 years, 6 months ago

Yep, that affects <7.3, see this thread too: https://ww.wp.xz.cn/support/topic/ninja-scanner-3-broken-update/#post-13624013

Actually we spent a lot of time to test it on 7.3, 7.4 and even 8.0 but we didn’t check well enough on 7.2 and below

Thread Starter Anonymous User 17880307
(@anonymized-17880307)

5 years, 6 months ago

Marking as resolved.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Parse error in 3.0 (wrong comma)’ is closed to new replies.

4 replies
2 participants
Last reply from: Anonymous User 17880307
Last activity: 5 years, 6 months ago
Status: resolved