requinix

Could be to "host" your content on their site so that they get traffic. Could be to try to increase their own legitimacy. Bots harvesting content for their own websites to drive more traffic to them and increase their ad revenue. Google does a decent job of distinguishing actual sites from spam sites. Likely either malicious probes or bots trying to spam you. There are tools to identify traffic patterns and react accordingly. fail2ban is one of the most popular and is primarily used to throttle IPs sending too many requests. Everything they do boils down to increasing advertising revenue. Keywords. If your reputable site has particular keyword content (even from comments) then it begins to establish a correlation between your actual content and their keywords. It's a long con. There isn't a whole lot of sabotage like that out there. It's mostly about associating spam sites/content with legitimate sites/content, thus suggesting a relevance to their content. If your site covers subject matter A, B, and C, and comments on your site also suggest spammy subject matters X, Y, and Z, then it suggest people interested in the former may also appear to be interested in the latter.

Next time try StackOverflow. They don't mind giving you the right answers to the wrong questions.

A "sudo user" doesn't make sense. sudo is a tool that lets you run commands as another user - typically root. Forget for a moment what you are trying to do. Why are you trying to do it? What is fiddling with permissions supposed to solve?

You did inherit the privileges of the www-data group. But the permissions you applied to allow writing are not for the www-data group. They are for the owner of the directory, and in this case the owner of the directory is www-data the user. There is a user named "www-data" and there is a user group named "www-data". They are two separate (but related) things.

What if you try running that query manually? Exactly as it is, copy and paste.

That's right: owner can write, everybody else cannot. www-data is the owner. Are you www-data?

Is STOREITEMS the root node? Then each $items will be a single PRODUCT...

Can you tell me what the permissions 755 mean?

The "best websites" aren't on the first page because they follow the standard rules of SEO. It's because they're popular. They're long past the first date so they don't have to wear fancy suits and nice dresses anymore. You do not know better than the experts. Get vaccinations, wear a mask, and follow good SEO principles.

Next time, please let people know you figured out that json_decode was the answer.

Okay... Does the debugger itself crash? Or does PHP crash and the debugger handles it gracefully? Hopefully PHP. Try this. Set a breakpoint on the line where it crashes and run the debugger. When it stops, grab the PID of PHP and hook into it with gdb. Then continue running and see if gdb can catch the problem. Then get a backtrace.

I don't know enough about the WP images to tell. I don't see anything OS-specific in there. Check /etc for any "release" files.

Checkboxes are for multiple selections. If you do not want multiple selections then do not use checkboxes. Use radio buttons instead. So I'll make a minor change to my first question and repeat it here: do you know what the HTML markup is for radio buttons? When you have that, all you have to do is drop the <select> tags and replace each <option> with a radio button. (And then probably a little more markup or styling to make the radio buttons appear the way you want.)

What? Screenshot? Check your browser's Javascript console for errors.

Do you have any watches or conditions set up with the debugger? Exactly when/where does it segfault?

Browsers do not decide to rotate images for no reason, but they may decide to not rotate an image. If you see an image rotated in one place and not another then that's because of what I said earlier: Can you upload here one of the problematic images?

If you don't ask a precise question then you might not get a precise answer. Do you know exactly which WordPress image you're using? What OS is it based on? Debian does have a "php-yaml" package so if you use that one then you can probably set up your own Dockerfile that FROMs the base WordPress image and apt-installs the php-yaml package.

I don't see instructions for doing it within Docker already written for you. Do you understand how Docker images work? What Dockerfiles do? It would not be hard to take the regular installation instructions and port them to a Docker environment.

Do you know what the HTML markup is for checkboxes? Your drop down does not support multiple selections right now. Checkboxes do support multiple selections. Do you want that, and if so are you working on changing your PHP code to support that?

FastCGI and php-fpm are not the same thing. If you don't want php-fpm to log then configure php-fpm to not log.

No offense, but there are tons of PHP + AJAX tutorials out there. Have you tried reading a few articles or watching whatever YouTube videos are out there? For the most part, all you have to do is write a bit of Javascript to send the data and receive the response (and do whatever else you would otherwise do). The PHP side is less complicated than your standard page because you output straight data (using JSON) instead of some complicated webpage. If you can write a PHP script that takes the form data then you're most of the way there. And it sounds like you already have that piece.

Every time I see WordPress code I have to take a shower to wash all the disgusting off me. The easiest way to accomplish what you want is to not do that. If you want the member ID to look like four letters from the last name (what if their last name is less than that?) and the number then show the last four letters and the number. Make a function or class or whatever that can take a member and their ID and give you the string you want. But here's the thing. You cannot use that last four + ID as a real identifier. It will cause lots of problems. You can show it to people but under the hood you should always deal with just the member ID.

yaml_parse_file is documented in the online PHP Manual. It is part of the PECL yaml extension. There are instructions.

Always record data. A payment failing counts as data. What. I think part of my problem with this thread is that I don't even understand why you would consider this idea. Sign the user up. That's a separate step. Store the order data. That's a separate step. Take the payment information. That's a separate step. Attempt to process the payment information. That's a separate step. There is no reason why one of those steps resulting in a problem should somehow undo what happened before it. Even if you went for step #2 (which, to reiterate, is wrong), there's nothing incomplete here. A user is a user. Doesn't matter whether they have an order, let alone have successfully paid for an order. These are two completely different concepts. And the order has every reason to exist even if the payment didn't go through - again, always record data. If the disadvantages outweigh the advantages when why would Amazon do it? It's not your fault the payment failed. (Probably.) You have no control over that. If it fails and the user aborts the order then sucks to be them. You cannot store order data for an anonymous user. It's not good. The user must exist so that you can associate the order to it. That's fundamental ecommerce there. That's right. You have to do that. I'd say "you have to do that" but you already have: it's called "anonymous people don't have access to the paid portion of the site". The only difference now is that you need to tighten your restrictions to allow users who have also paid (or have an active subscription or whatever). Bad analogy. They don't let you do that because there's a high risk you'll sneak off to a screening while the staff aren't looking. Which totally does not translate to an ecommerce website. I cannot come up with a polite response to this one. Do whatever you want. I'm out.

Have you checked the documentation to see what else odbc_exec might be returning?