Welcome to Geeklog, Anonymous Thursday, June 01 2023 @ 08:34 am EDT

Comments for Geeklog 1.3.7 released

Geeklog 1.3.7 released | 15 comments | Create New Account

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

Upgrade

Authored by: Anonymous (Anonymous User) on Monday, December 16 2002 @ 11:43 am EST

Is there a db upgrade to be concerned with (from 1.3.6)? Or do we just move the files in and edit the various config files?

Thanks.
Abe

http://www.tech-geeks.org

Upgrade

Authored by: Dirk on Monday, December 16 2002 @ 12:37 pm EST

The installation instructions include a section on upgrading ...

bye, Dirk

Upgrade

Authored by: Anonymous (Anonymous User) on Monday, December 16 2002 @ 02:10 pm EST

Yeah, I saw that. But I was confused when I saw that the Upgrade directions specifically mentioned the following:

\"Please note that there were no database changes between versions 1.3.5, 1.3.5sr1, and 1.3.5sr2, so when upgrading from any of those versions, simply select \"1.3.5\" as your current version.\"

But, it did not mention 1.3.6 or 1.3.7. Nor did the sql directory contain a file like \"mysql_1.3.6_to_1.3.7.php\". I thought it would be more efficient to ask, rather than start the process and hose my system.

Thanks,
Abe

(Forgot to login before my first post.)

Upgrade

Authored by: Dirk on Monday, December 16 2002 @ 02:37 pm EST

1.3.7 doesn\'t really upgrade the database (it doesn\'t add any fields or tables), it just fixes three problems, two of which exist only on some installs. So there was no need for a 1.3.7 sql file this time - these fixes are done by the install script.

In general, you should always run the install script with the upgrade option. The only exceptions were those that you cited: 1.3.5sr1 and 1.3.5sr2 used the exact same database as 1.3.5.

bye, Dirk

Upgrade

Authored by: jhk on Monday, December 16 2002 @ 01:26 pm EST

I just upgraded on my SME 5.5. Everything looks fine but I did have a few \"interesting\" experiences.

I copied everything in /public_html from 1.3.7 to the old /html folder and that was a slight mistake. If you are using Staticpages 1.2 (with PHP code available) skip /admin/plugins/staticpages and /staticpages. I had some problems with the new Staticpages.

Also, make sure you have copied all of your plugins from /root/to/geeklog/plugins to the new installation if you have it installed in a new directory. Otherwise Geeklog will show you nice, blank pages due to missing functions.inc.

Finally I chown\'d all of the files to www:www .

I believe that was it. We have similar servers, so it shouldn\'t cause you too many problems. Elapsed time incl. screwups < 1 hour.

(And now to report a bug with user.php).

/Jens

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks