requinix

I like answering with questions because often that encourages the person, in trying to answer that question, to start heading down the right mental pathway towards finding the answer - if not find the answer itself. Here, the answer to my question is something like "well the setting page says it's a path to PHP". Logically, then, if it's "the path to a PHP executable" then yeah, the answer probably is as simple as copying the php.validate.executablePath you have above it. Because the thing to remember here - and this might help dispel some confusion - is that despite the similarity between the two configuration names, they belong to two different extensions: the "php.validate.executablePath" is used by the built-in PHP extension while the "php.debug.executablePath" comes from PHP Debug.

I don't understand why this is a question. Do you know what that setting is for?

There's whitespace around the URLs. <loc> http://enginery.freecluster.eu/index.php </loc> It's a minor thing but could be a problem.

Maybe content "with media"? Or maybe "supporting uploads", because you'd need to do that for images to be possible. But there aren't really any special words. Because supporting images and deleting posts/articles and such are simply the normal features you'd find in most CMSes. Not especially. There are definitely special terms for many different things, like I mentioned "roles" earlier, but that doesn't mean everything has special terms. Like "allowing users to register accounts" isn't a term. It's a description. And "inserting images and videos into posts" is also a description.

These are very broad questions that do not have a single answer. What you can do varies a lot. The word you need is "role", as in a user login system where each user can have a different role (ie, user role or admin role). That just sounds like a CMS. Use PHPMailer or Swift Mailer to send the emails. You configure them with your email server information, like if you want to use a Gmail account, and they do the rest of the work.

Finding out the actual truth instead of guessing is probably a good idea. For Apache, SSL_PROTOCOL is available if you enable that. https://httpd.apache.org/docs/current/mod/mod_ssl.html For nginx, I believe you can get $ssl_protocol as a variable, but you would need to pass that as an environment/CGI variable to php-fpm in the server/site config. https://nginx.org/en/docs/http/ngx_http_ssl_module.html

So let's take a step back. Are you using Apache or nginx? mod_php or FPM? What is the server setup?

An optional parameter would be like public static function render($post, $withPost = true) { which will default to true if not provided. You would then use $withPost to decide whether to do that ->push or not.

Because it's apples and oranges. Just running on the same server doesn't mean anything - PHP could no more see what nginx is doing than nginx see what PHP is doing. If gw1500se is right then what I said may already be in place for you. So print out the contents of $_SERVER and see if there's an SSL_PROTOCOL or similar you can reference (and what its value is).

PHP doesn't have access to that kind of information - it's all handled by the webserver automatically. As it should be. But you can potentially have the server inject the information into your runtime environment. For example, nginx has a $ssl_cipher variable that you could pass into the PHP environment.

Odds are the versions of openssl and/or libssh installed on your system are out of date. Update them.

One or more of those, yes. Impossible to say just with your description. Depends. No.

Oh dear. If you've got the money to buy Windows Server Datacenter then you've got the money to hire an IT person whose job it would be to deal with these matters.

Don't use a redirect. Half of the point of a 404 page is that it returns a 404, and using a redirect makes it do something different. Why not just change the 404.php to be this new page? Wouldn't that be easier?

Is your custom 404 page on some other site?

Doesn't quite answer my question. The very first rule you have RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^ index.php [QSA,L] says that anything that does not exist should go to index.php. If you want other things to apply first, other things that also do not exist, then those rules need to go before it.

What are the rules in that .htaccess going to do if a file doesn't exist?

Oh, this is being used by the other pages too? Add a parameter to the function about whether it should include the post's title at the end, default it to true for convenience, then modify the archive and search pages to pass false instead.

Would that not be the level99.value you're already using at the beginning of the function? For your other question, I don't know the right way of going about the math to find a function that lets you scale from a gradual increase (ie, a line) to a severe curve (like the one generated by the formula I gave earlier). To solve that I suggest seeing what you can find on the internet - anything ranging from straight math to some sort of try-it-out graphing tool; the basic form of the final equation will probably be along the lines of a*e^n + b*n + c.

Working backwards, you can see the breadcrumbs come from $items inside wrap(), which is called by render(). Inside that is a "breadcrumbs" which starts with "categories" and then will prepend the "bloginfo" as well as push (append) the $post. So try removing the bit to do with the push. That line also says "active" so you'll probably want to put that on the last item in the breadcrumb list, but honestly that's probably something better suited for CSS.

If you're going to record all the data, wouldn't it be easier to just make the table mirror the user table and stick the old row in there? Or rather, stick the new row in there, and apply the trigger to INSERTs as well.

So /blog/post-title does not exist as a file, right?

Fix what? A null will be coerced to false.

Isn't that what you first tried? It's not correct. Look at my second reply.

PHP? There's basically always a home directory set up for each user, though it might not actually exist, but that's a system thing.