@jmaurin – Can you describe the process you are using to add album(s) into another album?
Thanks!
– Cais.
I’ve created 3 albums, called “Teste Root”, “Teste level 1” and “Teste final”.
In “Manage Albums”, I’ve selected “Teste Root” and tried to drag/drop “Teste level 1” to first column (Album ID 3: Teste Root). Then, click on “Update” and got this error: ERR_EMPTY_RESPONSE and blank page.
@jmaurin – Do these albums have galleries which in turn have images in them?
– Cais.
Yes, sometimes does. Actually, I think it’s an apache_itk error…..because I can change one time and next, got error (always). After apache restart, I can change one more time only, and so on…..
@jmaurin – Thanks for the update. Also, please remember, only use galleries that have images in them (and subsequently only use albums that contain galleries that have images in them).
– Cais.
I have encountered this error as well on one site.
As much as I have debugged this, it seams that the error gets triggered by bug in PHP which is reported to be fixed in PHP 7.1 only.
It seams that it gets triggered in file (NextGEN Gallery Version: 2.1.50) nextgen-gallery\products\photocrati_nextgen\modules\ngglegacy\admin\album.php.
Line 194:
parse_str($_REQUEST[‘sortorder’]);
Here is the PHP bug:
https://bugs.php.net/bug.php?id=73181
And here it says it’s fixed in 7.1
https://secure.php.net/ChangeLog-7.php#7.1.0
Not sure why it is not getting trigger every time because indeed album updates work well for few times and then then the error appears on third or second update (mostly).
We’re trying to upgrade server to PHP 7.1 to see if it solves the problem.
PHP 5.x seams to not be affected by this.
@armandsdz – Thanks for sharing these details … if the issue still persists after you update please start a new topic so we can look specifically at your environment.
– Cais.
Hi,
Any reports of success importing a 4IMAGES gallery
https://www.4homepages.de/
into wordpress, specifically NextGEN gallery?
Looks like there is something of a path to treat images as products and import to woocommerce but this would be still really be a chore.
Thanks,
Brian
@bigwavemaui – Please start your own topic so we can try to help you with your specific issue on your specific site.
See https://make.wordpress.org/support/handbook/forum-welcome/#post-in-the-best-place
Thanks!
– Cais.
I encountered the error in album.php too. Curiously simply doing
parse_str('gid[]=18');
print_r($gid);
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
$this->_set_album_preview_pic($album);
Thank you
-
This reply was modified 7 years, 8 months ago by
bodo.
-
This reply was modified 7 years, 8 months ago by
bodo.
Plugin Contributor
Imagely
(@imagely)
@canaaerus – If you are looking to submit a patch, please do so as a PR at our development repository here: https://bitbucket.org/photocrati/nextgen-gallery
Thanks!
– Cais.
Hi,
I found the same issue in the products/photocrati_nextgen/modules/ngglegacy/admin/album.php (row 194) independed from this post. Could you please add the above fix there?
I checked it with 7.0.20 (dotdeb) and PHP 7.1.6-2 from debian testing branch with the same result, so a fix in your code make sense the the moment.
Since I am using git, could @canaaerus add a pr there?