sandrab

Thanks, @fierevere for your fast reply!

I will ask the server administrator to reinstall the certificate.

That will probably solve the issue in this particular case, but I keep wondering about the WordPress side. I don’t understand why the ca-bundle shipped inside WP should contain an expired entry, which at best has no effect and at worst kills the functionality to connect to an external server. Not everyone has control over either the external server or the hosting environment they are using. And it just does not make sense to keep it there in my (slightly simplistic) view of things.

I will keep this post unresolved in the hope that someone might explain the rationale about whether we would want to update the WP core ca-bundle or not.

Anyhow, thanks for your input – it also helped me getting my head around it some more. Thanks!

Hi Paul,

That is great, thank you very much!

Sandra

For anyone coming here from a search, this seems to be the same issue as admin-pages-not-showing-readability-or-seo-score. With a corresponding GitHub issue.

Hi Kat,

Thanks for your reply, much appreciated!

I removed ‘proc_get_status’ from the disable_functions setting on this server a while ago to get rid of the warnings and have backupwordpress work properly – keeping my fingers crossed this does not open a security hole.

But when reading your reply I decided to look a bit further into the code of backupwordpress. I found that the check whether to use the Process class or not is done by checking whether proc_open and proc_close exist (classes\backup\class-backup-utilities.php – get_executable_path()).
The Process class however not only uses proc_open() and proc_close(), but also proc_get_status().

Would it not make sense to check on all three proc_ functions then?

I can not try to change the disable_functions on the server to test things there, because it is a production site. But I did try on my local development environment what happens when I have both proc_get_status AND proc_open in my disable_functions and as to be expected, that solves the warnings as well. The backup then falls back to using the class-backup-engine-database-imysqldump and class-backup-engine-file-zip-archive engines.
My local box is windows, so it might behave a bit different than unix/linux here, but I just wondered if you also think that adding a check on proc_get_status might be logical.

There is also a call to proc_terminate() in the Process class, but I can not really figure out when this is used or not. And to exec(), which seems to happen only on windows, but I don’t see anything going wrong when I put just ‘exec’ in the disable_functions on my windows box. Apparentely the function in Process using this exec() call is not reached in my situation.

I assume the other options I have in disable_functions on the server don’t influence this since I don’t see them in the Process class. Locally I don’t have them, and I did not try them either. Do you agree?

You could hack the style.css of your theme. Look for the code snippet I posted, and remove the line that says:

padding-bottom: 0;

Look for it in wp-content/themes/simple-catch/style.css.

If the Simple Catch theme gets updated with a newer version however, you would have to do this change again. So normally it is not advised to hack the theme directly but create a childtheme instead. If that is a bit too much, just be sure to remember what changes you made to the theme before updating it when a new version is available.

Seems like your theme removes the padding-bottom from paragraphs on home and archive pages. In the style.css it has:

.home .post p, .archive .post p {
clear: both;
padding-bottom: 0;
}


Are your sites part of a WordPress Multisite installation? Like described here: https://codex.www.ads-software.com/Create_A_Network?

If so, updating will update the entire network, so both sites in the network will be updated at the same time.

If not, the sites probably use a different table prefix (the default table prefix is wp_) and have separate WordPress directories. You can update them separately, turning only the site you are going to update into maintenance mode if you like.

Could be related to this ticket for 4.2.2:

https://core.trac.www.ads-software.com/ticket/32308