Geeklog Forums

After installation and getting the site back up and running from a mysql backup, if I go to post a new story, when I click "Save", I get the following in the error.log file:

Fri Jan 5 14:09:06 2007 - 1054: Unknown column 'advanced_editor_mode' in 'field list'. SQL in question: REPLACE INTO gl_stories

In the config file,

$_CONF['advanced_editor'] = false;

I have toggled this, tried again, same error. Changed back to false, same error.

Looks like, during the install, the field did not get injected into the table.

Thoughts? Fix?




/CF

So did you do an install or a restore from backup? Or both, meaning the backup was from an older Geeklog version?

bye, Dirk

Found the problem, previous admin of the site put some custom code into the story.php file. I believe I have it resolved.



/CF

I would like to please revisit this issue as I am receiving the same error. I restored a backup db into a new installation. All of the geeklog files are new and default except the ones necessary to change.



please let me know if you need more of the error. I am on the latest version of geeklog,

Sounds like you didn't run the install script in upgrade mode. You need to do this to update your database, e.g. to add new fields like the "advanced_editor_mode" (which is new in 1.4.1) it's complaining about.

bye, Dirk

So I should run the install script again, this time in upgrade mode?

I read this, maybe I am confused. http://www.geeklog.net/faqman/index.php?op=view&t=37

I received the backup of their database,
I installed geeklog
I emptied the database and uploaded their backup

now I need to go through the install agian and choose upgrade? While the current data is in the db?

Thank you very much for your help.

I also notice, it is giong to this page in the url when trying to post

http://www.jackkingoff.net/sngiconsmain/geeklog/public_html/admin/story.php

obviously this file is not in that location

i apologize for my incorrect post above.

Yes.



Check $_CONF['site_url']

bye, Dirk

I am not upgrading though, I am migrating and our geeklog is on the latest version for the old and new setup.

I am getting this, Its been re uploaded a few times and verified successfull by my hoting. i have also tried multiple backups of the DB.



Any thoughts?

Same as above: A complaint about a new field (used in the code but not present in the database).

Are you sure you were running the same Geeklog version on the old site as the one you now have on the new site? From the errors you're getting, I'd say they were different.

bye, Dirk

Yes I run the version check and it comes back with the latest version. 1.4.1

I dont see anything in story.php about anything in this error. Is there another file it may be in?

From what I can tell sp_help is the only field that is not in the gl_staticpage table if that means anything.

A search for "advanced_editor" should result in quite a few hits in admin/story.php

At the risk of sounding like a broken record: Your database seems to have been created with an earlier version of Geeklog.

Have you tried running the install script in upgrade mode? Since you have a copy of the database anyway, the worst thing that could happen is that you'd have to reinstall that db backup.

The install script will actually try to guess your current version (see what the version dropdown defaults to) and will refuse to continue if it thinks your database is already up to date. But my guess is that it will upgrade your database.

bye, Dirk

I had tried to run in upgrade mode and it has reported an error, something existed. I saw the error in the common errors part of the install instructions, it said something about havnig already tried the install. I did a fresh install and got the same thing.

Anyways, I went ahead and started from scratch again.

Installed 1.4.1, verified the new isntall worked.
Deleted the db content and imported the backup DB from the old hosting.
I verified I received the same error as above.
I tried again to run the upgrade.
It said it successfully went through.

I verified that Admin can log in and post, success. I have not verified regular users yet.

Thank You so much for your help. I am not sure why it took so many attempts to fix. Im sure i screwed something up to make the upgrade not work the first few tries while i was trying to fix the problem.

For future reference. Does it matter what version the old DB is, or the version it was installed from. I just went and verified and it said 1.4.1, however per the upgrade it said 1.4.0 so I'm assuming they installed 1.4.0 then upgraded to 1.4.1. ?

So, if I take this db from my test server and import it to a db in my production server. Theoretically, all I will have to do is to change the db username and pass in the config.php file correct? Assuming the import is 100% successfull and whatnot.

The version check in Geeklog only checks the version of the code, not the database. Actually, it only looks at the version number in config.php

The install script, when upgrading the database, looks at the existence of a few fields and tables and determines the current version from that (e.g. when the gl_users table has a 'remoteusername' field, it's at least version 1.4.0, and so on). It's not bullet-proof, though, and a failed upgrade could confuse it.

bye, Dirk