requinix

1. Yes, if the fancy UI is important to you. 2. As with any other user authentication system, yes.

Bots. Use a CAPTCHA.

Do you have the rest of it built out? Because if not then I would suggest using one of the millions of existing services to do this. But an .htaccess with a username and password is a really quick way to do this. They go to the site, the browser pops up a little window asking for a username and password, they enter it, and they get in. And the browser can remember it like the login for any other website.

The so-called "PHP error" only means that when the browser tried to send the login data to process.php the server responded with some sort of error. Could be so, so many different things going wrong, only some of which are to do with PHP. There's not much you can do unless you can reproduce the problem yourself, or find something in your PHP or server error log.

The version of phpDoc you have needs PHP 7.2. If you are using an official Docker image from phpDoc then they did something wrong. If you are using a Docker image you created yourself then you need to create a new one that has PHP 7.2 and then add phpDoc to it.

Then don't put the files into subdirectories. What I'm trying to understand is why you want everything to look and act a certain way but weren't making it actually be that way.

This isn't good. Why do you have so many subdirectories? Why are you not using the correct URL?

Also confirm that there are, in fact, 1000 characters in there.

Because you cannot customize the "required" validation warning that the browser gives the user. Or "pattern", which is going to tell the user something cryptic they won't possibly understand.

Then your browser doesn't support replaceState or it doesn't implement it correctly.

If the file was uploaded in 2016 then I doubt you're running a current version of WordPress.

Don't print both? Seriously, you've given me a tiny bit of code way out of context. I can't do much with that. If you want to do some basic validation with just Javascript then that's fine, but if it fails validation you don't then submit that to the server.

Still here. Still don't have anything to add other than you need a Docker container with PHP version 7.2.

No. Validating on the user's computer means telling it what to do and hoping that it happens. You must validate on the server, and you may validate on the client too. That sounds like a good reason to not only do validation on the client. Because your code and/or design is flawed. Handle it in whatever way you want as long as it works the way you need it to work.

What I was originally thinking turned out to not be possible (I was thinking of two concurrent iterators), so my answer is basically "whatever works" now. So, as long as you're not approaching your memory limit, I would stick all the string blobs from cURL into an array or ArrayObject, wait until cURL completes, then give that to JsonMachine. That's almost what you're doing now, except you're doing string concatenation and that can potentially hurt performance by a lot because every time you append a string PHP has to reallocate a new one in memory to hold everything and then copy the old value into it. An array/ArrayObject uses slightly more memory because of the overhead but doesn't come with the costly memory management.

cURL doesn't expose its streams. JsonMachine accepts an iterator. Use CURLOPT_WRITEFUNCTION to receive some number of bytes from cURL, feed that into an iterator, and give the iterator to JsonMachine.

I don't know. Can you?

(coughitdoesnt)

Undefined variable? Which variable? Is it $brand?

<input type="checkbox" name="checkboxes[]" value="whatever you want">

Correction: some upload to a server-side script that then places the file in a destination folder, and some upload to a server-side script that then places the file into a database. If you only have one server then store in a folder. It's just easier to work with. If you have multiple servers and a shared storage space then I personally would still store as a file, and if not then use the database.

I'm sorry but as a policy we do not delete accounts or posts, with obvious exceptions like for spammers, and when required to by law (ie, for EU residents). If you're concerned about personal information, all we have is what you've provided - and it appears you haven't provided anything. We don't mind if you just, you know, not use your account.

I've used jq when dealing with JSON files from the command line, yes. Relatively simple.

One option is to dump the response to a temporary file and use something like jq (which I think operates on a stream, not a full document) to extract pieces of the JSON.

Get a Docker container that has PHP 7.2.