jondho

Thanks for the reply and yes, fully understand that any changes need to be generic across other platforms. I haven’t looked in detail at the other platforms, although if they did each have various pieces of “extra” data (e.g. for flickr, geolocation and datetaken would be super useful), then perhaps these could be put in a generic “data-extra” html attribute (perhaps just as a comma or semicolon separated list… or even as json). Different platforms might return different pieces of “extra” data (or none) but would all return the content to the same data-extra attribute. This could mean that the mess gets kept at the level of the platform modules and higher up aspects like layouts etc just have to handle an extra attribute.

If this was possible, then this would negate the need for a raw output because this data could be accessed for various purposes either from PHP (by parsing the DOM response returned when calling the shortcode via do_shortcode) or form JavaScript.

For reference, what I am working on is only a private project and I will be integrating the use of your plugin with Toolset (https://toolset.com/) to dynamically construct galleries related to other data. As it is a private project, a bit of dirty hacking is fine and this is most likely an edge case in terms of functionality so I fully understand that.

A final point is that searching by date and having the date returned with the photo all the way to the gallery would also be useful (as a standalone and probably (?) simpler comment from above).

Best regards,
Jonathan.

As a really blunt approach (and what I have implemented as a temporary workaround) is to add:

if ($short_code['view'] == 'raw') {
  return $photos;
}

I have also added ‘geo’ to $flickr_params['extras'] and $flickr_params['primary_photo_extras'] (lines 123 & 124).

inside the process_photos function in Flickr.php (line 607) and then just use a shortcode with view=’raw’. This could also go higher up in the switch statement of course.

This has the effect of returning the full $photos object and means that I can call the shortcode (using do_shortcode) from another piece of php.

This is obviously is not a proper solution and results in various unintended issues, but it does deliver the initial functionality that I am after.

The API key has authenticated successfully and the pro functionality appears to be there. I will Put a support request in via your website and can provide some screenshots, etc.

I am also getting a JS error client side from https://static.xx.fbcdn.net/rsrc.php/v3/yj/r/cBY_yab8wOO.js

I am running this on an internal development server which is not accessible from outside world. Not sure if this is affecting it.

Haven’t tested it yet because we ended up using a workaround by forcing Sucuri to only use alphanumeric characters for passwords, but thanks for the solution.