Downgrading to a pr...
 
Notifications
Clear all

Downgrading to a previous installation (3.x.x to 2.x.x) and login errors

4 Posts
3 Users
0 Reactions
2,080 Views
(@guest2423)
Posts: 0
 

URL to your eFiction: http://www.strawberrywine.org/efiction/index.php
Version of eFiction: 3.4.3, in a way, but the upgrade failed, so TRYING to get off this crazy thing, Jane.
Have you bridged eFiction, if so with what?: No.
Version of PHP: 4.x
Version of MySQL: I honestly am not sure, as I'm horribly unfamiliar with MySQL, but I use http://www.phpmyadmin.net/ If someone were to explain how to determine this, I'd find it.
Have you searched for your problem: Tore the forums apart.
If so, what terms did you try: Every single "error ####" one that popped up (1054, 1166, among others) during installation, and then after ascertaining that yes, upgrading is totally not worth the hassle, I searched for things like "downgrade", and while I found a few threads referencing people "unfortunately having to downgrade" none seemed to actually detail the process :/ Then tried "1054 login error" with equal lack of helpful results.
State the nature of your problem: The upgrading problems aren't really what I'm here for, as they are too numerous to write out (mostly the automatic upgrades didn't work, and in all the manual stuff something went wrong somewhere I suppose), so I'll just say I'd really like to get back to the nice stable (hah!) environment I had with 2.0.7. Before attempting to upgrade, I saved all my files to my computer off my server and exported my database I was using into a zip file. Now I just want to put them BACK up, and while it's a simple enough task to just replace all the files on my server with the ones I'd copied off, it seems simply uploading them has left some unfinished problems. Now whenever I attempt to log in, I receive the following error:

_FATALERRORQuery: SELECT password,penname,uid,userskin,level,email,categories, ageconsent FROM txnfanfiction_authors WHERE penname='fencer_x'
Error: (1054) Unknown column 'userskin' in 'field list'

I'm not sure if perhaps something was changed on the MySQL end, and if it was, how on earth do I go about using this zip file I got when I exported my database to fix it? It only shows an error after attempting to login on user.php.

Do you have a test account for us? No.

In essence, I just want to know how to get everything back to "normal" since using this software for me seems to be like adjusting bunny-ear antennae on an old TV: once you finally get it working, NEVER TOUCH IT AGAIN πŸ™

(also, while this does have to do with 3.4.3, my problems are now relevant to 2.0.7 -- should this topic be moved?)

All the stories are back, but it's not going to do much good if no one can log in! Any help would be GREATLY appreciated!


 
Posted : 05/09/2008 3:16 pm
(@babaca)
Posts: 722
Member Moderator
 

Don't know. Did you back up your database before trying the upgrade?

The error message that you have posted is one about the user skins. The 3.x user skins doesn't play well with 2.x skins and vice versa. If your are reinstalling 2.x make sure you only have the 2.0 skins and not ones from 3.x


******************************************
Mucking around in eFiction since circa 2001 (ver. 1.0)
Now running v.3

 
Posted : 05/09/2008 3:56 pm
(@guest2423)
Posts: 0
 

I did indeed back up the database, and have a lovely .sql file that...I know nothing to do with. I've noticed, after playing around with it, that there are many features that have been messed with by the upgrade (with changes made to the database to support 3.4.3 that no longer work now that I've put 2 back on it), and suspect that if I can just overlay the original .sql file back on there everything SHOULD work again.

Except I've no idea how to do that  😐


 
Posted : 05/09/2008 10:08 pm
(@becca)
Posts: 553
Honorable Member
 

If you have your files/mysql backed up as babaca said, then what you should be able to do is start from a clean installation and just import the data so to speak using phpMyAdmin.


 
Posted : 06/09/2008 2:30 am
Share: