Possible to preview Instagram images in Explorer?

[craigfahner]

Hi,

I notice that in some of the documentation of the explorer feature, images are rendered – this is the case for Twitter datasets, for instance. When using the explorer on Instagram data, images are rendered as a grey square that reads "go to media". When clicked, another instance of the same explorer page is opened in a new tab.

Is there a way to display the scraped images in the explorer view for Instagram datasets?

[sal-uva]

Hi @craigfahner, thanks for the question.

• The URL link bug is already fixed. You can wait for a new release or, if you are an admin, update your 4CAT to our main branch (Control Panel -> Restart or Upgrade -> Upgrade to 'master').
• I am actually currently working on showing media files that were downloaded through 4CAT processors (e.g. 'Download images') in the Explorer. We've already done some preparatory work for this and hopefully I can implement this before the new release. In the meantime, if you have updated to master, you can upload a zip folder of images (e.g. Insta images) with Create dataset -> Import/upload media files. You can then inspect these images in the Explorer.

Hope that helps.

[craigfahner]

Thanks @sal-uva for your response. It seems that I am running the latest version, yet the URL issue remains.

Loading the .zip folder of images (or individual insta images created by 4cat) results in the following error (visible in the Docker console):

[2026-02-02 20:20:51 +0000] [138] [DEBUG] GET /results/43e0ad4c57a30836528167dcce37df7c/explorer/

ERROR:4cat-frontend:NotImplementedError (http://localhost/results/43e0ad4c57a30836528167dcce37df7c/explorer/): Cannot iterate through .zip file

ERROR:root:NotImplementedError (http://localhost/results/43e0ad4c57a30836528167dcce37df7c/explorer/): Cannot iterate through .zip file at app.py:917→app.py:902→_limits.py:326→utils.py:290→helpers.py:330→views_explorer.py:104→dataset.py:448→dataset.py:359

Thanks again, please let me know if you have any insights.

[sal-uva]

Hi Craig, I tried to replicate this and both works for me. I suspect you're not on the latest master commit yet? Simply running the latest release is not yet sufficient since we fixed this issue only a few days back, and we haven't published a new release since. You can either wait until we do or upgrade to master via these instructions.

[craigfahner]

Hi @sal-uva,

Thanks for your help. Unfortunately I've tried a couple times to upgrade to the latest commit using this link (and its respective .env file), but still these issues persist. Reviewing the history on the master branch, it seems the latest significant change was 15 days ago.

Happy to wait for the next release also – thanks again for your responses.