• Resolved chris

    (@achensee)


    Parse error: syntax error, unexpected end of file in /www/…/html/wp-content/plugins/mp-timetable/classes/blocks/class-timetable-block.php on line 188

    There was no conflict with previous version.

    WP5.1.1
    PHP7

    • This topic was modified 5 years, 11 months ago by chris.
    • This topic was modified 5 years, 11 months ago by chris.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor motopress

    (@motopress)

    Hi @achensee,
    TimeTable plugin has been tested on server with PHP 7.3.2 version and no errors have been detected. Could you try re-installing plugin once again?

    Thread Starter chris

    (@achensee)

    Hi MP, deinstalling/reinstalling didn’t help.
    I also testet the plugin on a blank wp install wp5.1.1 with all other plugins disabled: the same error!

    Server is PHP Version 7.1.27-1+ubuntu16.04.1+deb.sury.org+1

    • This reply was modified 5 years, 11 months ago by chris.

    Hello @motopress ,

    I have same issue here, everything was fine on PHP 7.0 and then I had same error after upgraded to PHP 7.3.1

    Hello @motopress same error here.

    @motopress @achensee OK Found it.

    Please replace line 183 ?></div><? by ?></div><?php

    By default, php 7 does not support short_open_tag.

    • This reply was modified 5 years, 11 months ago by franchez.
    • This reply was modified 5 years, 11 months ago by franchez.
    Thread Starter chris

    (@achensee)

    @franchez genius, that’s it!

    Same error.

    Disabled it renaming the plugin folder.

    Then when trying to renable the plugin, this errors shows up:

    Parse error: syntax error, unexpected end of file in /site/wp-content/plugins/mp-timetable/classes/blocks/class-timetable-block.php on line 191

    The edit pointed out by @franchez worked flawlessly.
    Thanks!

    Am definitely receiving this 500 Error as well. Please push through another update as soon as possible.

    Plugin Contributor motopress

    (@motopress)

    The issue has been fixed in version 2.3.1. Please try to update the plugin.

    We are sorry for inconveniences.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Upgrade to Version 2.3.0 causes Error 500’ is closed to new replies.