The Ultimate Weblog System

Resources

Getting started

Support

Development

Sections

Home

Geeklog (190)

Geeklog 2 (28)

Announcements (201)

Summer of Code (8)

Security (55)

Plugins (50)

Server (26)

Spam (10)

User Functions

Don't have an account yet? Sign up as a New User
Lost your password?

What's New

STORIES

No new stories

COMMENTS last 2 days

No new comments

TRACKBACKS last 2 days

No new trackback comments

NEW FILES last 14 days

LINKS last 2 weeks

No recent new links

Older Stories

Welcome to Geeklog
Friday, May 16 2008 @ 01:43 AM EDT

Making Huge Jump In Upgrade

Wednesday, January 09 2002 @ 02:14 PM EST
Contributed by: Anonymous
Views: 1,783

Hi -

I own Jiggin.net and am having some problems. First of all, if you go to www.Jiggin.net you will find a major database error...that is a big ordeal. Second..I want to upgrade to the newest release but am told from the guy I bought the site from that jiggin.net is using like a pre-1.2 maybe 1.1??? beta. Anyway, how do I make this upgrade? I am moving the site to a new host in the next couple days...it would be a great time to make upgrade. Would I loose all users in database or any other info in database?

I NEED HELP!

Thanks all!

matt

What's Related

Story Options

Printable Story Format

Making Huge Jump In Upgrade | 1 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

First things is first

Authored by: Tony on Wednesday, January 09 2002 @ 03:06 PM EST

I have no clue why you are getting the MySQL errror. My guess is your database configuration has changed or you edited config.php with the wrong database parameters. What do you have at line 79 of common.php?

Upgrading will be a major pain for you if you are using a non-production release (such as a beta). The only reason I say this is because there are no database upgrade scripts for non-production releases. What you should do is create a fresh 1.3.1 installation (due out any moment). During the 1.3.1 database configuration you should specify a database prefix of gl_ and that will create all the tables as gl_<table_name> leaving your original 1.1.x or 1.2.x tables in tact. Then you can go in and issue the SQL commands to copy over your users and stories from the old tables to the new tables (this will take a little elbow grease).

If you luck out and are using an older production release then all you need to do is apply all the updates in /path/to/geeklog-1.3.1/sql/updates to upgrade your database to 1.2.5-1. When that is done you can run the installation script to upgrade your database to 1.3.1

--Tony