requinix

Requests containing responses is common. Responses containing requests is probably not that common. Neither containing the other is also an option. I'd go for either the first or the last of those.

I can't decipher what you said. I already know the requests are not correct. My question was to prompt you to see how they were wrong, then trace that back through the code to find out where they were wrong. Have you done that?

Watch the AJAX requests in your browser. Are they all correct?

Why is there a redirect? If you want both sites on the same server that's totally fine, but why would there be any redirections for it?

My guess is that you're entering duplicate data. Something conflicting with the primary key, or a unique index.

GROUP_CONCAT

Looking good so far. What kind of problems are you having with it?

Don't expose dl.x.com to the internet. Store your files there if you wish but proxy everything through x.com. Will it harm your server to reduce the attack surface? I don't think so, no.

Do a View Source of your page, and find the line where you outputted $results. Does the Javascript look correct?

Do not use the session to pass data between specific pages. Use the query string and $_GET. The session may look appealing but it has a number of drawbacks, such as being unable to view the same page with two different sets of data, and users being unable to copy or share URLs to a page.

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'm partial to x = 1 - x. Are you sure you need a cronjob for this? Very many "I need a cronjob to do X" problems can be resolved in a way that doesn't need a cronjob...

Post your code and we'll tell you what's wrong with it.

Did you see the part of mac_gyver's post about having the button submit a unique ID from your database?

Stop supposing and actually find the answer. It's documented very clearly if you look for it. Yes, Bootstrap v3 and v4 define the sizes differently. Because apparently nobody over there has any idea what "backwards compatibility" is.

You're expecting way, way too much from it. PHP isn't a human being. It can't look at all your code at once and understand how every little thing is connected. It definitely won't be able to know that a particular button that you outputted is related to some particular code, let alone what the code was doing at a very specific moment while it was running. If you want things to work a certain way then you must be absolutely explicit about it every step of the way. Want a button to correspond to a certain row? Make sure that the button itself includes some value from the row, then write code that takes the value and looks up the row data. Then think about what you've done and ask yourself whether you've told PHP to do exactly what you wanted to happen.

$_SESSION["Title"] = $row['Title']; $_SESSION["PerfDate"] = $row['PerfDate']; $_SESSION["PerfTime"] = $row['PerfTime']; How do you expect this to work when you are dealing with multiple rows? What do you think it will do?

Where did you get those numbers? From the Bootstrap v3 documentation?

How about my second question? Did you find an answer to that?

PHP can do a lot of very different things so there isn't just one particular place you could start. My advice is to think of a small project you'd like to make for yourself and start working on it. Break it down into small tasks you can accomplish one at a time, and check with PHP: The Right Way if you're not sure how to do something.

A basic understanding of what glob() is and how it works. The kind of understanding one should be able to pick up by reading the documentation for a few seconds.

Not everything has to go through dependency injection. It's okay to hardcode some class names. You can always refactor later. If, on the other hand, you know right now that you want to inject those SomeOtherClass instances, pass the container to your constructor and configure the container to create them. Regarding not creating things in a constructor, that's not quite right. What's not necessarily good is creating dependencies in the class. Which is sometimes a nebulous term - see also my first sentence.

How wide is your display? What are the thresholds for what Bootstrap considers to be sm and md?

Use notifications.

That all sounds very consistent with the "putting code which creates the array into an include file" strategy.