-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
ACL compatibility problem between parse.com and parse-server #1150
Comments
After doing more test I found following behavior. parse.com parse-server Not sure is it a good suggestion if we change parse-server to update acl both way (include @gfosco Regarding to your comment in #167, I think you can give some comments on this too. Any comments would be appreciated! Thanks a lot! |
I'm not sure if this should be added to this or made a separate issue, so, I apologize if this is the wrong place for this. It could be related, so, I'm defaulting to adding it to the Issue. If you have Public Read/Write CLP's enabled and you use Pointer permissions, Parse.com server will still return the same as Public Read/Write, but, Parse Server will return only records that apply to the Pointer Permissions. This is most likely an edge case, but, I can see people wanting Public Read and only allow Write based off of an Pointer CLP. If this is unclear, I can try my best to help. |
It seems to be a bug in the pointer permissions. I'll have a look later |
Related to #1953 |
@carmenlau looking at the PR, I believe the original issue has been fixed. Feel free to reopen if it isn't the case |
During migration, it is difficult to avoid using parse.com server and self hosted parse-server at the same time. As per mentioned on issue #167,
_acl
has migrated to new structure_wperm
and_rperm
. The data will be inconsistent if we run parse.com cloud code and parse-server at the same time. For example, if we update ACL in the new app, but ACL in the old app will remain unchanged. Or create a new object in new app, the ACL object will be empty in the existing parse.com cloud code.The text was updated successfully, but these errors were encountered: