Support » Plugin: Shortcodes Ultimate » “images not found” error when gallery source is from taxonomy

  • cicopitalia

    (@cicopitalia)


    Usually I provide ids as source for image gallery and everything works, but when I discovered that also taxonomy can be used as source I understood that I could save a lot of time. So through “Enhanced Media Library” plugin I created some categories of taxonomy type “Categorie Media” (default type), and I created a “su_custom_gallery” having as shortcode “[su_custom_gallery source=”taxonomy: media_category/170″ limit=”-1″ link=”lightbox” width=”180″ height=”180″][/su_custom_gallery]” (where “170” is related to the taxonomy type I selected), but with my great sorrow and “images not found” error was displayd in place of the gallery.
    How can this problem be solved?
    Thanks in advance.

    • This topic was modified 2 months ago by  cicopitalia.
    • This topic was modified 2 months ago by  cicopitalia.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • cicopitalia

    (@cicopitalia)

    Follow up

    Errata corrige: “170” is related to category term

    I managed to retrieve programmatically a comma separated list of image ids (like “1244,1242,1241,1240,1239,1238,”) using the following snippet:

        $args = array(
            'post_type' => 'attachment',
            'post_status' => 'any',
            'post_mime_type' => array( 'image/jpeg','image/gif','image/png','image/bmp','image/tiff','image/x-icon' ),
            'posts_per_page' => -1,
            'tax_query' => array(
                array(
                    'taxonomy' => "media_category",
                    'field' => 'slug',
                    'terms' => array("term1","term2")
                )
            )
        );
        $query_images = new WP_Query($args);
        $id_list = "";
        foreach ($query_images->posts as $image) {
            $id_list .= (($image->ID) . ",");
        }

    So it means that database and input arguments are correct. I also had a look at the code but is not easy to find the problem without debugging tools.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.