Title: Problem after 2.0.66.17 update Last modified: August 22, 2016 --- # Problem after 2.0.66.17 update * [funkman733](https://wordpress.org/support/users/funkman733/) * (@funkman733) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/) * Hi to all, I have update nextgen to new version, but now I have some big problems: When I want to go to gallery setting and other options, the page remain blank, and in post edit page, when I click to nextgen icon, to administrate album, create album or upload foto, the popup window remain blank…. * What should I do? * [https://wordpress.org/plugins/nextgen-gallery/](https://wordpress.org/plugins/nextgen-gallery/) Viewing 12 replies - 1 through 12 (of 12 total) * [Erik Geurts](https://wordpress.org/support/users/erikgeurts/) * (@erikgeurts) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174569) * These are all caused by 500 Internal Server Error and therefore the page you see in the browser comes back as a blank. * There appears to be a coding error in the \products\photocrati_nextgen\modules\ nextgen_pagination\module.nextgen_pagination.php on line 31. * It looks like there is a whole chunk of code missing. I removed everything after line 30 for the time being and most of the sites we host now work again. * However, as a result, I also see errors in the Apache error log like: [Sat Aug 09 11:12:49 2014] [error] [client 94.212.64.xxx] PHP Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /var/www/virtual/www.domain.com/wp-content/ plugins/nextgen-gallery/products/photocrati_nextgen/modules/widget/module.widget. php on line 39 * I guess this is because module.widget.php is trying to reference the code that I removed from that other file. * [Erik Geurts](https://wordpress.org/support/users/erikgeurts/) * (@erikgeurts) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174573) * When I browse the code on SVN for [http://plugins.svn.wordpress.org/nextgen-gallery/tags/2.0.66.17/products/photocrati_nextgen/modules/nextgen_pagination/module.nextgen_pagination.php](http://plugins.svn.wordpress.org/nextgen-gallery/tags/2.0.66.17/products/photocrati_nextgen/modules/nextgen_pagination/module.nextgen_pagination.php) then it looks different from the file that’s included in the zipped downloadable v2.0.66.17 (I mean the one that is pushed when I auto-update from the WordPress admin UI). * Thread Starter [funkman733](https://wordpress.org/support/users/funkman733/) * (@funkman733) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174575) * The blank page, is not all blank, because I can see and click all wordpress menu… But now I see that the problems are only in my firefox windows, because if I try to enter with chorme windows or firefox android, it go fine. Now, I have another problem, when I go to select and save lightbox options it return me the 403 forbidden page….. why? * [Erik Geurts](https://wordpress.org/support/users/erikgeurts/) * (@erikgeurts) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174576) * I fixed my issue by downloading the latest stable from [http://downloads.wordpress.org/plugin/nextgen-gallery.latest-stable.zip](http://downloads.wordpress.org/plugin/nextgen-gallery.latest-stable.zip) and then uploading it over ftp. It seems that the auto-update process from within the WordPress admin UI either downloaded an incorrect zip file or made some other error while applying the update. * Thread Starter [funkman733](https://wordpress.org/support/users/funkman733/) * (@funkman733) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174584) * I have always 403 Forbidden page…… * [Erik Geurts](https://wordpress.org/support/users/erikgeurts/) * (@erikgeurts) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174592) * I do not know how to fix that, it may even be that we are talking about 2 completely unrelated issues. * [rogiermaas](https://wordpress.org/support/users/rogiermaas/) * (@rogiermaas) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174634) * Since the upgrade, my singlepics are all showing the very first image in my database. No matter what I do, I always see the same picture. Deleting this picture shows the next ‘first picture’. * What to do?! * – Rogier * [mforret](https://wordpress.org/support/users/mforret/) * (@mforret) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174648) * I have the same problem with singlepics, all singlepic shortcodes throughout the site show the first image in the database i.e. image id=1, regardless of the actual id number in the shortcode. * [rogiermaas](https://wordpress.org/support/users/rogiermaas/) * (@rogiermaas) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174650) * I have rolled back to 2.0.65 and things work again. I’ll wait for a version greater than 1.0.66.17 until this problem has been adressed. * I also have tried altering the sort order as suggested by others (amongst other things) but nothing seem to work for me. So I’ve installed an older version and all went well again. * As for the 403-error: check your rights, I’m sure that has nothing to do with the actual plugin.. * – Rogier * Plugin Contributor [photocrati](https://wordpress.org/support/users/photocrati/) * (@photocrati) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174665) * [@funkman733](https://wordpress.org/support/users/funkman733/) – A 403 forbidden error generally has me questioning if the permissions are correct for the installation. You might need to check with your web hosting service to see if that is the case. * [@erik](https://wordpress.org/support/users/erik/) Geurts – Thank you very much for your assistance. In some cases, we don’t know why, it does require a manual update to correct the issue. Your particular instance may be the second time we have heard of this specific file at that specific line number. * [@rogiermaas](https://wordpress.org/support/users/rogiermaas/) – Hello again! * [@mforret](https://wordpress.org/support/users/mforret/) – This is likely due to a recently found issue that has to do with the default sort order. Go under Gallery > Other Options > Image Options and set your default sort order to Ascending. This is a temporary work-around until we find the best solution to the issue you are seeing. If this does not correct it, please start a new topic. * Thanks! * – Cais. * [mforret](https://wordpress.org/support/users/mforret/) * (@mforret) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174669) * Thank you, changing the sort order worked. Look forward to the complete fix. * Plugin Contributor [photocrati](https://wordpress.org/support/users/photocrati/) * (@photocrati) * [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174685) * [@mforret](https://wordpress.org/support/users/mforret/) – I do not have an ETA, yet, but it is definitely high on our current to-do list. * Thanks for the update. * – Cais. Viewing 12 replies - 1 through 12 (of 12 total) The topic ‘Problem after 2.0.66.17 update’ is closed to new replies. * ![](https://ps.w.org/nextgen-gallery/assets/icon-256x256.png?rev=2083961) * [Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery](https://wordpress.org/plugins/nextgen-gallery/) * [Frequently Asked Questions](https://wordpress.org/plugins/nextgen-gallery/#faq) * [Support Threads](https://wordpress.org/support/plugin/nextgen-gallery/) * [Active Topics](https://wordpress.org/support/plugin/nextgen-gallery/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/nextgen-gallery/unresolved/) * [Reviews](https://wordpress.org/support/plugin/nextgen-gallery/reviews/) * 12 replies * 5 participants * Last reply from: [photocrati](https://wordpress.org/support/users/photocrati/) * Last activity: [12 years ago](https://wordpress.org/support/topic/problem-after-206617-update/#post-5174685) * Status: not resolved