We want to make a directory with people that are associated to our organisation. Because there are about 700 we want to make this as easy as possible for us. The people should make their own entries.
Questions:
1. To not have to deal with many registered users, we thought it could be a good option, that when somebody creates an entry via a hidden form, this person gets some kind of password and only if this password is entered the content could be edited. Is there an option in forms to make some kind of password field and to check this before someone can edit the content or is this only possible via user roles?
2. Is there a way to review changes to the content before it gets public, without hiding the old content till the changes get reviewed?
3. Is there a maps function to enter a Zip code and to show entries nearby?
Thank you for getting in touch. 1. To not have to deal with many registered users, we thought it could be a good option, that when somebody creates an entry via a hidden form, this person gets some kind of password and only if this password is entered the content could be edited. Is there an option in forms to make some kind of password field and to check this before someone can edit the content or is this only possible via user roles?
Unfortunately this wouldn't be possible with Toolset as you will need some form of way to randomly generate that password and store it so that the user can use it to access the post. This would require some form of custom coding to achieve.
2. Is there a way to review changes to the content before it gets public, without hiding the old content till the changes get reviewed?
Unfortunately no there isn't when a post is created as any other status except Published it won't be available on the frontend.So if you create a form that when you update the post it changes the status as Draft then the post won't be available on the frontend.
3. Is there a maps function to enter a Zip code and to show entries nearby?
Unless the post itself has a field on it that contains the zip code then you won't be able to filter by the zip code. My advice is to create a field and then allow the users to enter the zip code whenever they are creating the post. This way you can use it on the frontend to filter by.
