Fri, 10 Apr 2026 14:37:18 +0000 https://bugs.horde.org/ticket/6494 Tag cloud Show last 500 tags from images and galleries Mon, 17 Mar 2008 22:52:41 +0000 https://bugs.horde.org/ticket/6494#t43944 And of course the patch for Ansel_Tags Mon, 17 Mar 2008 22:53:59 +0000 https://bugs.horde.org/ticket/6494#t43945 I'm curious, why do you want to separate the image and gallery tags...and where do you see this page fitting into Ansel, as a Block in addition to the existing Tag Cloud block? Tue, 18 Mar 2008 00:20:14 +0000 https://bugs.horde.org/ticket/6494#t43947 > I'm curious, why do you want to separate the image and gallery > tags...and where do you see this page fitting into Ansel, as a Block > in addition to the existing Tag Cloud block? After importing my galleries, I auto-generated tags from captions. I see that words significantly differs from galleries and images so I keep them separated . It can go as a separate page listed in Ansel menu. btw: listTagInfo not limits any results. So just having the cloud block I am g oing out execution time. I still haven't got time to deal with this issue but you should really limit any possible long results. Duck Tue, 18 Mar 2008 07:48:52 +0000 https://bugs.horde.org/ticket/6494#t43952 > After importing my galleries, I auto-generated tags from captions. I see that > words significantly differs from galleries and images so I keep them > separated > . It can go as a separate page listed in Ansel menu. I'm not sure I agree with having two seperate tag clouds. I'd much rather integrate a filter to limit to galleries or images in either the existing results view or a more general serach function (something I've been meaning to do when I get the time). > btw: listTagInfo not limits any results. So just having the cloud > block I am g > oing out execution time. I still haven't got time to deal with this issue but > you should really limit any possible long results. That function already takes an array of tags to limit the search by and only returns the full tag list if it is omitted...however, I can see you point with large tag sets. It does make sense to limit to the first, I don't know, 500 or so tags (by resource count) if there are none passed in. Tue, 18 Mar 2008 13:51:41 +0000 https://bugs.horde.org/ticket/6494#t43957 Added a limit check in listTagInfo, and resolving this. Wed, 19 Mar 2008 15:32:17 +0000 https://bugs.horde.org/ticket/6494#t44003