Jump to content

spacemonkey

New Members
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

spacemonkey's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. The form now appears to be working properly, again. I think there must have been a short delay while the changes propagated to all the server cluster members. Many thanks again for all your assistance and patience.
  2. Update: The php.ini file has been updated and applied. The host provider has said the change would take effect immediately, but the issue persists. It may well be because the Apache server has not been restarted - understandable as this would affect other users. I've run a pnpinfo() check to make sure that register_globals is now set to off. Would anyone happen to know if there is a way to check when the Apache server was last restarted? Thanks again for your patience.
  3. Thank you both, Jessica and Pikachu2000, for your help. I will have to ask my provider when the server can be restarted. Happy New Year to you all and many thanks again.
  4. Hi guys, Thank you for your input, Pikachu2000. I've updated the PHP.ini file accordingly. Hmm, thanks for the heads up about my poor coding. I've just checked the PHP online manual, but it does not appear to help me when I am trying to assign the posted data to a variable. Could you direct me to some other reference that better clarifies how I should be coding the $POST information? Thanks again.
  5. I am hoping someone might be able to help to resolve an issue that has arisen recently with a number of websites I administer relating to contact form submission. Host server version configuration: Apache - 2 (When I check the headers using Firebug I just get: Server Nginx / Varnish) MySQL - 5.0.91-log Perl - 5.8.8 PHP - 5.3.13 The named data is being retrieved via a process.php file as follows: $subject .= $_POST['subject']; $title .= $_POST['title']; $forename .= $_POST['first_name']; $surname .= $_POST['last_name']; $phone .= $_POST['telephone']; $mobile .= $_POST['mobile']; $email .= $_POST['email']; $message .= $_POST['message']; $name .= $_POST['first_name'] . " " . $_POST['last_name']; Until about a month ago all the contact forms were working correctly, but now whenever a user attempts to submit data via any of the contact forms the form produces the following error. (The subject pulldown menu dictates the delivery destination of the form contact message): Any data entered into any of the form fields ends up being duplicated - e.g.: My SubjectMy Subject instead of My Subject If I change the PHP code to accept My SubjectMy Subject instead of My Subject the form will submit but the data in the sent message is garbage - see below: Message Subject: My SubjectMy Subject Title: Mrs.Mrs. First Name: SS Last Name: OtherOther Telephone No.: 0789012345607890123456 Mobile No.: 0789012345607890123456 Message: A message exampleA message example Email: an.other@whatdoneit.coman.other@whatdoneit.com I've tried researching the issue without any success so far. The following threads appear to indicate this is a bug: http://stackoverflow.com/questions/13574369/php-post-variable-has-duplicate-munged-data http://www.actionscript.org/forums/showthread.php3?t=210801 http://www.plantware.net/questions/13574369/php-post-variable-has-duplicate-munged-data I've tried adding a dummy name/value pair by adding the following additional code into the contact form after the message field and before the re-captcha box: <input type="hidden" name="splitter" value="1" /> but that did not work. (I may not have implemented that fix correctly, however.) Any assistance would be greatly appreciated. Thanks
  6. I am hoping someone might be able to help to resolve an issue that has arisen recently with a number of websites I administer relating to contact form submission. Host server version configuration: Apache - MySQL - 5.0.91-log Perl - 5.8.8 PHP - 5.3.13 Until about a month ago all the contact forms were working correctly, but now whenever a user attempts to submit data via any of the contact forms the form produces the following error. (The subject pulldown menu dictates the delivery destination of the form contact message): Any data entered into any of the form fields ends up being duplicated - e.g.: My SubjectMy Subject instead of My Subject If I change the PHP code to accept My SubjectMy Subject instead of My Subject the form will submit but the data in the sent message is garbage - see below: Message Subject: Mrs.Mrs. Title: Mrs.Mrs. First Name: SS Last Name: OtherOther Telephone No.: 0789012345607890123456 Mobile No.: 0789012345607890123456 Message: A message exampleA message example Email: an.other@whatdoneit.coman.other@whatdoneit.com
  7. I am trying to pass the contents of a user completed text field in FileMaker Pro 9 (- the FileMaker database is being served from Macosx 10.5.5 as is the PHP server (- same machine)) the (using Open URL script step) to a variable in the receiving send_message.php file. The text is transmitted and received, however, the user generated text includes 'smart quotes' (“ and ”) and consequently appear as “ and †respectively (-note the hidden character after the †for the ”). I have tried using the following code to no avail: $oldmsgString = "“"; $newmsgString = "\""; $test_message = stripslashes($_GET['message']); $new_message = str_replace($oldmsgString, $newmsgString, $test_message); Interestingly when I pasted the code directly from the send_message.php file into this post it appeared as: $oldmsgString = "‚Äú"; $newmsgString = "\""; $test_message = stripslashes($_GET['message']); $new_message = str_replace($oldmsgString, $newmsgString, $test_message); n.B. the content of the $oldmsgString. It would appear to be an issue to do with the text encoding in FileMaker and PHP but I have no idea how to resolve this. Is there a way I can convert the text received from the FileMaker text encoding to that expected by PHP? Any help would be appreciated.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.