Timeline for Programmatically validate a node?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 27, 2012 at 20:31 | history | suggested | htoip | CC BY-SA 3.0 |
Linked function calls to API documentation
|
| Mar 27, 2012 at 19:08 | review | Suggested edits | |||
| S Mar 27, 2012 at 20:31 | |||||
| Oct 31, 2011 at 8:16 | vote | accept | berkes | ||
| Oct 28, 2011 at 15:21 | answer | added | avpaderno♦ | timeline score: 5 | |
| Oct 28, 2011 at 14:20 | history | tweeted | twitter.com/#!/StackDrupal/status/129880139273211905 | ||
| Oct 28, 2011 at 13:29 | history | edited | berkes | CC BY-SA 3.0 |
added 15 characters in body
|
| Oct 28, 2011 at 13:28 | comment | added | berkes | I just want to avoid storing nodes that are "invalid", according to whatever defines if they are valid. If, say, an image is required, one can assume that the theme will be able to render that image, regardless. If my importers start saving nodes without these images, the theme will print broken image-links. | |
| Oct 28, 2011 at 13:24 | comment | added | mpdonadio♦ | Is the problem that your data source that you are using may have invalid data in it, or just that you are trying to validate your own code? | |
| Oct 28, 2011 at 12:40 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
added 46 characters in body; edited tags; edited title
|
| Oct 28, 2011 at 12:12 | history | asked | berkes | CC BY-SA 3.0 |