• From the codex:

    You can launch the automatic upgrade by clicking the link in the new version banner (if it’s there) or by going to the Tools -> Upgrade menu. After that it should be straightforward.

    In a pigs eye! I get a screen that asks for

    Hostname:—
    What hostname? All I can think is that its the domain name that is running this WP. But why is it asking? Surely it knows already — it shows it in the upper left corner of the screen.

    username and password:—
    Again, whose? by the above logic I’ll use my wp-admin values. But again, it already knows these.

    Try it, get error message ‘cannot connect’.

    There’s a little ftp radio button, maybe it wants to ftp to my host.
    Enter ‘anonymous’ for user — won’t accept missing password.

    Try my main ftp account name and password.

    Still can’t connect.

    Can someone explain to me what really goes in hostname, username and password, and why this must be obvious to everyone but me?

Viewing 13 replies - 1 through 13 (of 13 total)
  • Hostname: FTP host
    Username: FTP username
    Password: FTP password

    Thread Starter ek_wals

    (@ek_wals)

    Nope. Perhaps it doesn’t like the form
    https://ftp.myhost.com/~user
    Forced on me because the (working) site is at another host.
    Can you only upgrade a live site??
    And is it true that you can’t use anonymous?

    Where is this site? Local or on a remote server?

    And is it true that you can’t use anonymous?

    That would depend upon the server/host that you’re using but in 99.9% of cases, I’d say that anonymous FTP login wouldn’t be allowed

    Thread Starter ek_wals

    (@ek_wals)

    The site is currently on Dreamhost. I want to move it to ASO(asmallorange.com) and to upgrade it and change the theme. I do not want to do the upgrade to the live site. I have installed WP 2.8.6 at ASO, and want to upgrade it to 2.9.1 before I attempt to overlay the actual site and import the sql.

    Is it ASO who are using the https://ftp.myhost.com/~user hostname?

    You could try entering the ftp credential into your wp-config.php file and see if they’re accepted that way.

    Thread Starter ek_wals

    (@ek_wals)

    Yes. I have to because ‘mydomain.com’ points at the site on dreamhost.

    I put the FTP_HOST, FTP_PASS and FTP_USER defines into wp-config.php
    Upgrade now shows those values already entered in shaded boxes but the same message
    Error: There was an error connecting to the server, Please verify the settings are correct.

    The host box shows the host ending with “…:2” instead of ‘..:21’ Is there an actual length limit on the hostname, or just a display issue?

    Tried without the ‘:21’ same result
    Created a new ftp user with simple password — same result.

    Thread Starter ek_wals

    (@ek_wals)

    My ftp client seems to have the same problem but give a better error message “invalid host name specified” Apparently I just can’t FTP to an inactive site. Fortunately the inactive site can still upload.

    I think I’ll give up and assume that WP cannot be updated except on a live site (scary), and stick with 2.8.6 until Fantastico starts installing a newer one.

    Thread Starter ek_wals

    (@ek_wals)

    Perish the thought! I’m already lost in the woods. I don’t need to get sidetracked into getting a local server to work, and then figure out how to incorporate it into my work flow.
    I’ll just assume that 2.8.6 is good enough for now and some time into the future and live with it.

    Just got to the point of seeing that to get Akismet working I had to enter my WordPress API key. After getting new passwords from WP etc, I discover what it really meant was “Akismet API key (which I had already) Grr!

    Thanks for your help. A negative result but a result nontheless.
    At least I know this one problem is not just my stupidity!

    If you use Windows, I reckon you can get a server set up inside 30mins using EasyPHP:

    https://www.easyphp.org/

    Thread Starter ek_wals

    (@ek_wals)

    Yeah but then what? what pitfalls await? What stupid thing will I do to mess things up? What little thing will I forget that leads me on a wild goose chase? How can it help but provide a dozen more places for me to screw up?

    After all, this goose chase began with the desire to upgrade WP. What could be simpler than pressing the upgrade button? On a newly installed WP instance. 3 hrs later and I’m preparing to reinstall my site from scratch just to get it to work without the upgrade.

    The bottom line is that the WP automatic install can’t work until the nameservers are pointed at my site – at which point I won’t dare to even try on the live site.

    Sorry about the rant – this stuff seems trivial for everyone but me.
    Thanks for trying to help (actually, you did)

    Ah well – can’t win ’em all. ??

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Upgrading to 2.9.1’ is closed to new replies.