Hi,
Twenty minutes composing a reply to you and the idiot browser crashed and threw it all away! :mad:
Printable View
Hi,
Twenty minutes composing a reply to you and the idiot browser crashed and threw it all away! :mad:
Yea I have all ready learned those issues the hard way. I am sitting here doing the same. Except in a .txt doc. I hate when that happens...
Anyway since you opened up that can of worms. Do you have vBulletin set to log everyone out after tens minutes? It might be less time than that... but it's going to drive me insane lol.
Email on the way man just a few more things to get sorted.
Hi,
It's set to keep you logged in unless you log out.Quote:
Anyway since you opened up that can of worms. Do you have vBulletin set to log everyone out after tens minutes?
So, I guess you must have a cookie issue with your browser.
I'm always logged in forever.
The following error occurred in FormMail :
fmcompute_exec
**********
Error=The following error messages were reported from the FMCompute module: Statement 6 on line 19, position 1, failed runtime expression evaluation: Invalid action 180. If one operand is a string, they both must be.
I got this one... a few little ' is all it needed.
Hi,
Yes, the parser and runtime system for the computations check for most errors.
Glad you found it.
Hi Russell,
Can I change the fmcompute file name?
Say logic.php and then logic1 for the hidden field.
Can it be "cloned" to another name thru out the setup?
Can all the other file names.php be changed as well?
I would just like it to flow better and make more since in my setup.
I do like the names you have chosen to convey what they do.
But I want to clone them...
Hi,
You can change the name of the fmcompute.php file in FormMail's configuration section:
As for changing the field names, you can only do that by changing the coding of FormMail. And then you'll have to re-do those changes when you upgrade.PHP Code:$FMCOMPUTE = "fmcompute.php";
It's not recommended.
I guess you want to do this for "security" reasons. However, I think I mentioned in a previous post that you should write down your threat model first.
You can think you're achieving "security" when all you're really doing is wasting your time.
So, start with a threat model (what are you worried about) and then develop solutions for that.
I have been working on my plan. I am not really worried about threats. I just want to hide what I am using to make the forms work.
So if someone see the fields in my form then searches google for them. lol They wont end up here.
I know you want people to find your site. I just don't want anyone "meaning my competition" to understand how I am building my forms with one google search.
I certainly hope that, that does not offend you in anyway. My post is not meant to offend just to understand how I can achieve my goals for my project.
Hi,
OK, why? (I think you've answered this below.)Quote:
Originally Posted by billy
Sounds like a security concern you have (also known as a "threat").
Search engines don't look in hidden fields. It makes no sense for them to do so.Quote:
In fact, they don't look inside the value of any fields in a form (non-hidden fields typically have no value anyway).
So, that won't happen.
The search you've mentioned is finding the contents of files people have linked to on their website.
They've done silly things like tell search engines to look inside a language pack.
Completely harmless, but silly.
If you actually look at the results, there are no "fmcompute" field values shown.
Sounds like a security threat you're worried about.Quote:
I know you want people to find your site. I just don't want anyone "meaning my competition" to understand how I am building my forms with one google search.
So, be specific: write down a scenario that you want to prevent from happening.
Then, I can advise the best course of action to avoid that scenario.
You've just mentioned one, and I hope I've explained that it's not an issue.
No offense taken in any way. :)Quote:
I certainly hope that, that does not offend you in anyway. My post is not meant to offend just to understand how I can achieve my goals for my project.