For sets we can use [flickr-photoset:id=72157634563269642,size=s,num=8,media=all,random=true,count=false]

This could be made valid also for groups and users, just as we did for sets by using the functions from the Flickr Block submodule.

Comments

lolandese’s picture

Status: Active » Needs work
StatusFileSize
new29.96 KB

User IDs. Posting intermediate patch to save the work till now.

lolandese’s picture

Status: Needs work » Needs review
StatusFileSize
new49.89 KB

264 insertions(+), 526 deletions(-)

The ideal patch. A bunch of new features and a bunch of code lines removed.

New features:

  • Extended parameters for text filter tags with group and user IDs
  • Block 0 is dynamic now, from 'User recent photos' to 'User (node author) recent Flickr photos tagged as term from node'. If a site is used by multiple users https://drupal.org/project/private_taxonomy would be a good addition. It avoids the terms added by others showing up (as suggestions) in the vocabulary used to filter on Flickr tags. To add to the documentation once this goes into the stable version.
  • #2253897: Flickr tags for text filter E.g. [flickr-user:id=98518260@N02, size=q, tags=kids/men] is now possible. Also [flickr-group:id=91484156@N00,size=q,num=4,tags=flowers]
  • Unified 'recent' and 'random' functions by adding a parameter and moved them from flickr_block.module to flickr.inc.

  • Commit a2f2db0 on 7.x-1.x by lolandese:
    Issue #2253641 by lolandese: Extend parameters for group, user IDs and...
lolandese’s picture

lolandese’s picture

Version: 7.x-1.x-dev » 6.x-1.x-dev
Status: Fixed » Patch (to be ported)

  • Commit 0142f9f on 7.x-1.x by lolandese:
    Issue #2253641 by lolandese: Removed unused parameter  in forgotten...
lolandese’s picture

Status: Patch (to be ported) » Closed (won't fix)
lolandese’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Closed (won't fix) » Closed (fixed)

Setting this back to D7 and being 'fixed (closed)'.

Main reason is the fact that links to this issue show the status on hover without revealing the version (6 or 7). This might give the impression that the mentioned issue will not be solved, while in fact it is already fixed for the D7 version. 'Fixed (closed)' reflects the current status correctly for D7. 'Closed (won't fix)' is only valid for the minimally maintained D6 version of the module.