Won’t Fully Upgrade to 2.6

I always upgraded manually until the last time. It’s not a hard job and it doesn’t really matter how much files it regards, I just select everything in my FTP client and go. The last time I also used the automatic upgrade plugin which went even easier. No problems with it.
What you can try to do is upload the files from the WP root folder, which includes the file with the version you’re running. If that doesn’t do the trick, you might want to do the upgrade process again, manually or with the plugin (but if the latter malfunctioned before, I’d do it manually).

WP root folder ! hmmmmm don’t tell me . . .

I’m assuming this is the folder with the wp-admin, wp-content and wp-includes folders in it – PLUS about twenty files including index, readme and license.

I’ll upload them again – excluding wp-config.php which incidentally I manually upgraded, as directed, to include the secret key.

Perhaps I simply missed something when I did the manual update first of those twenty or so files.

Many Thanks !

Even more so if it works! ??

Guran

OK

That brings up fatal error

Back to drawing board

*wonders if it will still restore to an earlier backup I made tonight*

What DID we do before electricity?

That brings up fatal error

Then my next guess is that none of the other files are actually 2.6 and the plugin did nothing in the end. You can continue uploading the 2.6 folders until you’ve copied them all and continue the upgrade manually.
All just suggestions of course.

Yeh thanks Gangleri

My Restore worked, so the Blog is fine.

Now all I need is about six hours to upload each folder-full of files.

I do have ftp-transport and net-transport but I only ever worked out how to USE Net-Transport. This could be a good occasion to find out how to use something I spent money to get!! ??
I don’t suppose you have any ideas? Perhaps I should looksee if there is a help or readme! heh

When I earlier tried uploading the files manually I ended up with the same fatal error message. There are just so many files I figured that was why the guy who developed the Automatic-Upgrade laughingly suggested people who liked it might wanna send cash!

I mean, in theory it should only save at least a day’s work!

You are no doubt right. I will probably painstakingly upload folder by folder all the files.

Thanks for your help. It’s kinda nice to know there are still people out there with the time to help.

Upgrading with FTP doesn’t take much longer than by use of the plugin, it’s just that the plugin makes backups automatically. Basically it’s simple, you use FTP to copy ALL files from the WP pack to your server. Normally this can be done in one time (just select all files and folders and go), but safer is folder by folder. After that, try to login and you’ll be prompted to upgrade and that’s it. It takes about 10 minutes. If all goes well of course ??
Extra folders such as uploaded themes and plugins are left untouched, so there’s nothing to worry about when you didn’t edit any WP files or the default theme.

hmm

The FTP I use in my Direct Admin only allows selection of files – as many as I like but still I hafta do the job one sub-folder at a time and there are lots!

I know the basic procedure – just you use the term ‘upgrading with FTP’ as though I could simply select, for instance, wp-includes , with all its sub-folders and upload it directly to my domain. I’m not sure that’s even possible, given the access protection protocols of WP and my Direct Admin application.

I’ll ‘speriment’

Ahhhhh *smiles*
My FTP Transfer thingy has spaces for “Host” “Username” and “Password”

PORT will throw me but it’s only a speriment eh?

That was easy!
Now I am TOTALLY confused.
It’s only 45 minutes to tomorrow sooooo

yep ??

There’s also ‘real’ FTP software, such as Filezilla.

OK – another day. Where I am at.

At present I have all the files in the public_html folder at ver. 2.6 except wp-login.php and wp-settings.php

When I upgrade those I get the fatal error message. It says:

Fatal error: Call to undefined function: force_ssl_admin() in . . . and then refers to the two above files, via their root and dependencies.

ie. Fatal error: Call to undefined function: force_ssl_admin() in /home/Host/domains/OURblog.com/public_html/wp-login.php on line 15

The identical problem crops up in ‘settings’ at line 390.

Any suggestions? Or if there was a way to disable that call to ssl, would that simply let the login routine run until it found the NEXT inconsistency?

The blog is up and running (has not auto-upgraded on login) with, so far as I know, only these two files still being at ver. 2.5.1

*confused*
*unhappy*

As far as I know, WP doesn’t use SSL unless you tell it to. I don’t use SSL for sure and I haven’t had to turn it off when I went from 2.5.1 to 2.6. Perhaps the article referred to in this thread gives some more information. Weird though that you can’t just install 2.6…

Hi Gangleri ! I’ll go to that link and see if it makes sense to meh.

I’m really the one who puts the tracklist together for our music player!! But I know about as much as Guran (meaning my mistakes are just as disasterous and my lucky guess as sweet) ??

What I can’t understand is why it calls for ssl in the first place. It’s a feature on the page intended for the use of visitors (I think – it was on the old blog but that ran in Joomla.) Should have no reference, I feel, to either login or page loading at the site.

RaiofOz

Ya! Think I’ll stick to developing omelettes.

Rai