muddg

It could very well be. You are referring to the name server setting in your domain registration account (Godaddy?). The name server setting should contain a server name where your domain is being hosted (also Godaddy?)

If you don’t have domain privacy (through a domain proxy) you can see who your registrar is and what the name server setting is by using this WHOIS search which you will find at the bottom of GoDaddy’s home page. Just enter your domain name in the search box and look for the Registrar URL to confirm the registrar company and then scroll down the page and note the Name Server. There are usually two or three Name Servers specified.

Armed with this information you can then talk to your hosting company (Godaddy?) about what the name server should be. And if the registrar is GoDaddy they will also be able to tell you how to change it if it is incorrect.

Note: if you do update your name server, it usually only takes a couple of hours for the update to be effective but sometimes it can take up to 48 hours. So give it time before you conclude that it hasn’t worked.

Hope this helps.

The problem with running WordPress on IIS is that comparatively few people do it. There is tons of information about running on Unix/Linux based platforms but not Windows IIS.

I manage WordPress sites on a Windows Server (2008) running IIS7. It is never easy to locate answers to problems with WordPress on IIS.

It is trying to copy a file or folder and probably doesn’t have the correct permission.

Start by checking the permissions on the root folder.

Is this on a Mac? If so check this support post for some useful details.

Below is the code in class-wp-filesystem-direct.php
starting with line 213 to 221
`function copy($source, $destination, $overwrite = false, $mode = false) {
if ( ! $overwrite && $this->exists($destination) )
return false;

217 >>> $rtval = copy($source, $destination);
if ( $mode )
$this->chmod($destination, $mode);
return $rtval;
}’

It is trying to copy a file or a folder.
This is probably a permission problem.
Read the last entry on this support post where Dave explains how to check permissions on WAMP.

Well before you try upgrading again, you might want to research how to run two different versions of PHP at the same time. That way you don’t have to downgrade….you can just swap from one to the other and back again. I do this all the time on IIS with fastcgi. I’ve read you can do this on Apache so presumably you could do it on ubuntu.

Good luck with future upgrades!

After searching for instances of the error non-object in the update-core.php I would look closely at plugins. There might be some plugin you are using that isn’t playing nice with the version of PHP to which you upgraded.

Well…you would “hope” that that at least the themes released with WordPress would work with the latest version of PHP.

You seemed to imply that you’ve eliminated all other possible causes (e.g. permissions? an incompatible plugin?). You said: the only thing that makes sense is the PHP upgrade.

Easy to prove your theory by reverting back to an older version of PHP. You can have two versions of PHP installed and specify which version a specific WordPress install is to use.

I just quickly researched the non-object error message. Makes me even more suspicious of PHP but I want to dig deeper.

What about the PHP.INI file? Did you review all the settings in light of the upgrade? I am assuming you have control over your webserver.

This kind of thing usually happens because of a permission problem on a directory or a specific file.

You can “usually” (9 times out of 10) resolve the failed installation by doing a manual update.

So you have to use FTP to get to the back end. If you haven’t alrady, take steps to do a backup including MySQL database and at the very least backup the wp-config.php file which is in the root directory of the WordPress install.

You can find instructions for the manual update on this page.

If you need any further help with this procedure, post your questions here.

Forgive me if I am telling you how to suck eggs.

Have you tried swapping to a different theme…just to eliminate a theme problem?

Have you disabled any plugins you might be using?

Have you checked your PHP error log. I find it more convenient to turn debug on and off in the wp-config.php file. If you want more info on this see this article.

When all else fails…double check your permissions.

There are many “image” related problems reported for 3.9. You might want to revert back to 3.8.3 until 3.9 is stable. You can find an archive version here.

Look…I don’t want to waste your time but I still think you have a permission problem.

Do I understand correctly? You are setting the permissions on the windows install. Then moving the whole thing over to your mac with ftp…assuming the permissions are going to follow?

Also you mentioned custom.css. You are using Thesis theme, yes? Which version?

Oh good!

Okay. I’ve done some research. There are a ton of ways this problem can occur but I think your problem might be the same as describe by this support log Unable to Access Admin Page

There are numerous other sources reporting that the problem … when it occurs out of the blue … is due to the hosting service changing something. Here is another example not related to WordPress.

If that isn’t the cause of your problem, enter the following into google and review some of the other ways people have encountered and solved this problem in relation to WordPress.

site:www.remarpro.com “err_connection_reset”

Well that certainly indicates a permissions problem. I found this information about permission problems on a Mac:

To get around permission errors, on a Mac, you would just have to change the permissions. Go to the file/folder you’re trying to access, right click and View Info. at the bottom there is a box for permissions, and just change for the user _www (add it if it’s not in the list, it might be www) and give it read and write permissions for whatever it needs.

That paragraph came from this page. You might want to review all of the contents on that page but initially scroll to the paragraph at the bottom.

Again, I am not familiar with Mac so that page listed above might lead you down a successful path. I will see what more I can learn about permissions on a Mac.

I don’t know WordPress on a mac so I might be asking stupid questions but when you say editing the files themselves…as a workaround…do you mean you are editing the post records directly in the database itself?

There are different types of users in WordPress and the authority to edit posts varies according to the type of user logged in. Are you sure the logins you are using have authority to edit posts?

Okay so if I understand the problem. You did have wordpress running successfully and then all of a sudden you started getting the error above only when you visited https://www.bhgis.org/wp-admin and try to login?

Were you just setting up wordpress or did you have content because I
I see that https://www.bhgis.org/index.php works but it is the standard WordPress “hello” page…no real content. And when I try https://www.bhgis.org/wp-admin I get a 404 error but if I click on the login link at the lower left corner, I get the login page.

Was there any updating you did before this problem occurred? A WordPress Update or a new plugin installed or updated? Or was the server where the site is hosted get updated in any way? A PHP update?
Did you change any of the permission settings on any of the WordPress files or folders?

Where is the site hosted?
What is the version of WordPress?

Did you move any files or folders around? I can make the error happen just by trying to login. There is something about the URL that pops up after trying to login doesn’t look right to me. Is wordpress installed in the root of your domain or a sub directory?