Page 1 of 2

Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sat Apr 13, 2019 10:48 pm
by rodndtube
Reference Instructions in:
https://www.phpbb.com/support/docs/en/3 ... /upgrade3/

Current: phpBB 3.0.14, MySQL 5.5.59, PHP 5.6.40
Target: phpBB 3.2.5, same MySQL, PHP 7.2x (plan to have hosting service provider update after phpBB upgrade)

I've had some issues with the AUTOMOD the past few years. The AUTOMOD tab in Administration Control Panel indicates there are no installed MODS detected. It shows 3 uninstalled MODs:
Activation Justification, Add Homepage Link in Header, and Favicon 1.0.2. However, I believe the Activation Justification might still be working as I do receive emails with a justification statement with the option to look at the person's profile and written justification.
Image

When attempting to update the phpBB from 3.0.14 a couple of years ago I ran into problems so just copied my backup files and the forum was working again. It appears that 3.2.5 might be a semi-fresh restart, but then again maybe not. My attempt earlier today to install the The Support Toolkit was unsuccessful--I had hoped to use it to clean out any installed/unistalled MODS.

So, back to the primary question in the posting:

I have some questions regarding the updating of the database.
1. Backup of the database:
1.a. Backup type: Full, Structure only, or Data only?
1.b. File type: gzip or text?
1.c. Action: Store file locally or Download? (Or both?)

2. Restore the database:
2.a. Restore from server is better than from my hard drive? And it restores the choice from 1.a. above?
2.b. Per directions, "For large boards, you may wish to update via the command line instead of using a web browser. From your board's root, execute the following command: php ./bin/phpbbcli.php db:migrate --safe-mode "

The part about the command line is all Greek to me:
2.b.1. Where is the command line, in my FTP program? See below screenshots.
2.b.2. Is the first part of the commend entered php<space>.bin/phpbbcli.php db:migrate --safe-mode
-- use "php" or some thing else here
-- be sure there is a space before the .bin/ ?

FileZilla
Image

Menu | Server | Enter custom command
Image

Manual Transfer
Image

Thank you in advance for your patience and assistance.

Re: Updating the DB for transition from phpBB 2.0.14 to 3.2.5

Posted: Sat Apr 13, 2019 10:57 pm
by tbackoff
rodndtube wrote:
Sat Apr 13, 2019 10:48 pm
1. Backup of the database:
1.a. Backup type: Full, Structure only, or Data only?
1.b. File type: gzip or text?
1.c. Action: Store file locally or Download? (Or both?)
1.a) I would do a full backup.
1.b) Your preference.
1.c) In case something happens, download (or both).
rodndtube wrote:
Sat Apr 13, 2019 10:48 pm
The part about the command line is all Greek to me:
2.b.1. Where is the command line, in my FTP program? See below screenshots.
2.b.2. Is the first part of the commend entered php<space>.bin/phpbbcli.php db:migrate --safe-mode
-- use "php" or some thing eFFlse here
-- be sure there is a space before the .bin/ ?
2.b.1) This would be in a SSH window to your server. If you don't have SSH access, don't worry about it.
2.b.2) Correct command is php bin/phpbbcli.php --safe-mode db:migrate. Spaces between php and bin, .php and --safe, mode and db.

Hope that helps!

Edit: A note about FileZilla, make sure that "Treat files without extension as ASCII file" is not checked. It could screw up any attachments you might have on your board. See Knowledge Base - Transferring attachment files with Filezilla.

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 12:57 am
by Lumpy Burgertushie
you need full database backup just in case.
I would download it just in case.

download all the old files and folder from your ftp just in case.

you need to remove all parts of all MODs before you start.

what problem did you have with the STK?

part of the upgrade is removing all the old files except for those noted in the instructions and uploading all new files.

basically, once you have run the database cleaner in the STK and made your backups ,you just follow those upgrade instructions exactly and in order and you should be fine.


robert

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 2:50 am
by rodndtube
Lumpy Burgertushie wrote:
Sun Apr 14, 2019 12:57 am
you need to remove all parts of all MODs before you start.

what problem did you have with the STK?

part of the upgrade is removing all the old files except for those noted in the instructions and uploading all new files.

basically, once you have run the database cleaner in the STK and made your backups ,you just follow those upgrade instructions exactly and in order and you should be fine.
robert
I will try to reinstall the STK again and then take a screen shot of the errors.

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 12:54 pm
by Prosk8er
rodndtube wrote:
Sun Apr 14, 2019 2:50 am
I will try to reinstall the STK again and then take a screen shot of the errors.
just copy only the stk folder from the support toolkit zip file to your forum root and browse to http://yoursite.com/stk

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 1:28 pm
by rodndtube
The error message when attempting to access the STK, image and text versions:

Image

General Error
Language file ./language/en/en/common.php couldn't be opened.

BACKTRACE


FILE: (not given by php)
LINE: (not given by php)
CALL: stk_msg_handler()

FILE: [ROOT]/includes/session.php
LINE: 2112
CALL: trigger_error()

FILE: [ROOT]/includes/session.php
LINE: 2071
CALL: user->set_lang()

FILE: [ROOT]/stk/includes/functions.php
LINE: 350
CALL: user->add_lang()

FILE: [ROOT]/stk/index.php
LINE: 32
CALL: stk_add_lang()

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 2:17 pm
by stevemaury
Is that file present? If so, what are its CHMOD permissions. If not, upload it from a 3.0.14 download and set its permissions to 644.

See https://www.phpbb.com/support/docs/en/3 ... rmissions/

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 2:37 pm
by Lumpy Burgertushie
why is it looking for language/en/en/common.php

it should be looking for language/en/common.php


robert

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 3:16 pm
by stevemaury
Kind of a kludge, but try putting a copy on the en folder inside the en folder. Somewhere, probably in the database, there is a repetition.

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 4:01 pm
by rodndtube
I, too, was wondering about the /en/en double entry.

So, the permission was changed from 604 to 644 and I added another /en folder inside the /en folder. Only one error now:

General Error
Language file ./language/en/en/common.php couldn't be opened.

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 4:31 pm
by Lumpy Burgertushie
did you put a copy of the common.php file in that extra en folder?

robert

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 4:43 pm
by stevemaury
What are the permissions of /en/en/common.php?

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 5:49 pm
by rodndtube
The permissions:

Image

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Sun Apr 14, 2019 6:53 pm
by stevemaury
Run this SQL and post the result Executing SQL Queries in phpMyAdmin . If your table prefix is not phpbb_ change accordingly.

Code: Select all

SELECT config_value FROM phpbb_config WHERE config_name = 'default_lang'

Re: Updating the DB for transition from phpBB 3.0.14 to 3.2.5

Posted: Thu Apr 18, 2019 10:30 pm
by rodndtube
The results from the query:

Current selection does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available.

Showing rows 0 - 0 (1 total, Query took 0.0004 seconds.)

SELECT config_value FROM phpbb_config WHERE config_name = 'default_lang'



en