Welcome to Geeklog Friday, February 23 2018 @ 11:32 am EST


Status: offline

OMAL

Forum User
Junior
Registered: 06/12/2017
Posts: 15
I'll upgrade my geeklog site from v.1.4 on php ver.5.4 to the latest version on php ver.7.
Geeklog ver.1.4 does not support PHP ver.7, and latest version does not support php ver.5.4.
It would be really appreciated if you have some advice for this situation. Wink

Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/2005
Posts: 1257
First thing I would do is make sure to backup all of your files and MySQL database. That is quite a version jump between 1.4 and 2.1.3.

I would also disable all plugins you are using that are not core plugins (plugins that come with the geeklog install) as if they don't support PHP 7 they could error out and ruin the upgrade.

I would then upgrade your PHP to version 7. The current 1.4 site may not work but once you copy over the new files, the install will work just fine along with the upgrade process.

Tom


One of the Geeklog Core Developers.

Status: offline

OMAL

Forum User
Junior
Registered: 06/12/2017
Posts: 15
Thanks.I'm relieved to hear that.
That is What I'm going to trying to do.

Status: offline

OMAL

Forum User
Junior
Registered: 06/12/2017
Posts: 15
Another question.

When I use installer to upgrade my site, what the installer can handle and inherit to automatically upgrade the site is only config.php file of my current site, is it right? Geeklog's manual for site update says like that.
From that information, I think installer only handle config.file and I have to deal with all the other upgrading process after the install.
Am I missing some thing? Anything else they can handle to upgrade site except for config.php?

Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/2005
Posts: 1257
The latest install should be able to handle the config file fine. It should convert the required config values and store them in the database. Copy over the new install files and make sure you remove the old ones not used anymore except leave the config.php files so the upgrade can grab the require information. Once the upgrade is complete you can then remove that old config.php file

It has been a long while since I have dealt with such an old install like 1.4.1. As I said before backup everything before hand incase you need to redo the upgrade process again incase something errors out.



One of the Geeklog Core Developers.

Status: offline

OMAL

Forum User
Junior
Registered: 06/12/2017
Posts: 15
When I open install/index.php on a browser, following message appears:
Geeklog Installation

Unable to locate Geeklog files

The installer was unable to locate critical Geeklog files. This is probably because you have moved them from their default location. Please specify the paths to the files and directories below:

db-config.php

I can configure path here, but I am worried about the term "db-config.php", because I have now two configuration files in geeklog directory, config.php from my site and db-config.php from downloaded zip.

I tried to indicate config.php file, then, the following error occurs:

ERROR The path /***/private/config.php/db-config.php does not appear to be correct. Please go back and try again.


So, the name config.php seems not be acceptable for the installer.
Then I ignored config.php file and instead entered db-config.php path. That is "/***/private/" or "/***/private/db-config.php", both result in same status in step2.
Next, I chose upgrade, then the third page(step 2) displays form for site configuration. Here, all default data does not reflect my config.php file, instead, just "site_name: Geeklog Site" for example, not my site name.

The latest install should be able to handle the config file fine.

The installer is the latest version but from Japanese site, so it is possibly lack of the handling ability.

Do you think which is better, modifying db-config file manually before working with the installer or after working with that?

thanks.

Status: offline

OMAL

Forum User
Junior
Registered: 06/12/2017
Posts: 15
I ignored config.php on Step1 and Step2, input data such as host_name, then on next page, errors are displayed. That error include the word "config.php", so it is used. But the errors was weird. That says the installer warns like "Fatal error: 1051: Unknown table 'mydb.gl_****' in /****/private/system/databases/mysqli.class.php on line 469".
After that error, some of tables in my database seems to be DELETED on the installation process.
I'll check it out later about this issue.
Now I think, placing config.php in the geeklog system directory before installation process is bad idea, and I should overwrite configuration with config.php after the installer complete the installation.

PS. When installer worked, my local test system seemed to be crushed and db was destroyed, it may be the cause of weird errors.

Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/2005
Posts: 1257
The installer shouldn't be deleting tables unless they are not needed anymore. In most cases it will just be altering tables to either change or add table columns as needed.

Try the install without the config.php and

rename the db-config.php.dist to db-config.php

and the siteconfig.php.dist found in public_html to siteconfig.php
One of the Geeklog Core Developers.

remy

Anonymous
Quote by: Laugh

The installer shouldn't be deleting tables unless they are not needed anymore.



What's the condition to decide that tables are
not needed anymore
?

How would you know ?


Status: offline

Laugh

Site Admin
Admin
Registered: 27/09/2005
Posts: 1257
Well the installer uses the update scripts found in the directory \sql\updates so you would have to look in those to figure it out.

I believe Geeklog 1.4.1 was released over 10 years ago so If memory serves no tables should be deleted since 1.4.1 but tables have been added and modified since then (along with the data in them.
One of the Geeklog Core Developers.

All times are EST. The time is now 11:32 am.

  • 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