-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
File object on Config page goes type "String" instead of "File" #637
Comments
I saw this issue as well. After doing some investigating, I think this is an issue in parse-server itself and not parse-dashboard. In parse server, when transforming a 'File' object to be stored in the database it looks like it is converted to only the value of the 'name' field which appears to be the root cause of the issue you are reporting. (see FileCoder.jsonToDatabase): If you look in your underlying mongoDB, you can see that when you create a config value of type 'File' in the dashboard, it correctly creates the file, it is just referenced improperly in the '_GlobalConfig' collection. For example, if you create a 'File config value named 'test', your '_GlobalConfig' in mongo will have a field something like: If you manually update this in the database to be of the form: "test" : { and then refresh parse dashboard in the browser, you will now see that everything works properly. In summary, it looks like parse-server is failing to record the config value as type 'File' with a 'name' and 'url' field so even though the File itself is stored, the dashboard doesn't know where to find it. I will file an issue on Parse-Server |
Here is the tracking parse-server issue: |
Closing as tracked on parse-server |
Thanks @mross22 do you want to take on the fix? |
sure, I'll follow up on the other thread and send out a PR |
@mross22 @flovilmart this was actually a bug by itself, not related to parse-community/parse-server#3457. I've fixed it and opened a PR #666 |
Fixed in the latest release |
broken again |
@Abderezai that's not what I would say a proper issue report. |
Environment Setup
Parse Dashboard 1.0.22 on Windows 10, Node.js v6.9.2
Parse Server v2.3.2 on Amazon Linux, EC2, wrapped with Elastic Beanstalk
Steps to reproduce
The text was updated successfully, but these errors were encountered: