HFS, RAWR-Template, RAWR-Player, and an Email form Bounty

[rejetto]

ok, i fixed this bug for next build.
now i'm going to work on another problem: by testing i saw that this way of accessing [sections] by using the /~tilde in the URL, doesn't apply to diff templates. it's limited to the main template.
i hope to get over this problem without affecting performances.

[rejetto]

ok, i think i solved.
let's see if next build runs smoothly.

[ajpaterson]

Hi Rejetto,

I tried the new build (232) with both the original code and new code you provided as home/root diff template and diff template doesn't appear to be working for me at all now.  The shoutbox remains original.

[rejetto]

it's normal.
that code was not meant to automatically replace the shoutbox.
it is generic and will work with any template.

i made some adjustments to fit your needs: replace file
template\rawr_default\shoutbox\display_posts\hfs.diff.tpl
with the attached one

this should be enough.
and you can also remove the text you pasted in the diff template.

[ajpaterson]

i made some adjustments to fit your needs: replace file
template\rawr_default\shoutbox\display_posts\hfs.diff.tpl
with the attached one

this should be enough.
and you can also remove the text you pasted in the diff template.

I replaced the hfs.diff.tpl file and reloaded the page and bam, there was the new form in the place of the shoutbox!  I've just received my first email from the system entitled, messaging from hfs.  Unfortunately the contents of the message was missing.  I'm going to take a look at the diff file to see if I can figure that part out myself.

[rejetto]

i updated the attached file above, to make the output message nicer.

anyway, i just tested and got the content as well.
if it doesn't work on your side, maybe it's because there's a problem saving the temporary file that stores the content.

it's this line
{.set|tf|email.temp.txt.}
where tf stands for temporary file, the rest is the name

[ajpaterson]

i updated the attached file above, to make the output message nicer.

anyway, i just tested and got the content as well.
if it doesn't work on your side, maybe it's because there's a problem saving the temporary file that stores the content.

it's this line
{.set|tf|email.temp.txt.}
where tf stands for temporary file, the rest is the name

I tried this at home and you are correct, it is including the body.  It must be a temporary file or permissions issue on my server. I'll try it out and report back.

-Anthony

[ajpaterson]

Well it appears that bmail and my isp's mail server don't get along. 

Mail sent to my personal account is fine, but mail sent to my work account has the body stripped.

In any case, I will probably change direction with this a little as this form is too small to send a useful message, and I may simply set up mail to: buttons to cover several potential recipients.  Thanks Rejetto for putting so much time into this, fixing a bug, and showing me the way.  I'll be sending the additional donation tonight.

Regards,
-Anthony

[TSG]

mailto: links will be a problem with spam if its a public server. Better to use a form with a captcha or login, OR you could only show the mailto: to logged in users, that should stop the spam.

[rejetto]

thanks Anthony for keeping faith.
these years i've spent more time giving support than developing HFS, and being rewarded sometimes is nice.

having a simple link to a bigger form was my first idea, and it's the original version of the code.
you just need to link /~contactus and put the code in the diff template.

Mail sent to my personal account is fine, but mail sent to my work account has the body stripped.

if this is very important, i know a way that may possibly workaround it.
let me know and i'll tell you more.

[rejetto]

mailto: links will be a problem with spam if its a public server. Better to use a form with a captcha or login, OR you could only show the mailto: to logged in users, that should stop the spam.

he doesn't want links.
about the captcha, i came to an idea. javascript idea.
when the user click "send", i can just change the button in "press another time".
and just then you'll be truly sending.
we'll probably may get a better "text" for the buttons, or we may like to create a second button just after the first is pressed.
but the point is that this may stop the bots.

the bots, actually, can force the submit without pressing the button. but i may wait for a certain value that is created only when you click the second button. without this special value the submitting can be simply ignored.