Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource gets added to RSS on PUBLIC, not on published #1248

Closed
peterdesmet opened this issue Dec 16, 2015 · 3 comments
Closed

Resource gets added to RSS on PUBLIC, not on published #1248

peterdesmet opened this issue Dec 16, 2015 · 3 comments

Comments

@peterdesmet
Copy link
Member

@peterdesmet peterdesmet commented Dec 16, 2015

Steps:

  1. I add a new resource to our IPT
  2. The to-be-published version 1.0 of the resource will be public, so I set visibility to PUBLIC. Since I haven't finished writing the metadata or uploading the data yet, I'm not yet publishing the dataset.
  3. The status PUBLIC triggers the IPT to include the resource in the RSS.
  4. Via IFTTT a tweet is sent with the link to the not-yet-published dataset.
  5. Visitors of the link see an Not authorized page

Solution: Setting a dataset to PUBLIC should not trigger the IPT to update the RSS. Only publishing a resource should trigger this.

Note: the not-yet-published resource is NOT included in the DCAT feed, which is the correct behaviour.

@kbraak
Copy link
Contributor

@kbraak kbraak commented Dec 16, 2015

Thanks for reporting this issue Peter. It should be possible to fix in the next minor release (2.3.3).

kbraak added a commit that referenced this issue Sep 30, 2016
@kbraak kbraak self-assigned this Oct 3, 2016
@kbraak
Copy link
Contributor

@kbraak kbraak commented Oct 3, 2016

Confirmed working, closing issue.

@kbraak kbraak closed this Oct 3, 2016
@kbraak
Copy link
Contributor

@kbraak kbraak commented Dec 16, 2016

Issue verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Version 2.3.3
Done (included in v2.3.3)
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.