We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
  • Both a fresh install of 2.2.3 and an upgrade to 2.2.3 fail on an Ubuntu server. Anyone else having problems with this release? I wanted to check here before filing a bug report.

    Sitting in the manager, minding my own business, I get an error that pops up:

    Unexpected token '<':
    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.
    Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
    More information about this error may be available in the server error log.
    Apache/2.2.17 (Ubuntu) Server at www.neotalogic.com Port 443


    The main thing I'm seeing is that I can't see the files under the files tab: the "Media" folder is there, but I can't open it. I also can't upload files. This was working on this same server with MODX 2.2.2.

    Some more goodies from the logs:

    PHP FPM's log:
    Jun 14 03:23:46.304157 [WARNING] [pool xxxxxxxxxxx] child 30975, script '/home/xxxxxxxxxxx/public_html/connectors/browser/directory.php' execution timed out (60.276877 sec), terminating
    Jun 14 03:23:46.307945 [WARNING] [pool xxxxxxxxxxx] child 30975 exited on signal 15 (SIGTERM) after 62.668815 seconds from start
    
    
    
    Slow Request log:
    Jun 14 03:23:46.158009 [pool xxxxxxxxxxx] pid 30975
    script_filename = /home/xxxxxxxxxxx/public_html/connectors/browser/directory.php
    [0x097a96c0] sanitizePath() /home/xxxxxxxxxxx/public_html/core/model/modx/modfilehandler.class.php:117
    [0x097a9028] sanitizePath() /home/xxxxxxxxxxx/public_html/core/model/modx/sources/modfilemediasource.class.php:43
    [0x097a7908] getBases() /home/xxxxxxxxxxx/public_html/core/model/modx/sources/modfilemediasource.class.php:96
    [0x097a762c] getContainerList() /home/xxxxxxxxxxx/public_html/core/model/modx/processors/browser/directory/getlist.class.php:51
    [0x097a730c] process() /home/xxxxxxxxxxx/public_html/core/model/modx/modprocessor.class.php:173
    [0x097a6998] run() /home/xxxxxxxxxxx/public_html/core/model/modx/modx.class.php:1586
    [0x097a5968] runProcessor() /home/xxxxxxxxxxx/public_html/core/model/modx/modconnectorresponse.class.php:131
    [0x097a5828] outputContent() /home/xxxxxxxxxxx/public_html/core/model/modx/modconnectorrequest.class.php:79
    [0x097a5614] prepareResponse() /home/xxxxxxxxxxx/public_html/core/model/modx/modconnectorrequest.class.php:66
    [0x097a551c] handleRequest() /home/xxxxxxxxxxx/public_html/connectors/browser/directory.php:3


    Anyone have any ideas?
      • 28215
      • 4,149 Posts
      A recently discovered issue due to an integrated pull request that missed better checking. A reversion is here:
      https://github.com/modxcms/revolution/commit/975675e604da58da8db011dd4ffb9ddf2a77ad39

      That will fix the issue.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com