Jump to content
justb3a

Module: Instagram Feed

Recommended Posts

Represents the instagram feed of a user.

Instructions:

  1. Register a new instagram Client: at instagram. It's really important to add the current url as redirect url. (For example "http://page.dev/processwire/module/edit?name=InstagramFeed/").
  2. Complete module settings (Client ID and Secret), leaving the access input token field empty. This value will be generated.
  3. Click the "get Access Token" link to generate code and access token in module settings.
  4. Configure username to output feed from (default setting is "self":  to get the most recent media published by the owner of the access token)
  5. ... and use it!

detailed instructions at github

  • Like 14
  • Thanks 1

Share this post


Link to post
Share on other sites

Hey this looks great! I have one recommendation that you might want to consider, I didn't see anything that caches the json array that you get back. I had an issue with a site a while back where periodically due to the server having to make a round trip to the instagram api every load the rest of the page would hang a bit. Not really an issue if you are using something like procache, but maybe a cache option might be a good idea for a configurable option . Just a thought. :)

  • Like 1

Share this post


Link to post
Share on other sites

@MuchDev: Thanks, this is really a good hint.  Do you have any suggestions how best to tackle this issue?  ;)

Share this post


Link to post
Share on other sites

I used an article on stack overflow, I think it was this post: 

http://stackoverflow.com/questions/20558078/caching-instagram-api-requests-using-php

I don't think I had to do too much. I didn't end up using markup cache as you could I just cached the file to a static directory in my cache folder. You can see in the script where you could parameterize your settings in. Good luck . :)

Share this post


Link to post
Share on other sites

Yeah good point there is that too. I think why I used that was in debugging, having direct access to the file made it easier to just delete it and have it re-cache, also I got to play around with some bare metal php.

Share this post


Link to post
Share on other sites

My first site with PW has an Instagram feed coded in the most horrible way haha, just like, plugged in from everywhere because I didn´t understand much of PW modules (I think I still don´t haha).

I did resolve the caching issue just by saving the response in a file (though using file_put_content and stuff like that, no fancy PW functionalities, not even saving it inside the cache folder!!) , and also managed to make an ajax call to keep calling more images with the pagination API (that would be really nice to have in the module also!). With each new call, I updated the cache file list of image data and substituted the next pagination id.

Some of my doubs is if suddenly a big cache file could turn troublesome and also I don´t really get how you could call a module function from an AJAX call, like, do you use an URL?

Anyway, thanks for this nice module!

Share this post


Link to post
Share on other sites

Thanks for all your input! I decided to use the built-in WireCache functionality.

v0.0.2

(module settings)

Cache Expire: By default a cache lasts for one day but you can select another lifetime:

  • ... hourly, daily, weekly, monthly
  • ... never, to prevent expiration
  • ... save, to expire when any page or template is saved
  • by clicking the link below all module caches will be deleted
 
  • Like 4

Share this post


Link to post
Share on other sites

THANKS!

Tried it and seem to be getting strange results, sometimes the images appear and sometimes not - bottom of this page: http://www.benbyford.com/about/

Is there a problem with Instagram connection or caching or something?

<?php
    $feed = $modules->get('InstagramFeed')->getRecentMedia();
    foreach ($feed as $image): ?>
        <a href="<?=$image['link']; ?>" class="instagram-item">
            <img src="<?=$image['images']['thumbnail']['url']; ?>" alt="">
        </a>
        <div class="hidden">
        </div>
    <?php endforeach; ?>

Share this post


Link to post
Share on other sites

@benbyf: which ProcessWire version are you using? What’s your cache setting in module settings? What happens if you disable caching (set it to “now”). If caching is enabled, have a look at your database table caches. There should be an entry named module.instagramfeed-recentmedia. Is the depending “data” field filled? There should be json including your requested images.

Share this post


Link to post
Share on other sites

it's strange as it worked then didnt.

no template cache, module cache set to "never" (couldnt see "now" as an option)

Share this post


Link to post
Share on other sites

Which ProcessWire version are you using? Have a look at your database table caches. There should be an entry named module.instagramfeed-recentmedia. Is the depending “data” field filled? There should be json including your requested images.

Have a look at the ProcessWire error log, if something went wrong while authentification / receiving access token there should be an entry. 

In your instagram client settings, did you activate "Enforce signed requests" (this checkbox must be unchecked!). 

In module settings is there an access token?

Clear the cache for this module in module settings.

Make sure you have the username spelled correctly or leave it empty (default: self).

I receive your media without any problem:

post-2759-0-34846100-1444628970_thumb.pn

Share this post


Link to post
Share on other sites

I added this endpoint, could you please pull develop branch and test it? 

Get a list of recently tagged media
  • getRecentMediaByTag($tagname)
<?php $feed = $modules->get('InstagramFeed')->getRecentMediaByTag('processwire'); ?>

post-2759-0-58186600-1449818035_thumb.pn

  • Like 2

Share this post


Link to post
Share on other sites

Wow that was fast :) 

For the first time it works currently for me  :frantics: 

Thank you. 

I will test it out on the weekend

Share this post


Link to post
Share on other sites

whats the intagram strategy, its like they're locking it down more and more with the new approval process and new sandbox mode. https://www.instagram.com/developer/sandbox/

also do you create one client, or multiple clients - new one for each site? If multiple its almost impossible to do as each time you have to setup, submit to approve with instagram (including a step that asks you to submit a video of how your using instagram...) and wait.

:( boo instagram boo!

Share this post


Link to post
Share on other sites

Hello, 

is it possible to set more than one hashtag and set limit for the page ?  My idea is to inegrate it in a blog. and only e.G. 4 last pics with hashtags should be visible on the current post.

maybe something like

<?php $feed = $modules->get('InstagramFeed')->getRecentMediaByTag('processwire, cms'); ?> 

Thanks  

Share this post


Link to post
Share on other sites

@iNoize: I cannot find an instagram api endpoint which supports more than one tag. If you're not able to get your request fullfilled by using the official instagram app or website, it won't work in most cases.

Share this post


Link to post
Share on other sites

whats the intagram strategy, its like they're locking it down more and more with the new approval process and new sandbox mode. https://www.instagram.com/developer/sandbox/

also do you create one client, or multiple clients - new one for each site? If multiple its almost impossible to do as each time you have to setup, submit to approve with instagram (including a step that asks you to submit a video of how your using instagram...) and wait.

:( boo instagram boo!

this still the case or am i missing something?

Share this post


Link to post
Share on other sites

this still the case or am i missing something?

I have to say that I personally don't use instagram. I just created an account to develop this module which I needed for a client project.  :P

Share this post


Link to post
Share on other sites

First of all, great plugin!

Two questions:

— Is there a way to update the cache every 60 seconds?

— Is it possible to access the "high_resolution" endpoints, even though they aren't already implemented in instagram API (files are there but not implemented)?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
×
×
  • Create New...