[ckan-dev] Trouble setting up email notifications

Wed Mar 12 18:55:41 UTC 2014

Ohh yes... I forgot to mention that I configured the .ini file.

I added the empty dictionary param and now I'm simply getting an authorization error:

curl http://localhost/api/action/send_email_notifications  -H "X-CKAN-API-Key:<my-api-key>" -d '{}'
{"help": "Send any pending activity stream notification emails to users.\n\n    You must provide a sysadmin's API key in the Authorization header of the\n    request, or call this action from the command-line via a `paster post ...`\n    command.\n\n    ", "success": true, "result": null}

The api key was taken from the admin account page.

I think I remember reading somewhere in the docs about needing to enable authorization on the server... Could this be an issue?

Thanks for your help!

Justin

From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] On Behalf Of Stéphane Guidoin
Sent: Wednesday, March 12, 2014 12:31 PM
To: CKAN Development Discussions
Cc: Jeff Socia
Subject: Re: [ckan-dev] Trouble setting up email notifications

Hey Justin,

When posting a request to the email trigger via the API, you have to post an empty dictionnary.

So with curl the command should look like that:
curl http://my.domain/api/action/send_email_notifications  -H "X-CKAN-API-Key:ae475a5a-6a9f-4800-9e2d-x338847r" -d '{}'

Also: did you configure all the SMTP stuff in the .ini?

Even though it does not look interesting, please post any error you see, either in curl or in your web server error log.

Steph

On Wed, Mar 12, 2014 at 12:33 PM, Justin Lewis <jlewis at drcog.org<mailto:jlewis at drcog.org>> wrote:
Hi,

I'm trying to get e-mail notifications setup for a local CKAN instance and having some trouble.

While trying to run the '/api/action/send_email_notifications' request through the terminal I get errors like this "Bad request - JSON Error: No request body data".  I have tried:

1.       sending as simple http request through a browser

2.       sending as a curl request - 'curl http://geodataportaldev/api/action/send_email_notifications -H "Authorization:my-api-key"'

3.       sending as a paster request as outlined in the docs  -  echo '{}' | /usr/lib/ckan/default/bin/paster --plugin=ckan post -c /etc/ckan/default/production.ini /api/action/send_email_notifications

a.       ensuring that the paths are correct to production.ini in the paster request

4.       adding authorization (api_key) to all variations of the request

5.       ensured email notifications where enabled and sending to a valid email

6.       ensured there where recent changes to data that would trigger an email

I'm unsure where to go from here.  If anyone has a working example of a request this could be helpful to make sure that I am getting the syntax correct.  Otherwise I am seeing little useful info in regards to log errors.

Thank You,

Justin Lewis | Software Developer | Administration and Finance
Direct 303-480-6750<tel:303-480-6750> | Fax 303-480-6790<tel:303-480-6790> | jlewis at drcog.org<mailto:jlewis at drcog.org>

[cid:image001.gif at 01CF3DF2.5FEAD840]<http://www.drcog.org/>

[cid:image002.png at 01CF3DF2.5FEAD840]<http://www.denverregionalequityatlas.org/>
Check out the new interactive Regional Equity Atlas<http://denverregionalequityatlas.org/>: Mapping
opportunity on a regional scale from a local perspective.

[cid:image003.png at 01CF3DF2.5FEAD840]<http://www.facebook.com/Denver.Regional.Council.of.Governments>   [cid:image004.png at 01CF3DF2.5FEAD840] <https://twitter.com/DRCOGorg>    [cid:image005.png at 01CF3DF2.5FEAD840] <http://www.linkedin.com/company/denver-regional-council-of-governments?trk=cp_followed_name_denver-regional-council-of-governments>

_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org>
https://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140312/75c7ecb4/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 8239 bytes
Desc: image001.gif
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140312/75c7ecb4/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7178 bytes
Desc: image002.png
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140312/75c7ecb4/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2696 bytes
Desc: image003.png
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140312/75c7ecb4/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1830 bytes
Desc: image004.png
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140312/75c7ecb4/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2770 bytes
Desc: image005.png
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140312/75c7ecb4/attachment-0015.png>