No. I will. not do that (upgrade to vB4)
I already commented out the offending lines yesterday.
My question is basically fixing this for vB 3.8 otherwise, I’ll just fix it myself. I reported, in this post, a ‘bug’ about code and if I cannot get a bug fix in code reply, I’ll just code the fix myself.
That is why I posted the bug here :). It is a bug report about code. The code has a bug and so I reported it…
Hmmm. I was attempting to be sociable and post the bug here and hopefully, get suggestions from the leaders (code) that work for me in my case (not the vB4 case); and sorry again, but am not going to upgrade to vB4 under any condition. Sorry to be so direct and for not following thatidea. I will mod the migration script as necessary and mod our DB as required.. So far, I’ll already added code for custom code tags, etc.
Cheers.