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

also i've found data in the module in the DB, my module settings

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

Hello,

thanks for the Module.

is it possible to add also feed by hashtag ?

Thanks

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...