Hi,
I replied by email a few days...have you found the cause of the problem?
Welcome to the Tectite Forums! You can download and get support for our free PHP FormMail (form processor) and other free software.
Hi - I've just started seeing this from a form that has been live for a couple of years on a server that has seen no significant changes other than standard system upgrades, etc.
I am able to run fmencoder manually from the command line:
I was wondering what status 135 meant and what we can do to get the encoder working again.Code:# ./fmencoder -k pubkey.txt test encoder manual . FormMail Encoder/Decoder Version: 1.6 Available from www.tectite.com ID:mysecretkey *7829DBwajvco5fRs+Q.... <snip>
Hi,
I replied by email a few days...have you found the cause of the problem?
Russell Robinson - Author of Tectite FormMail and FormMailDecoder
http://www.tectite.com/
Eventually managed to work it out.
I upgraded formmail to latest version here: http://www.tectite.com/wizards/fmupg.php
Then checking $FILTERS variable I noticed that encode was being called from ~/public_html/cgi-bin/ when in fact I was expecting it to be in another location. It was working fine for a couple of years set up like that.
Correcting the $FILTERS['encode'] variable has got it all working again for me now.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks