Skip to content
A Social Media Aggregator for WordPress
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


A Social Media Aggregator for WordPress


Once installed, go to Settings > Discussion, and scroll down until you get to the Taggregator Social Media Aggregator section. You will see a number of options:

  • Actively Scraping? Whether the cron job that runs is actively trying to access the servers in question.
  • Tag What tag you'd like to search for. Please keep it to one word, and precede it with a hashtag.
  • Twitter Consumer Key (maybe) The Consumer Key for your Twitter Application. Twitter's v1.1 API requires an application to connect and query.
  • Twitter Consumer Secret (maybe) The Consumer Secret for your Twitter Application.
  • Instagram Access Token (maybe) The Access Token for your Instagram Application. Instagram requires an application to query its API for media tag items. Once you create one, you can find your authentication token through their developer panel. You don't need their application keys, just an authentication token.

The latter three options will only display if they've not been globally defined in constant form by a network administrator.


If Actively Scraping? is selected, then it will attempt to use the credentials provided to scrape the respective services at a given interval (currently 1 hour) via wp_cron.

To trigger a scrape manually, have a site administrator append the taggregator_cron_active GET argument to any admin page, like so:

Please note, however, that this method will be going away soon. It is merely for testing purposes at the moment. It will be replaced with a button somewhere in the admin to do the same task via ajaxy goodness.


You can output the content on any post or page using the [taggregator] shortcode. It defaults to the most recent 30 items, but can do any number by specifying it as such: [taggregator qty="50"]

Future display methods are forthcoming, as well as loading new items in via ajaxy goodness.

Something went wrong with that request. Please try again.