Search results

add_filter() is a core WordPress function defined in wp-includes/plugin.php. It’s used to register a filter hook — in other words, it lets you modify or extend WordPress functionality. The error says: PHP Fatal error: Uncaught Error: Call to undefined function add_filter() in wp-config.php:103...

That may be true, but it's only one side of the coin. The other is that the users who care about this are also the top professionals who can handle virtually any situation. Because they have familiarized themselves with almost every area through constant engagement with problems and have gained...

The ticket has been processed, as usual with precision and within a good time frame. But the outcome was not satisfying. My argument is that when a domain is set to "no SSL" meaning SSL is disabled, this does not affect the "webmail" subdomain of that domain, even if that webmail subdomain is...

And now we finally got a case just as @mow described it. So it seems it is not OS dependent. So obviously, not all SNI-files are updated, and one single wrong file will keep Dovecot from restarting.

Argh, just as I am getting involved, it starts hitting servers here. One reason for an outage here was that a custom Dovecot configuration file was in conf.d that could no longer be interpreted by the new Dovecot version.

The operating system might make a difference, because installation and upgrade processes are different between Debian and RHEL. Our systems are running Alma, so maybe that might have avoided the issue. But in general I think you are very right that there is a strong testing deficit before...

Not so likely. On the servers here, Dovecot becomes unavailable for several minutes, but finally restarts properly. There seem to be reload or restart attempts during the upgrade, but there is also a final reload after the update is through.

5% seems a bit low, maybe try something like 30% or more? Else the warning will be triggered if a service like Apache uses more than 5% of your RAM, and at 8 GB that is very likely to happen.

I am almost certain they won't want to do that, because it's more economical to have all users on the same release state. That is what makes your solution so interesting. A small rebellious Gaulish village that stands up to the great world power :-)

I've created ticket #95829596

Maybe @Kaspar can jump in and do it as a coop project. I think he knows how to create the extension.

That would make a great Plesk extension!

This has been asked for for several years. Plesk used to have three tiers, including a "late adopter" tier. I, too, think they should re-introduce that. I'd rather have the upgrade only after the first two fixes to a new release came out.

Please don't make such stupid assumptions. Overall, I am pretty much fed up with your posts. They are rants against the panel only. What's the point of this? If you don't want to use the panel, don't use it. But you are constantly trying to convince others that they should not use it either. You...

Username: TITLE SSL auto-renewal attemps do not stop after removing cert and disabling SSL PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Obsidian 18.0.73 #2 Alma 8.10 But the issue exists since 17.8 and CentOS 7 PROBLEM DESCRIPTION A domain that previously pointed to the...

Thank you, I'll try it on a few servers. So far I have "AllowStoreRestart On" on all, but I did not yet have "DeleteAbortedStores Off". The latter might cause new issues when a truly interrupted backups cannot be resumed, because then partial backup files might occupy space on the external FTP...

Backup Manager: A full backup takes hours, during that time period we experience short network connectivity issues to the external FTP storage space. These are probably short, maybe a minute, maybe two. But they are long enough that the backup manager thinks, the connectivity is lost and ends...

Either Mod_Security (web application firewall) is blocking access (you can tell from an error.log entry of the 403 error code) or the permissions of the document root directory of the website are wrong. They must be <subscription user account name>:psaserv, not psacln.

I sometimes ask myself why I give detailed to-do descriptions when all that results is just a repetition of "something's wrong" ...

Yes, but what could I use the information for?