> I'm using CKAN version tagged ckan-1.6 at the github.com/okfn/ckan. Yep, I can reproduce your bug in ckan-1.6. But not in the soon-to-be-released 1.6.1, so I guess this bug has already been fixed. Thanks for letting us know about this anyway