CRUD Registration entities with Web services

Created on 24 July 2015, over 9 years ago
Updated 11 June 2023, over 1 year ago

First of all, many thanks to you guys for sharing and maintaining this module. On our project, it takes a core role.

We are currently setting up a Web service via Services β†’ and to handle CRUD on the registration entities, we use Services Entity API β†’ .

So far so good. But we ran into problems referring the rights management of the user_uid and author_uid fields of the object, which do have read only access. So we can retrieve, update and delete actual existing registration instances (created within drupal system), but are not able to create new registrations associated to the user via the App.

Is there any possibility, not to be forced to modify your module code, in order to create a fully filled and referenced registration instance? Or, if not, does it make sense (security issue) to modify permissions in code directly?
As the project ist already running, and we don't want to interfere with the current permission settings, we are curious about changing core code and asking therefore you for support.

Thank you very much for reading and for answering our support question.

πŸ’¬ Support request
Status

Closed: outdated

Version

1.4

Component

Registration Entity Access

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024