Please post issues with modifications in the modification's thread/site/board from which you downloaded it. This way it alerts the author that they need to fix their modification, posting here will serve very little purpose.

I hope I am not going blind already at my young age. :(

Could someone pm me the link to the forum if possible?

Is there a way to access this information without being a vb.org coder?

Find the post forms in the template system and you will find your answer or you can always look in the init.php file. The answer can be found in either. I am not going to say it because I can be wrong.

Thanks, it seemed like it wasn't too difficult judging by the FORM code, but I wanted to make sure, I'll try it out.

never mind me.

Which, as people keep pointing out, is of little use if you have made your own modifications, as we are often quite sarcastically told to go off and learn how to do.

Quite what the logic is of keeping this apparently simple fix for the eyes of the elite only is beyond me.

Perhaps every time I see someone having a problem with a modification which I can fix, I should refuse to post the solution on the same basis. This site used to be about helping each other, not a select elite.

Technical explanation on hwo to incorporate CSRF Protection into custom scripts has now been posted as an article also: Implementing CSRF Protection in modifcations

Was rather looking forward to a gold release this weekend but glad that some bugs were fixed anyway.

Can someone please tell me if the security problem announced is affecting vB 3.0.xx?

I know, ancient, but I do not plan to upgrade until absolutely essential and so far, I haven't find a good reason to do so.

Many thanks.