mike=). wrote:1. will I be doing all the work online (remote), or can some be done locally?[/quote[
It is intended to be done online, but it is possible to do locally if you run into timeout limits set by your hosts.
This article describes how: Knowledge Base - Offline Conversions
It is ALL the dynamic content of your board. Users, posts, PMs, forum names.2. what is the database exactly? Is that the memberlist (nick+passwords), the posts made, the appearance of the forum (look, layout etc.) or the software itself?
phpBB3 uses UTF, which supports all standard fonts, including cyrillic.3. cyrillic font is neccesary for the forum. Does this have to be added seperately?
[/quote]4. I have a site redirect for domain.ru -> domain.com. The forum does not. Can this be implemented, i so how and when?
Which database should I prepare? If I want to prepare the ../forum1/ database online, then surely I will need the "install" directory online (ie at remote)? Not sure of next step.Start by downloading the v2.0.23 files, and run the "install/update_to_latest.php" script you will find in the archive. That will prepare your database for the upgrade to 3.0.
You will have to set up a second database, and copy the information across if you want to do the update to .23 in parallel.mike=). wrote: Ideally, I would want to setup an identical forum parallel to the existing one, with the update software, renamed as http: //www.domain.com/forum1. Then debug, check the skins, and finally when all is ok, replace the database of forum1 with the up-to-date database of ../forum, then "throw the switch" (ie re-name/replace ../forum with ../forum1). This should avoid messy re-directs and 'under construction' pages for the next weeks. Please let me know if this approach wiil NOT work.
"The archive" means the ZIP file. It will have contained a folder called "install", which contained a file called "update_to_latest.php"espicom: I have downloaded the phpBB v.2.0.23 zip from forgesource. There is no 'archive' directory. The best I can find is an "update_to_latest" file in the "install" directory. So ignoring the "install" and "upgrade" files.
Did the backup appear to complete normally? No frozen screens?To make the database backup, I have gone to Database Utilities : Backup in the phpBB administration section. Then selected the options: "full backup" YES, "additional tables" NONE, "Gzip compress file" NO.
The file is stored on my local machine as phpbb_db_backup.sql .
Both your boards are accessing the same database right now!I have copied the /domain.com/html/forum/ directory and renamed /domain.com/html/forum1/. This will be the one I'm working on. Checked, ../forum1/ is fully functional. The other one is hard-linked to the rest of the website. Screencap included of the ../forum1/ directory.
Which database should I prepare? If I want to prepare the ../forum1/ database online, then surely I will need the "install" directory online (ie at remote)? Not sure of next step.Start by downloading the v2.0.23 files, and run the "install/update_to_latest.php" script you will find in the archive. That will prepare your database for the upgrade to 3.0.
(please be patient with me...I'm doing my best, and trying to understand things correctly at the same time).
I'll be doing it on remote. 2 reasons: 1) I am flat out of memory on my main PC, and I have an .htaccess problem to resolve before I can use Apache. 2) the site is hosted on a fast dedicated server, with easy access.ric323 wrote:You will have to set up a second database, and copy the information across if you want to do the update to .23 in parallel.mike=). wrote: Ideally, I would want to setup an identical forum parallel to the existing one, with the update software, renamed as http: //www.domain.com/forum1. Then debug, check the skins, and finally when all is ok, replace the database of forum1 with the up-to-date database of ../forum, then "throw the switch" (ie re-name/replace ../forum with ../forum1). This should avoid messy re-directs and 'under construction' pages for the next weeks. Please let me know if this approach wiil NOT work.
It is possible to do it all on your own PC. Have a look at Knowledge Base - Offline Conversions
The backup appears to be ok. I'll make a few more watching for timeouts, and checking file-sizes. I probably won't need the backup anyway, as there are now two databases on remote, and one downloaded by ftp on local.ric323 wrote:Did the backup appear to complete normally? No frozen screens?To make the database backup, I have gone to Database Utilities : Backup in the phpBB administration section. Then selected the options: "full backup" YES, "additional tables" NONE, "Gzip compress file" NO.
The file is stored on my local machine as phpbb_db_backup.sql .
(The built in backup facility is prone to timeout errors, which would give you a truncated backup. This article says how to do it with phpMyAdmin. Knowledge Base - How to move a phpBB 2.0.x board to a new server
As I will be working with the forum software on remote, am I correct in assuming that there is no point in having two forum databases (public and 'beta')?ric323 wrote:Both your boards are accessing the same database right now!I have copied the /domain.com/html/forum/ directory and renamed /domain.com/html/forum1/. This will be the one I'm working on. Checked, ../forum1/ is fully functional. The other one is hard-linked to the rest of the website. Screencap included of the ../forum1/ directory.
Which database should I prepare? If I want to prepare the ../forum1/ database online, then surely I will need the "install" directory online (ie at remote)? Not sure of next step.Start by downloading the v2.0.23 files, and run the "install/update_to_latest.php" script you will find in the archive. That will prepare your database for the upgrade to 3.0.
(please be patient with me...I'm doing my best, and trying to understand things correctly at the same time).
I think a duplicate seperate database for the second phpBB2 board is what I have now.ric323 wrote:If you want to work completely independant of your original board, then you need a duplicate seperate database for the second phpBB2 board (and you will then need a third database for the phpBB3 board).
I say this because the update_to_latest script modifies the database. The 2.0.17 board shouldn't mind that this has happened, but it won't be maintaining the extra fields correctly, so you are safest to experiment with a totally seperate database.
The URL of the board says nothing about what database it is using, that is controlled by the config.php file in each of those addresses. If you just copied config.php from the first board to the second board, then they ARE using the same database. The database is NOT stored inside the folder.mike=). wrote:I think a duplicate seperate database for the second phpBB2 board is what I have now.
The first: http: //www.domain.com/forum/
The second: http: //www.domain.com/forum1/
I copied the entire forum directory by ftp, then renamed and added to remote.ric323 wrote:The URL of the board says nothing about what database it is using, that is controlled by the config.php file in each of those addresses. If you just copied config.php from the first board to the second board, then they ARE using the same database. The database is NOT stored inside the folder.mike=). wrote:I think a duplicate seperate database for the second phpBB2 board is what I have now.
The first: http: //www.domain.com/forum/
The second: http: //www.domain.com/forum1/