Welcome to Geeklog Saturday, September 21 2019 @ 12:06 pm EDT

Geeklog Forums

Specific 1.4 to 1.5 upgrade


Status: offline

ofey

Forum User
Full Member
Registered: 18/03/05
Posts: 213
Location:Dublin, Ireland
I wish to upgrade from geeklog 1.4 to 1.5. The documentation states:

When upgrading from Geeklog 1.4.1 or earlier: Put the config.php files from your old install back into their place now (the main config.php and those for the plugins). The install script will read these files during the upgrade to pre-populate the new Configuration admin panel with your settings. If you skip this step, you will end up with default settings for Geeklog and the pre-installed plugins.


So after extracting the new tarball for 1.5 I have two geeklog private directories let me call them geeklog1.4(old directory) and geeklog 1.5(new directory) and I also have my real public directory public_html (not the public_html directory in geeklog1.5).

There seems to be nothing in the documentation about copying the files in geeklog1.5/public_html to the real public_html directory. (Maybe my server's set up is a little different than most, but I have my geeklog private directory and public directory alongside each other.) Anyway if I do copy the files in geeklog1.5/public_html to the real public_html directory won't I over-write a lot of the plugin files for example the files for the filemgmt are in pubic_html/filemgmt_data. Perhaps it would be better to backup the plugin directories and place them back where they were after I put copy geeklog1.5/public_html to the real public_html directory.

I also see that I have to put the main config.php (making changes to it first) and each plugins' config.php in from geeklog1.5 into their respective new places.

When upgrading from 1.4 to 1.5, is this process really more to do with upgrading the database or are there much changes to the actually files in the directory geeklog1.4 and the actually public_html directory?

Shane
Those who say it can't be done, are usually interrupted by others doing it.

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
The documentation isn't very specific about 3rd party plugins, I have to admit.

The basic idea of an upgrade is: Remove all the old files, put the new files into place, run the install script. When upgrading from a pre-1.5 version, you also need the old config.php files so that their content can be added to the Configuration settings which are now in the database (otherwise you would end up with default settings).

So, what about other plugins? You could put them back into place before you run the upgrade. Which may or may not cause problems, e.g. when a plugin is not compatible with the new version.

The installer will check if an enabled plugin is not available and will disable it during the upgrade. So you could simply run the upgrade without the 3rd party plugins and put them back once the upgrade went through. That's a bit more work, I guess, but makes it easier to figure out issues when something goes wrong.

HTH

bye, Dirk

Status: offline

ofey

Forum User
Full Member
Registered: 18/03/05
Posts: 213
Location:Dublin, Ireland
I successfully upgraded from 1.4.1 to 1.5.1 but I was only trying it out so the upgrade was done to a different domain than I would untimately use. I wasn't then able to change over to the correct domain. So I started again.

This time when I am upgrading fro 1.4..1 to 1.5.1 I get:

Geeklog Installation (Step 1 of 2)

Welcome and thank you for choosing Geeklog. You are only 2 steps away from having Geeklog 1.4.1 running on your system.


But I already have Geeklog 1.4.1

Ignoring this I then continue and do an upgrade databse and get

Geeklog Database Settings (Step 2 of 2)

Now we are ready to add the necessary data structures to your Geeklog database. If you are upgrading, please be sure to select the current version of your Geeklog database below. If this is a new installation, just hit the 'Next' button. We hope that at this point you have already backed-up your existing database (if you have one). If you haven't then do so before clicking the 'Next' button below. You've been warned.
Database already up to date!

It looks like your database is already up to date. You probably ran the upgrade before. If you need to run the upgrade again, please re-install your database backup first!


There is only a 'Back button'

If I go to the normal URL, I get the error,

Fatal error: Call to a member function displayElements() on a non-object in /home5/simongib/glffetac/system/lib-story.php on line 79


Has anyone got any ideas?

Shane
Those who say it can't be done, are usually interrupted by others doing it.

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
You're using the old install script. As of 1.5.0, we have a completely different install script with a different UI - you'll notice the difference immediately.

Make sure you've updated all the files. See above ...

bye, Dirk

Status: offline

ofey

Forum User
Full Member
Registered: 18/03/05
Posts: 213
Location:Dublin, Ireland
thoughtful
Thanks Dirk.

Clearly I mustn't have updated the files correctly then.

Say I have an old and a new directory which I call:

/geeklog-1.4.1 and /geeklog-1.5.1

In this case should I be putting the old files into the new directory or the new files into the old directory to upgrade?

Shane
Those who say it can't be done, are usually interrupted by others doing it.

Status: offline

ofey

Forum User
Full Member
Registered: 18/03/05
Posts: 213
Location:Dublin, Ireland
thoughtful
I downloaded geeklog-1.5.0 and opened the tarball, but there is no admin/ directory in it and therefore no /install/install.php or install/index.php

Shouldn't the /admin directory be in gl-1.5.0 or is this because there is a new install script?

I tried the same with gl-1.5.1 and have the same problem?

Shane
Those who say it can't be done, are usually interrupted by others doing it.

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
I can assure you that there is an admin directory in all the complete tarballs (the ones that are around 4 MB in size). Sounds like a problem with whatever you're using to unpack the tarballs ...

bye, Dirk

All times are EDT. The time is now 12:06 pm.

  • Normal Topic
  • Sticky Topic
  • Locked Topic
  • New Post
  • Sticky Topic W/ New Post
  • Locked Topic W/ New Post
  •  View Anonymous Posts
  •  Able to post
  •  Filtered HTML Allowed
  •  Censored Content