Skip to main content
8 events
when toggle format what by license comment
Feb 28, 2016 at 11:59 vote accept Paul Frost
Feb 28, 2016 at 11:59 comment added Paul Frost I've got this working now. I'm using the original entryId as the secretKey in a hidden input and also asking for their email address as a second test. I suspect many people will forget any sort of password that they set or remember a generated random string. Security isn't that big an issue in this case.
Feb 27, 2016 at 20:19 history edited carlcs CC BY-SA 3.0
added 483 characters in body
Feb 27, 2016 at 20:02 comment added carlcs Well, you could also allow the user to set a password instead of generating one. But what happens when more than one "request" is stored with a password "1111"? This (most likely) won't happen with the generated ones. What you could do is to let them input a password, show them the request's ID and require them to input both, ID and password to submit a "response".
Feb 27, 2016 at 18:58 comment added Paul Frost Thanks carlcs, any reason why the user couldn't input their own password (instead of using Preparse) when they post their first entry and then use that when they submit the second one to remove it? Any chance of adding some comments to the code to explain what's happening so I can try and learn for the future. If the first set only gets all entries with the type: 'requests' how does the second set hasResponse get type: 'responses' find any 'responses' if the original set only included 'requests'?
Feb 27, 2016 at 18:20 history edited carlcs CC BY-SA 3.0
added 900 characters in body
Feb 27, 2016 at 17:22 comment added Paul Frost That sounds like a plan. I've been thinking about letting them create a second entry and having a field that holds some common string, but I can't work out how to compare 2 separate entries for a matching string and then not show either if there is a match. Any pointers to a code example?
Feb 27, 2016 at 1:38 history answered carlcs CC BY-SA 3.0