On Thursday, 2 November 2017 at 18:51:09 UTC, bauss wrote:
On Thursday, 2 November 2017 at 18:48:10 UTC, bauss wrote:
Before you did:
render!("index.dt", title, major_categories);
Have you tried to check the contents of "major_categories"
making sure it's all there. Just to figure out whether
On Thursday, 2 November 2017 at 18:48:10 UTC, bauss wrote:
On Thursday, 2 November 2017 at 16:23:55 UTC, SamwiseFilmore
wrote:
On Thursday, 2 November 2017 at 08:40:28 UTC, bauss wrote:
[...]
No, the html does come in, and the whole content of the
rendered page is sent to the browser. The
On Thursday, 2 November 2017 at 16:23:55 UTC, SamwiseFilmore
wrote:
On Thursday, 2 November 2017 at 08:40:28 UTC, bauss wrote:
Do you get a response back with rendered html or does the
connection get dropped?
No, the html does come in, and the whole content of the
rendered page is sent to
On Thursday, 2 November 2017 at 08:40:28 UTC, bauss wrote:
Do you get a response back with rendered html or does the
connection get dropped?
No, the html does come in, and the whole content of the rendered
page is sent to the browser. The page has closing head and body
tags.
Have you tried
On Thursday, 2 November 2017 at 04:00:10 UTC, SamwiseFilmore
wrote:
I've got a serialized JSON structure that looks something like
this:
[...]
Do you get a response back with rendered html or does the
connection get dropped?
Have you tried to cut down the amount of data and see if it will
I've got a serialized JSON structure that looks something like
this:
{
"title": "Webpage title",
"major_categories": [
{
"title": "Major Category title",
"categories": [
{
"title": "Minor Category title",
