royatl

I have the same problem (i.e. file manager does not show up except for “WP File Manager”), but in my case, deactivating the GoDaddy Worker plugin (i.e. ManageWP worker) allows WP File Manager to work.

Looks like while Maps API was the only thing that was needed to associate with the key five days ago, now they require also enabling and associating Geocoding API and Geolocation API. Did so and now location map works.

Deactivated Divi Builder on my site and that worked. Fortunately I was just testing some pages so deactivating isn’t a big deal, but the next version of the site is based on the Divi theme.

And by the way, replacing with the OSM plugin didn’t work either, so it looks like EM is not instigating the search (though it does look like a nice plugin — does it do satellite imagery?? I need that.)

Unless the APIs or their procedures have changed again in the last couple of days, I don’t think this is due to APIs, as I have the various keys and have confirmed they work, and entered locations as recently as a week ago.

Same problem here. This started with another bug I’m about to report on, where I’m entering a new location and the geolocation is not responding to any address entered. In case these are somehow related, I’ve mentioned it here.

I second that this would be useful (like I need it right now! hehe), or at least be able to enter a projected date, but replace the date display with a string like “TBA”, “To Be Announced”, or something similar.

Ah, very good. Thanks!

That pretty much is the step-by-step.

To start with, I had, say, three locations defined. We’ll call them Atlanta, Memphis, and Nashville.

An event was defined, with location Memphis.

At some point, we found we couldn’t use the Memphis location, and we would have to change it to Atlanta, but Atlanta was not yet confirmed, so I had to make some change on the schedule, so I went to the event and checked “This event does not have a physical location”.

A couple of weeks later, Atlanta was confirmed, so I went to the event and un-checked “This event…(etc)” and then typed Atlanta into the location field, thinking it would do the search and let me select the Atlanta location. But it did nothing.

I then typed in the rest of the information for the location, and when I hit enter, I got an error message that the information is incomplete.

I then went to the location page and found that another “Atlanta” entry had been made.

Thanks for looking into this.

That sounds like you haven’t made the wordpress root folder writable to IIS.
You need to give write permission to user IUSR.

Point to your wordpress root folder (probably under C:\inetpub\wwwroot\).
Right click, select Properties, select Security tab, click the Edit… button. If IUSR is not in the top list, click Add… and add it. then give it full control.

Now go back and try the wordpress install again. This time it should work great.

——

ooops, just noticed you said IIS6. I’m pretty sure this solution will work with IIS6, but there might be a slight difference along the way. Like maybe the IIS user will have a different name. Google or Bing for the differences between IIS6 and IIS7.x

The problem was that I was going to

https://subdomain.domain.com/wp-admin

…without a trailing slash like so:

https://subdomain.domain.com/wp-admin/

… This works as advertised!

The problem here was that I was going to

wp.mydomain.com/wp-admin

I should have been going to

wp.mydomain.com/wp-admin/

Note the trailing slash! It is uber-important!!

Sorry that I didn’t update this topic immediately upon finding the answer. Hope this helps someone.

(the “paths” I refer to are 1. to the host; and 2. to WordPress. Yes I’m aware I put four items, but two are to the host, and two are to WordPress, so I feel I’m within the spirit of correctness if not the letter)

Here is the problem.

As with many things, there are two sides to it.

First. GoDaddy (and other hosts, probably) set a PHP script’s max_execution_time to 30 seconds.
Second. Some of GoDaddy’s servers are slower than others. Even when they’re supposed to be much faster.

Third, in class-wp-upgrader.php, there are three routines that have to be done: download_package(), unpack_package, and install_package. WordPress uses set_time_limit() to increase max_execution_time temporarily to five minutes. But ONLY for installation. It does not do this for downloading or unpacking.

The combination of slow server with short max_execution_time means that large updates, or updates with large numbers of files, will probably timeout while downloading or updating. The timeout is silent (i.e. no error is displayed) so the end result is that the process has appeared to hang.

So, there are two paths you can go by… (hmm. there’s a song there…)

1. you can go to your host and get them to increase PHP’s max_execution_time (or if you have access to php.ini, you can do it there).

2. you can annoy your host to speed up the servers.

3. you can annoy the WordPress coders to add ‘set_time_limit(300);’ to the appropriate routines in class_wp_upgrader.php.

4. you could add the lines yourself, but you’ll lose them first time you update WordPress, which sorta defeats the purpose, and anyway, is against the WordPress Way.

Roy

Brief update: Haven’t gotten with GoDaddy about this since I have other fish to fry at the moment. However, I updated the Akismet plugin with no problem. WordPress update still hangs during unpacking.