0
  1. How to set rights on parent Publication? I am able to set rights on all child Publications using Core Service API. Issue is with parent Publication. In our current CMS, parent Publication has rights setup. I am trying to modify these rights and find out how these rights were setup on parent Publication, or at some point was this a child Publication with rights changed to a parent Publication.

    Error : Unable to save the Publication - No Parents have been added.

  2. How to set permissions on Category and Keyword org item using Core Service call or even manually? Can we only set permissions on individual Categories, not on the organization item? Tried with Core Service call:

    CategoryData organizationalItem = (CategoryData)client.Read("/webdav/010%20Schemas/Categories%20and%20Keywords", new ReadOptions());
    

    Error: No items found for WebDAV URL(s): /webdav/010%20Schemas/Categories%20and%20Keywords.

  3. If permissions are set on each Category, when a new Category is created, where does it inherit the permissions from?

| improve this question | | | | |
  • Well, you are not loading Category, you are trying to load "Categories and Keyword", which is container for all categories. Please try to load Category itself – Marko Milic Oct 3 '17 at 7:41
3

The second error is an expected one, you are trying to read the Categories and Keywords node, which isn't an Organizational item, it is just a node in the navigation tree. You can see that in the CME, as there are no properties for that node. So you are also unable to set rights and permissions on that, you have to set these on each Category separately.

For the first error, I'm wondering exactly what you are setting? The first error seems to indicate you are setting rights that are inherited from a parent, which isn't there for that Publication. I would suggest that you edit your question and supply a bit more detail to that part of the question.

update

A top level parent Publication can never be changed to anything lower, also a Publication can never be added into a BluePrint unless it was already part of that BluePrint before. So with that knowledge, the error you mention still doesn't make sense, unless there is something wrong in your database. But without tangible details there isn't much more I can add to this answer.

As for your third question, When you create a new Category, it will be given read permissions to all Groups that have rights set in the Publication it is created in. It basically is up to the creator of the Category to set the correct permissions at creation time. Keywords will again inherit these settings once created.

| improve this answer | | | | |
  • 1
    Bart you got me by 30 seconds :D – Marko Milic Oct 3 '17 at 7:42
  • 1
    @MarkoMilic I've had the complaint about me being too fast before :D – Bart Koopman Oct 3 '17 at 7:44
  • hahahahahhahahahahahahhah – Marko Milic Oct 3 '17 at 7:48
  • @BartKoopman : Modified the question. – Deepthi Mandava Oct 3 '17 at 14:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.