Custom Query (2152 matches)
Results (1111 - 1113 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1103 | duplicate | searching broken in development setup | johnlawrenceaspden | |
Description |
With the default test data created by paster db clean paster db init paster create-test-data going to the front page shows two recently changed packages A Wonderful Story A Novel by Tolstoy But none of those words "Wonderful", etc produce search hits. In fact as far as I can tell, nothing produces any search hits. That isn't true on ckan.net, where searching seems to work. |
|||
#1104 | fixed | create-test-data doesn't index the packages it creates | dread | johnlawrenceaspden |
Description |
With the default test data created by paster db clean paster db init paster create-test-data going to the front page shows two recently changed packages A Wonderful Story A Novel by Tolstoy But none of those words "Wonderful", etc produce search hits. In fact as far as I can tell, nothing produces any search hits. That isn't true on ckan.net, where searching seems to work. |
|||
#1115 | wontfix | can have two authzgroups with the same name | johnlawrenceaspden | |
Description |
If you've got edit permission on an authzgroup, then you can change its name to be the same as another existing authzgroup. This causes some strange UI effects at worst, and probably causes worse problems somewhere else. Is there any reason why changing the names of existing authzgroups should be allowed? And if so, name collisions should presumably be guarded against in both the name-changing and creation functions |