call returns around 21 items but they do not display in the entries list. The green processing message just stays on the screen. I dont seem to get any asp errors or JS errors. My form is a multipage form and has a lare number of fields (around 50 over the 3 steps)
We are hoping to launch this really soon if possible a quick response would be great, could this be to do with the json size?
Thanks for your reply, it doesnt seem to have worked for me unfortunatly. The records.aspx call doesnt throw any kind of error and in fact returns the JSON i would expect, it is just that it does not seem to output it to the screen.
Backend failing to retrieve entries
Hey Guys,
Still running into some issues with my contour install, When I try and retrieve a months worth of samples (around 20 entries) from the database
/umbraco/plugins/umbracoContour/webservices/records.aspx
call returns around 21 items but they do not display in the entries list. The green processing message just stays on the screen. I dont seem to get any asp errors or JS errors. My form is a multipage form and has a lare number of fields (around 50 over the 3 steps)
We are hoping to launch this really soon if possible a quick response would be great, could this be to do with the json size?
L
I am experiencing exactly the same problem. It will be great if anyone from the HQ can look at this issue.
Hi Lachlann,
I just found a solution. You need to modify the web.config file as follows
<system.web>
<httpRuntime requestValidationMode="2.0" executionTimeout="600" maxRequestLength="Number" maxQueryStringLength = "Number"/>
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits
maxQueryString="Number"
/>
</requestFiltering>
</security>
Number = The max size you want.
I hope it helps
M.
Hi Muhammad,
Thanks for your reply, it doesnt seem to have worked for me unfortunatly. The records.aspx call doesnt throw any kind of error and in fact returns the JSON i would expect, it is just that it does not seem to output it to the screen.
Best
L
is working on a reply...