I'm just wondering if it is possible to modify a form submission asset once it has been completed as a public user. Logged in users don't seem to have any problems resuming the submission (if they have permissions) and saving changes, however public users (even if granted write/admin permissions over the submissions folder) seem to be unable to do so. When they have sufficient permissions public users are able to retrieve the stored values, but are unable to resubmit the form (it just reloads the page). Has anyone encountered similar issues before?
On a slightly related note I was messing around with the JS API to try and work around this - Is there any reason why I can't use the JS API to set the complete attribute on a form submission back to 0? If I try set it to other random values it will set the value to "1", but it won't allow me to change the attribute to 0, the POST comes back with:
{"error":"Please make sure to provide an Asset ID, Attribute Name and Attribute Value"}{"success":"Attribute complete has been set to 0"}
the system log shows nothing, and the system error log just shows:
Raw Entry: [07-Dec-2009 20:05:53]
Raw Entry: 0: js_api_error_handler (/home/websites/gjames3242/packages/web_services/js_api/js_api_error_handler.inc line 31):
Raw Entry: ERROR: Please make sure to provide an Asset ID, Attribute Name and Attribute Value. Error Number:512
There might be an error much deeper than the one returned, such as the system not allowing you to set the form submission back to 0, but the JS API does not know that, so it just returns a general error about not being able to set the attribute.
Did you see anything else before that JS API error in the logs?
[quote]
There might be an error much deeper than the one returned, such as the system not allowing you to set the form submission back to 0, but the JS API does not know that, so it just returns a general error about not being able to set the attribute.
Did you see anything else before that JS API error in the logs?
[/quote]
Nope, that's all that appears in the logs.
On a fairly unrelated note, but on the topic of the API, is there any reason why you dump all the data into the query string when you're using POST? I was getting 414 errors when I was using (misusing?) the API to set large amounts of data. I got around it by forming my own POST instead, so no real dramas, but I was curious.
[quote]
On a fairly unrelated note, but on the topic of the API, is there any reason why you dump all the data into the query string when you're using POST? I was getting 414 errors when I was using (misusing?) the API to set large amounts of data. I got around it by forming my own POST instead, so no real dramas, but I was curious.
[/quote]
When I first wrote it, my focus was for small functions such as sending the ID to get attributes and setting values such as the asset name. It expanded into much more than that, and, the method for send the data has not changed.
It is something I would be happy to work on changing, but I a not sure I have the time right now. I will add it to my list of things to add, but if you wanted to submit code as well, we would appreciate that as well.