Results 16 comments of PG Lewis

There is already a dedicated "Custom Template" textarea field in the list items widget. If you have templates enabled and have available templates, the "Template" field is a drop down...

This was introduced here: https://github.com/pods-framework/pods/commit/523af9

Sorry... why the reference to that issue with no other comment... ?

This is an escaping issue from all the backslashes in the SQL, so I'm leaning toward "unrelated"

@Shelob9: do you remember what this was about? Since it's involving the unit tests I suspect this is something that has since been ironed out.

In the case of an ACT with a number field, default 0 but no data (the field is added after records are created) results in `NULL` from `display()` or `field()`

Executive decision that this shouldn't hold up 2.5.3 (nothing breaks, it just leaves detritus), so punting to the next milestone.

I think the best suggestion to avoid re-hashing is also to follow WordPress's lead: ![wordpress-password](https://cloud.githubusercontent.com/assets/1973916/3249670/ebae1ec0-f19b-11e3-8dea-c3a4b6fc9005.png) There is no use in populating the password box after the password has been hashed...

One more thing from the brainstorming session in `#pods-dev`: we should also expose a (public static?) method to check the input against the hash. Implementors need this functionality and the...