requinix

<?php if($gst="OUT"){ <input name="noopaxs" id="noopaxs" readonly = "" value="<?php echo $row['noopaxs'];?>"> else{ <input name="noopaxs" id="noopaxs" value="<?php echo $row['noopaxs'];?>"> }} ?> Couple issues in there: 1. One = means assignment. Two == means comparison. Make sure you use the correct one. 2. You cannot put HTML directly into PHP. If you want to write HTML like you did above then you have to first leave PHP mode with a ?> and then, when you're done, go back into PHP more with a <?php. Like how those two echos look: the <?php switched from HTML to PHP mode, then the ?> switched from PHP to HTML mode.

How familiar are you with PHP?

Did you remove the @s? Next step is to modify your code so that you can know whether each mail() was successful: by checking the return value. If either call returns false then the mail will not get sent.

What article? Because if that's what it says then you should stop reading it. Do you think the browser is doing that? Saying "oh, this textbox is disabled, I shouldn't update the database", or "oh, this textbox is readonly, so if the user changes it then I need to update the database"? It isn't. Which is why what the article says is technically wrong. And it's wrong in a way that is important for you to understand. You know how to check a condition. You know how to mark a textbox as disabled. Combine the two. If you have problems making that work then post what you've tried.

Remove the @s. That hides errors. If there are errors you need to know about them. Was the email marked as spam/junk?

"Sold"? I don't know what snake oil GoDaddy is trying to sell you, but DKIM is completely free, and as long as you control DNS for your domain (which you have to for SPF) and the emailing code (which you do) then you can set it all up yourself. It's also industry-standard. So if you want to do SPF only, have a single email go through, and then think you've solved the problem, then be my guest. It's not my emails going through the spam filters.

Okay, I'll back up a bit. Emails should always be From: someone that you can (properly) claim is you. Obviously you're not @gmail.com so don't have your emails claim to be. That's almost definitely going to be the reason Gmail thinks your emails are spam: because you're not just lying about who you are, you're pretending to be them. Their secureserver.net thing, admittedly not the greatest. If the emails have to be From: someone you can claim to be, that would be whatever your domain is. So the sender email should be something (such as no-reply) @your domain. But Gmail is going to look at the email and say "hey wait a minute, the email says it's from @your domain but it's actually from secureserver.net" and consider marking it as spam. The solution to that is SPF and DKIM: you don't try to trick Gmail, you tell it that secureserver.net is okay to be sending emails for your domain.

Emails should always be From: your server. Always. If you want people to Reply-To something else then that's what you do.

You haven't posted what your original code was... or maybe, what the new code is? Not sure. Either way, I don't know what you changed. But using variables or moving them around is not going to change anything. Gmail doesn't care about your PHP code. It only cares about the email it received.

Don't do that. I mean, WTF? No. Just, no.

The email claims to be from a @gmail.com account. Are you actually doing that? Because I don't think you're actually doing that. And lol to the recruiter spam label.

Do you know how to mark a textbox as disabled?

Using PHPMailer doesn't mean your emails will get through. It means you won't have many of the problems that manually-crafted emails do and that spam filters know to recognize. Set up SPF and DKIM if you haven't already. Have your emails follow standard industry practices regarding things like unsubscribe links. Use proper spelling and grammar. What warning?

"Better" is debatable. You don't need a new file. Just rearrange the code so you do the work (form processing and all that) before the output.

money_format() was a very simple thing. One of the reasons why it was deprecated. The Intl stuff is quite a bit more sophisticated, and being a different thing it also works differently. Most of them work by you setting up a "formatter" with whatever settings, then using that formatter to get what you want. Hypothetically you could set up that formatter at the beginning of your script and settings from your database or the user and then share it around so that all your code could use it - would save you from having to set it up over and over again.

I don't see what the difference between the second example and your working version is - besides changing the locale string and currency ID. You had something that didn't work - what did you change so that it did work?

Can we assume that within those next three years you'll learn how to "do programming"?

Don't have that capability. Besides, half of preventing editing is about stopping spammers who make posts that look fine, wait, then edit in spammy keywords and links.

Don't hijack other people's threads for your own question. TextWithRotation looks like it comes from an FPDF "extension". Did you "install" the code for it? Did you notice that you have to create an instance of RPDF and not FPDF?

Are you using Javascript to submit the form? What's the code for that? Does it blindly look for a form on the page? Or is it smart and look for the form that contains the button that was clicked? You could probably skip all that Javascript stuff if you used a regular form submit button.

Does quite a bit more than just WebM and MP4. The script is broken down into a number of different scripts. Some of them are dedicated to converting to a particular format. If you don't want that format (at least not yet) then comment out the whole step.

Text Fragments As is usual for the web client industry, one browser (Chromium, so Edge gets it too) decided to implement this capability without it being an actual standard yet. It looks funky, but Google wants it so we're probably going to get it.

I expect they were making their best effort to prove somebody else wrong in order to make themselves look better. You know. StackOverflow. JSON is fine.

There is a syntax error in your code. Download and install an IDE or editor that supports PHP code. Put your code in there. You should be able to see the mistake very quickly.

Look at how your script uses the $dob variable.