Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Will do, thx.

    Ah, thank you.
    Would be nice to have some indication of that.
    But I could imagine that would help spammers as well ^^

    I encountered the error in album.php too. Curiously simply doing


    did not cause a problem, but doing print_r($gid) in xdebug causes the segfault.
    Ubuntu 16.04 LTS does not provide PHP 7.1 by default, so I want to fix the problem in the nextgen plugin. The above use of parse_str is highly discouraged anyway (though I think this instance is not a security issue).

    Could you please apply the following patch, so the next update wont overwrite my changes:

    --- WordPress/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/admin/album.php	2017-05-04 09:37:02.000000000 +0100
    +++ Plugins/nextgen-gallery/products/photocrati_nextgen/modules/ngglegacy/admin/album.php	2017-06-08 18:58:14.000000000 +0100
    @@ -191,10 +191,10 @@
     			$album = $this->_get_album($this->currentID);
     			// Get the list of galleries/sub-albums to be added to this album
    -			parse_str($_REQUEST['sortorder']);
    +			parse_str($_REQUEST['sortorder'], $sortorder);
     			// Set the new sortorder
    -			$album->sortorder = $gid;
    +			$album->sortorder = $sortorder['gid'];
     			// Ensure that a preview pic has been sent

    Thank you

    • This reply was modified 2 years, 8 months ago by bodo.
    • This reply was modified 2 years, 8 months ago by bodo.

    Hi ftorresibesz,
    dear Calvin.

    I encountered the same problem.
    After upgrading from php 5 to php 7, the default ubuntu install did not contain the mbstring extension anymore.
    So that was when the plugin started displaying the corresponding error message.

    I thought fixing the issue should be easy enough:

    aptitude install php-mbstring
    phpenmod mbstring
    service apache2 reload

    and indeed this installed and enabled the mbstring extension.
    Nevertheless the error message was still there.

    I could of course manually hide it with the accompanying button,
    but I don’t want to do that for every blog on this server.
    Furthermore when the mbstring extension gets deactivated again,
    the message would remain hidden.

    Unfortunately the only thing I could discern from your source code,
    was that the message is generated in lib/environment/check.php and
    is related to the ai1ec_mbstring_notification option.

    Please let the message disappear automatically, in case you detect the mbstring extension.

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