Benjamin

Hi LovePS,

NextGen uses a handful of custom posts to store settings. Since the 2.0 release we introduced a few new ideas beyond plain albums and galleries. Since we organize our plugin to be as modular as possible we split up the methods for generating a thumbnail gallery from an imagebrowser gallery, so our “basic thumbnails” is one “Display type” and the “basic imagebrowser” another. Each display type is its own module and has its own code for handling display, settings, etc. Each display type will create its own custom post to store the global settings you see in the “Gallery Settings” page.

A “displayed gallery” is created by our “Attach To Post” window and is the equivalent of a serialized shortcode. It contains all the settings that display needs like which galleries it comes from (a “displayed gallery” can show images from multiple “galleries”, thus the distinction).

The “displayed gallery source” post is again used to store some internal settings. NextGen 2 has several ‘sources’ — galleries, albums, ‘recent’ images, ‘random’ images, and tags. A basic thumbnail displayed gallery could display all images tagged a certain way, but albums can only use albums as their source of content.

If you want to monitor when Attach-To-Post galleries are created you would want to inspect the “displayed gallery” type posts. If you’d like to monitor when any new displayed gallery is rendered you can use the “ngg_displayed_gallery_rendering” filter which provides the rendered HTML as well as the displayed-gallery object.

Let me know if you have any more questions! NextGen has several actions & filters to use, if you can be more specific about what you want to achieve I can help with what method may work best.

This shouldn’t be a problem with NextGen 2.1 anymore as we load the ATP iframe via admin_url() which should play nicely with WordPress-HTTPS. If this is still an issue please let me know-I could add a filter to WordPress-HTTPS’ ‘force_ssl’ to make our ATP preview always be HTTPS.

You can use WordPress’ method do_shortcode() to return the results of a shortcode, thus in PHP you could do: $galleryHTML = do_shortcode("[ngg_images source='tags' container_ids='motorrad' display_type='photocrati-nextgen_basic_thumbnails']");

Hi markwebstar,

You’ll want to create a new directory in your active theme directory and name it “nggallery”. Place the following code in a file called singlepic-title-below.php in that directory:

<?php if (!defined ('ABSPATH')) die ('No direct access allowed'); ?><?php if (!empty($image)) { ?>
    <a href="<?php echo nextgen_esc_url($image->imageURL); ?>"
       title="<?php echo esc_attr($image->linktitle); ?>"
       <?php if(!empty($target)) { ?>target="<?php echo esc_attr($target); ?>"<?php } ?>
        <?php echo $image->thumbcode; ?>>
        <img class="<?php echo $image->classname; ?>"
             src="<?php echo nextgen_esc_url($image->thumbnailURL); ?>"
             alt="<?php echo esc_attr($image->alttext); ?>"
             title="<?php echo esc_attr($image->alttext); ?>"/>
    </a>
    <?php if (!empty($image->description)) echo esc_html($image->description); ?>
    <?php if (!empty($image->caption)) { ?><span><?php echo $image->caption; ?></span><?php } ?>
<?php } ?>

You may need to wrap the echo of the $image->description attribute in a span, div, p, etc as necessary.

Unfortunately we don’t currently support this well at all, but I think it’s a great feature request with only a little effort. I’ve checked in a new filter, ngg_datamapper_table_name, that will allow users to choose which table is read from. It should be in the next release.

__EC__TEST__ is created by a JS library we use (“EasyCookie”) that creates the cookie with a content of Date.toGMTString() and deletes it to determine if the library has read / delete access and can thus function. It doesn’t store any other information.

Hi appugappu,

Unfortunately this has been built into NextGen for some time and we don’t have an easy way to disable it. The best solution I can think of to prevent an image from being created that may conflict would be to add a filter to “sanitize_file_name” and use it to search the gallery directories for the $filename parameter used in the filter. I would add this as an option but at the moment we’re in a feature freeze until we release our next update; we do take feature requests though.

If you’re willing to edit the nextgen-gallery plugin I would point you towards package.module.nextgen_data.php’s upload_base64_image() method; just look for the if(!ini_get('safe_mode') && @file_exists($abs_filename).. line.

Sorry I can’t help any more.

No, it isn’t currently possible with our latest beta (2.0.92), but it is definitely already a goal for the next major release.