artdyke

Yeah, they're a little wonky in places, but I know a lot of people that use them and they have a flawless reputation. I'm about to switch to GET and see if I can figure that one out. Security's not really an issue since I only have to validate username/email on my end. Otherwise I'll do the hidden form method. I was just hoping there was a slightly more elegant solution out there.

It's Zombaio, who we must use for a number of reasons. I assume they do their own validation on their side, but it needs to match up with my database on my side, hence the need for validation on my side. What I really need to know is if there is a way to make cURL behave just like a regular POST form, redirect and all. I've found several threads around with questions along these lines but they've never been answered once it gets down to the basic question of how to redirect the user along with the POST data. Is this not possible?

Looking at the above links from mjdamato, are there any advantages/disadvantages to the cURL method vs. the HTTP POST method described?

Yes, it takes you to the 3rd party site to go through several steps.

So I'm launching a paysite soon and we're using a 3rd party payment processor. However, said 3rd party is more geared towards maintaining htaccess username/password lists rather than working with a database. After running some tests, I found that the 3rd party isn't running any kind of validation to check if the user already exists and I'm able to sign up with duplicate emails/usernames. So I need to do some validation myself. I'm used to keeping the form, validation, and processing all in the same file. How can I do the form/validation on my side and then send the POST stuff to the final processing file once it's validated? It seems like I would need two "action" destinations... my own validation one and then if that clears, on to the 3rd party one. How do I do that? This seems like it would be easy but I haven't been able to figure it out...

- You should let the text on the left wrap instead of using <br />. It breaks in weird places instead of looking like it "fits". - I'd add the site name to the titles i.e. "Mike Hiscott - Home" instead of just "Home". - Love the header

Hi, I'm relatively new to programming in general. PHP is the first language I've learned. I'm not trying to make a career of this or anything. I'm designing a browser game with my wife, but it's more for fun and the game design/art design experience (something I do plan on making a career of eventually). Sorry if this is too much background, but I'm trying to give you an idea of where I'm coming from with this question. So I'm on the brink of really getting into moving from the design phase into the heavy programming phase and I'm trying to decide how best to approach everything before I spend forever working on it. I've heard a lot of hype about OOP, and I've got the very basic basics down, but honestly, I don't really see the advantage of it when I'm gonna be the only one working on this. It seems like far more trouble than it's worth. And then I thought, 'Well I'll just try it anyway because everybody swears it's the best way to go,' but I've found that it's a lot more awkward for me to deal with - either I'm not getting something or my brain just doesn't work that way. Can't I achieve the same reusability and modularity by using includes/requires? Why is OOP really better, functionally speaking? Because these abstract notions of why it's better theoretically don't seem to apply to how I operate...