I am wanting to add some fields to the registration page, so I thought I'd write a plugin for it.
It looks like the process would be:
Add a 'filter:register.build' hook function to insert the html for the extra form inputs.
Add a 'filter:user.custom_fields' function to insert the key/value to the userData object.
I looked at the spam-be-gone plugin to get an understanding of how to go about it, but my question is: Is it possible to place my added field(s) at the top of the form -- or anywhere else -- rather than the bottom?
I can also do this by adding my additional html into the register.tpl file and then adding the key/value to the userData object in /src/user/create.js, but I'd rather do it via a plugin as it seems cleaner. I don't need the data to appear on the site (i.e. the user's profile) so just these two things work fine.
The problem is I believe I'd have to do a 'git pull --rebase' each time I wanted to get updates for nodebb which could break things over time. Seems hacky. Plus, it is more maintainable to keep my modifications modular.
So, is there a better way? What's the best way to go about doing something like this? I'm just assuming that doing it via a plugin would be ideal, but if there are better options that are clean, then please let me know.
Lastly, if I wanted to have a function run a check on this info for duplicates during the registration (exactly like the one for username) can you steer me in the right direction on how I'd go about it?
when will the appropiate hook be to be able to parse the recipe and arrange and pretty it to show it to the users?
The hook you want is probably plugins.fireHook('filter:post.save', postData, next);. This is called right before the post is saved into the database.
How are posts saved? in raw text? is the text parsed with Marked when each post loads?
Yes the raw text is saved into the database and parsed on the way out.
The easiest way for this to work would be to listen to that hook and find the file links in the postData.content they will be in the form [link text](link url). You can grab link url, make sure it exists and read it and then append it to the postData.content in your plugin.