WordPress.org

1. uiqo
   Member
   Posted 2 years ago #

   All 701 galleries containing a total of 9118 images no longer display in my posts using the standard [gallery=galleryname] call. Was working just fine prior to upgrading to 1.4.1.

   Please advise.

   http://wordpress.org/extend/plugins/nextgen-gallery/

2. uiqo
   Member
   Posted 2 years ago #

   Just to add. I can see the galleries fine via WP-ADMIN/GALLERY. The galleries are no longer displaying in all my posts.

   Example:

   http://www.uiqo.com/2009/09/15/batman-arkham-asylum-pc-screenshots-2/

3. uiqo
   Member
   Posted 2 years ago #

   More info for you.

   If I use (for example) [gallery=721] then it displays fine. Previously however I was using [gallery=batman_screenshots] but calling the actual gallery name is no longer working.

   Is this a bug or am I required to edit 701 posts and change the call from gallery name to gallery ID?

4. uiqo
   Member
   Posted 2 years ago #

   Sorry to spam my own thread. Hopefully this info will be helpful.

   Downgraded to NG Gallery 1.3.6. Run NG Gallery 'database upgrade script' and galleries can now be called by name.

   Upgraded again to NG Gallery 1.4.1. Run NG Gallery 'database upgrade script' and galleries can no longer be called by name. They must be called by gallery ID.

   Downgraded once again to 1.3.6. Run NG Gallery 'database upgrade script' and once again galleries can be called by name. Since I have 701 galleries, I'll stick with 1.3.6 for now until 1.4.1 or greater supports to calling of gallery names.

5. moodyjive
   Member
   Posted 2 years ago #

   I'm having the same problem. I'm wondering if it's a Php 5 issue as I am running WP on Yahoo and they use PHP 4.

6. rovo89
   Member
   Posted 2 years ago #

   I just experienced the same problem... the problem is the line
   $galleryID = (int) $galleryID;
   in the function nggShowGallery (nggfunctions.php). If you remove this line, gallery names will work again. However, I'm not exactly sure whether there are any side-effects.

   According to this ticket, this is a wanted behaviour. The developer of the plugin writes that "this is a older shortcode which is no longer supported".

Topic Closed

This topic has been closed to new replies.