{23} Trac comments (3729 matches)

Results (3701 - 3729 of 3729)

← 28 29 30 31 32 33 34 35 36 37 38
Ticket Posixtime Author Newvalue
#1413 1322481235000000 dread approximate 'once they log in' as 'whenever they visit their account page' I had imagined that this would be done in the user.py:logged_in method, but doing it in your way sounds like an even better plan. Another thought is: a lot of people might just use the cookie and v. rarely logout/in. Perhaps it could be done when they come back to the site at intervals (e.g. daily)? i18n Yes your strings should be internationalised because they are user visible. You're right that these other strings should be internationalised. I've created a separate ticket for this: #1491
#849 1291715179000000 pudo == #846
#698 1292239372000000 rgrp 1. move repo to bitbucket 2. clone james proxy code and modify to make google spreadsheets compatible (add a test ...) 3. update the ckanext to pass on parameters .... 4. Deploy all of this to test.ckan.net 5. Rufus: check redirects with javascript
#263 1273083179000000 johnbywater 1. Have suspended cookie setting (which was remembering the provider). 2. We are already using openid-selector. 3. Fixed type in page ('indentity' => 'identity') 4. Have changed 'sign in or create new account' to 'Login to CKAN using Open ID'
#1737 1337594352000000 icmurray - package_search action is now documented, with reference to the solr search parameters available. http://docs.ckan.org/en/latest/apiv3.html (auto-docs not working on rtd at the moment). - actions defined in get.py are now GETable. http://docs.ckan.org/en/latest/apiv3.html#get-able-actions - we won't be providing direct access to solr api, as we think the cost outweighs the benefit.
#521 1283538342000000 pudo * still needs to have schema adapted a bit * work so far is at eu4:~/var/solr/iati/conf/schema.xml
#1695 1327426989000000 dread * links_to/linked_from was already available (since Sept - Friedrich put them in). * Count property not easy so not done. * POST to the Relationships Register (all three) works now (and the original way via the entity still works too) * Schema/validation was added along with tests for error conditions. * Creating a new relationship documented in Model Methods * 'Model Formats' section in API docs restored and updated. Committed to master aimed for release 1.6 https://github.com/okfn/ckan/commit/f16450c1c34cac09046a098273f66d2b75aa87dd Spent 6h on this in the end - generally useful tidying in this area.
#851 1292860957000000 wwaites * link checker above uses the queue. queue not running generally * quickest way forward is just to put the curate tool in a cron job and make a suitable rule. shall do this soonest
#520 1283538080000000 pudo * http://bitbucket.org/okfn/iati/changeset/378431974c76 solr facets
#135 1255180858000000 dread * authz/is_sysadmin method now looks up sysadmins in user-role table * SystemRole and System added * migration script for new SystemRole and System * CLI for adding sysadmins Done in cset:94028478608a
#518 1283536932000000 pudo * Still needs "archive file" and "donors country" fields, PE questions to be answered.
#518 1282893844000000 pudo * Priority: 5 * Web user interface for publishing entities
#519 1283536828000000 pudo * Mostly implemented, still have to consider further cleanup.
#1119 1304104689000000 rgrp * Merged ckanext-upload into ckanext-storage * Got existing API systemin in ckanext-storage fully working (e.g. api section was broken -- maybe due to changed boto ...) * API now supports GET requests and JSONP where appropriate * Added auth form to API (could be useful for ajax form stuff going forward) * Improved UI of upload including having ckan based file links (using redirects) * Set uploaded-by field on uploaded files * Checked on AWS And GS Also did: * Improved ofs in various ways including change to standard metadata handling and improved testing (see e.g. https://bitbucket.org/okfn/ofs/changeset/36fac29b7775) * Tracked down [https://github.com/okfn/boto/commit/0d9635c8a9785c9b20b44ee93a0679c002961592 bug with boto and metadata updating on GS] and provided patch.
#523 1283897688000000 pudo * Auth will be finished in #524. * PE write access etc. via standard API, compare ckanextiati:a02467cb67ba
#501 1282563166000000 pudo * Apache version is documented here: http://knowledgeforge.net/okfn/tasks/ticket/466
#843 1319710380000000 dread * "we should show the openid as well to distinguish between users with the same name." - when "Full name" is not distinguishable, maybe best to display the unique 'name' field as a hover-over. * "on account creation, the user should be redirected to their personal details page to encourage them to fill in a human readable name." - yes you always got take to the personal details page. We should use a flash message at this point if they have not filled in the "Full name" field to suggest they click edit and do this. * "List is to long" - this has been addressed - see http://thedatahub.org/user
#1214 1310067831000000 dread underscore in search parameters I think its trying to filter search results by values of an extra field called "_", even though this probably doesn't occur. If it is not too ugly, I suggest using one of your other ideas for solving the cache issue. I suggest you bring it up with Rufus or the ckan-dev list to get opinions.
#1292 1320145677000000 dread Review process of releases and updating strings (pot) and translations (po) files c.f. http://lists.okfn.org/pipermail/ckan-dev/2011-May/000718.html http://wiki.ckan.net/Release_process updated with basic process Get language changing thing to get home page to mostly work - push to key strings translated (or don't advertise the translation?) Welcome message is translated in all languages. Most language have upped their percentage translated significantly and Swedish and Polish added as well. Review long list of strings for improvement Consolidate any? Get rid of i18n for strings in api About 50% of the strings are templates, 30% are in the logic layer and 20% are in the controllers. Removed a handful from ckan/lib/base.py that were only displayed in the api, but the logic layer ones are generally errors that can be displayed in the Web UI as well as the API, so not ideal to remove. Try and remove javascript Tom did this. Add in extensions This could be done. Have raised ticket #1292 for this, next release. #1374 Fix switching to en from other default language Done #1417 Fix browser language detection Done
#1214 1310067327000000 dread Relationships use "object" key rather than id or package_id. I'm not totally clear on this one. The URLs for relationship editing can be package ids or names. When you GET a relationship packages are referred to in IDs for v2 API. When you create or update a relationship it returns package IDs for v2 API. Are you referring to the relationships listed in the response when you PUT a package? (If so that would be fixed by my previous fix.)
#1413 1322575534000000 seanh Another thought is: a lot of people might just use the cookie and v. rarely logout/in. Perhaps it could be done when they come back to the site at intervals (e.g. daily)? As discussed on IRC I've moved the notice from the user account page to the front page, in the hopes that people will see it often enough even if they are always logged in via a cookie. As discussed on IRC, we could make the notice appear on every page but no more than once per day, but that would be more complicated to implement and more likely to break. Yes your strings should be internationalised because they are user visible. Done. You're right that these other strings should be internationalised. I've created a separate ticket for this: #1491 Also done! :)
#251 1270564365000000 rgrp 1. /api/rest/revision/ returns nothing 2. /api/rest/revision/{id} does not return revision.packages and should do.
#221 1271756757000000 dread * Ability to add the package to groups on this page. MOVED to ticket:295 * Fields could be grouped. DONE * Inconsistent capitalisation (Url -> URL). DONE * Tag editor YUI script appears to break occasionally. DONE * Perhaps move to two column forms to save vertical space? IGNORE * Notes field to monospace? IGNORE * Extras fields need some jQuery love -- shouldn't have a fixed number available. MOVED into ticket:294 * Typography is a bit of a mess. DONE
#1739 1328495651000000 kindly fixed cset:117dce4d64de731e7b0a3c55175a1d093f2bf540
#353 1280262363000000 pudo cset:1366:e719f449bc74 fixes this
#2942 1348611144000000 dread > {{{ > >>> requests.post('http://datahub.io/api/action/package_list', data='{}', headers={'content-type': 'application/x-www-form-urlencoded'}).content > }}} Or even better: {{{ >>> requests.post('http://datahub.io/api/action/package_list', data='{}', headers={'content-type': 'application/json'}).content }}}
#842 1303474228000000 thejimmyg > Otherwise I see a button that says "login to add todo" > > expands out the form > Actually rather than expanding the form, you will go away to the login page and come back to see the expanded form (question: how does this redirect you back to the bottom?)
#1027 1299666326000000 pudo 1. home controller -> __before__ (check "site-read" on model.System) 2. user -> each individually (repoze-who pseudo action must not be blocked) * user-read (index/read/update pages for users) * user-create (register) 3. revision -> __before__ (check "site-read" on model.System) 4. tag -> site-read (__before__) functional/test_authz.py * denies site-read ... * checks for visitor / logged in user .. * checks you can still visit login
#336 1276162601000000 dread
← 28 29 30 31 32 33 34 35 36 37 38
Note: See TracReports for help on using and creating reports.