Chris Jensen commented on request
If you’re using
for people following a link from email, it will only work return true if you’ve checked “When the recipient clicks on the email, automatically add their info to any forms”.
Probably obvious, but caught me out during testing.
posted 2016-04-21 01:12:03 -0700
request.sorta_logged_in?
request.sorta_logged_in?
for people following a link from email, it will only work return true if you’ve checked “When the recipient clicks on the email, automatically add their info to any forms”.
Probably obvious, but caught me out during testing.
Chris Jensen commented on page
In case this has thrown anyone else, it’s worth noting that children only includes a pages that are published. Unlisted pages will not be included.
posted 2016-02-28 16:01:56 -0800
Chris Jensen commented on API based credential checking?
I don’t follow – the OAuth does not allow you to identify the specific user, does it?
posted 2016-02-28 02:51:35 -0800
Chris Jensen tagged
Alex Montgomery's
When will API and web hooks be updated to reflect the new paths? with Important
posted 2016-02-28 02:42:31 -0800
Chris Jensen commented on Liquid Basics
Hi Lindsey,
The challenge is that sometimes it’s not always obvious what the variables on a particular object are named when you want to access a particular attribute of, say, a person, or a page.
This gets even trickier when iterating over a nested variable, like, say, all the custom fields on a person, or a nested, nested field like, say, the options of choice custom field of a person.
(What’s the attribute to access the id of the choice and the value?)
In the shopify example linked to, the person is able to print out a list of all the attributes on an object so as to help them find that information out.
He’s not using developer tools, he’s just doing a regular liquid output, but with a filter that dumps the object for him, in the example I linked to, where he writes:
He probably ended up in his HTML with something like
Without that, I’ve found myself in the position of embedding all my guesses as to what an attribute might be named until I find it, eg
which is time consuming, and also means I end up posting more requests to you guys when I can’t guess it ;-)
posted 2016-01-24 16:28:27 -0800
The challenge is that sometimes it’s not always obvious what the variables on a particular object are named when you want to access a particular attribute of, say, a person, or a page.
This gets even trickier when iterating over a nested variable, like, say, all the custom fields on a person, or a nested, nested field like, say, the options of choice custom field of a person.
(What’s the attribute to access the id of the choice and the value?)
In the shopify example linked to, the person is able to print out a list of all the attributes on an object so as to help them find that information out.
He’s not using developer tools, he’s just doing a regular liquid output, but with a filter that dumps the object for him, in the example I linked to, where he writes:
{{item | json}}He probably ended up in his HTML with something like
{'name':'The things name',
'id':1,
'country_code':'AU'}Without that, I’ve found myself in the position of embedding all my guesses as to what an attribute might be named until I find it, eg
{{item.country_code}}
{{item.countrycode}}
{{item.country}}
{{item.location}}which is time consuming, and also means I end up posting more requests to you guys when I can’t guess it ;-)
Chris Jensen commented on Stop form redirect upon success (or customize with js)
For those wondering how to set the page dynamically, I have found that it is the page_id value that matters.
Setting that to the destination page you want gets the desired results.
posted 2015-12-15 20:08:16 -0800
Setting that to the destination page you want gets the desired results.
Chris Jensen commented on page.signup
Why can’t a user leave feedback on a signup page?
I noticed the volunteer template has a {% text_area “content”, class:“textarea form-control autogrow” %} that allows general comments when the user volunteers, but if I try to copy paste that into my template for signups, I get the liquid error: content is not a valid form field for Signup.
It would be valuable for us to enable feedback/comments on our signup pages.
posted 2015-12-15 16:23:59 -0800
I noticed the volunteer template has a {% text_area “content”, class:“textarea form-control autogrow” %} that allows general comments when the user volunteers, but if I try to copy paste that into my template for signups, I get the liquid error: content is not a valid form field for Signup.
It would be valuable for us to enable feedback/comments on our signup pages.