conwetlab / ckanext-datarequests Goto Github PK

In ckan-2.8.0 the template organization/read_base.html has an extra context variable named group_type. This template is extended by organization/datarequests.html without providing the extra context variable which causes the exception UndefinedError: 'group_type' is undefined to be raised when this extension is used with ckan-2.8.0.

I installed the extension with CKAN 2.6.6 and when creating a new datarequest I cannot add a specific organization. I start typing the org name but nothing happens, and even if I write the correct name I cannot choose it.
Thanks.

Also the creation date a new data request is -1 days ago

Data requests are displayed with inaccurate "Created" strings, eg "-1 days ago".

This appears to result from a lack of time zone handling. actions.py populates the creation timestamp without specifying a time zone, but when it is rendered, it uses a localisation method (formatters.localised_nice_date) that assumes a lack of time zone data means UTC.

Either the time zone should be specified when first creating the data request, or else the current server time zone (eg from helpers.get_display_timezone()) should be assumed when displaying it. The latter approach would also resolve existing data requests.

This is similar to ckan/ckanext-xloader#102

Email template reads:

An user has commented in the "Need dataset" data request. Check this new comment just in case you want to give it a reply.

You are receiving this notifications because:

• You are the owner of the data request
• You are a member of the organization where the data request has been created
• You are following the data request
• You have posted a comment in the data request

Should read:

"A" user

HI, We' ve tried to use this module but database generation failed since postgresql apparently does not support max length for field definition. I get the following exception:

Error - <class 'sqlalchemy.exc.ProgrammingError'>: (ProgrammingError) type modifier is not allowed for type "text"

Removing max length constraint from db.py and plugin.py did the job for me:

https://github.com/conwetlab/ckanext-datarequests/blob/master/ckanext/datarequests/db.py#L68

Related ticket:
https://bitbucket.org/zzzeek/sqlalchemy/issue/3370/text-and-length

Hi,
I am getting an internal server error on redirect after closing a request. The closing works.
The same thing happens on redirect after creating a request. The request is created, I get the error on the redirect that happens.

Anyone has ever had this problem?

When a request is deleted all the associated follows and comments must be deleted from the database.

Hello,

Ckan 2.10.x version deprecated IRoutes. Instead, blueprints are being used. Will there be any development regarding this issue?

Thank you.

Pylons routing is going away in CKAN 2.9, and should be replaced with Flask blueprints.

We're likely to build this into the qld-gov-au fork soon, but that has other changes mixed in. Could still serve as a reference.

Hi,

Can you advise if comments left on data requests will be handled by ckanext-disqus if installed (https://github.com/ckan/ckanext-disqus), or is it via a different mechanism?

Thanks!

Hi,
After I submit data request application, my webpage show server error.
Here is my apache2 error log.

I also look into base.py and I didn't found any redirect function also.
Please help, thank you

Hi, I wanted to add a translation for Macedonian directly on the instance of CKAN that we have.

I navigated to the ckanext-datarequests folder and I ran python setup.py init_catalog -l <YOUR_LOCALE> there.
Then I edited the mk/LC_MESSAGES/ckanext-datarequests.po file, and then I ran python setup.py compile_catalog, after which I got the following message:

97 of 97 messages (100%) translated in ckanext/datarequests/i18n/mk/LC_MESSAGES/ckanext-datarequests.po
compiling catalog ckanext/datarequests/i18n/mk/LC_MESSAGES/ckanext-datarequests.po to ckanext/datarequests/i18n/mk/LC_MESSAGES/ckanext-datarequests.mo

I then ran sudo supervisorctl reload. When I navigate to anything related to the datarequests while having chosen Macedonian as a language, I don't get the translations, and it's defaulted back to English.

Any idea on how to proceed?

Would be nice to sort by date, age, requester and organization

Any plans to update this extension for CKAN 2.8?

And have the ability to sort it (#4)

For folks who have integrated a different commenting system (e.g. discourse, disqus).

Perhaps, make it a setting in the ckan INI file?

<class 'sqlalchemy.exc.InvalidRequestError'>: Table 'datarequests' is already defined for this MetaData instance. Specify 'extend_existing=True' to redefine options and columns on an existing Table object.

So it can be shown in box_stats? See https://github.com/ckan/ckanext-showcase/blob/master/ckanext/showcase/templates/home/snippets/stats.html

Hey. Thanks for this plugin. We're having a small issue of spam. Any suggestions on how to handle it?

Out of the blue, I started getting this exception:

Traceback (most recent call last):
  File "/usr/lib/ckan/default/lib/python2.7/site.py", line 702, in <module>
    main()
  File "/usr/lib/ckan/default/lib/python2.7/site.py", line 682, in main
    paths_in_sys = addsitepackages(paths_in_sys)
  File "/usr/lib/ckan/default/lib/python2.7/site.py", line 281, in addsitepackages
    addsitedir(sitedir, known_paths)
  File "/usr/lib/ckan/default/lib/python2.7/site.py", line 203, in addsitedir
    addpackage(sitedir, name, known_paths)
  File "/usr/lib/ckan/default/lib/python2.7/site.py", line 172, in addpackage
    exec(line)
  File "<string>", line 1, in <module>
KeyError: 'ckanext'

Tried to debug, the KeyError is from exec(line) where line is any line from '.../site-packages/ckanext_datarequests-0.2.13-py2.7-nspkg.pth'.

I don't know how to further investigate this, if I place a set_trace() in a try block around the problematic statement and exec it manually in the debugger, everything works.

This codebase is currently not compatible with Python 3.

We've recently been updating the qld-gov-au fork to handle Python 3, but it has other changes mixed in (adding CircleCI testing, adding a "Closing Circumstances" field, etc), so it wouldn't be as simple as just merging it. It could serve as a reference, though.