Project

General

Profile

Actions

Bug #47746

closed

Converting 4.7 sites to 6.1 sites much to complicated and breaking - white pages in Install tool

Added by Andreas Becker (Andi) about 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Install Tool
Target version:
-
Start date:
2013-04-30
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

When you try to convert an existing site which is 4.7 and which has an updated set of extensions it is leading to white pages and follows an unlogical order of steps, even when you try to call the Install Tool. The ONLY way to get it working sufficiently is to disable the localconf.php i.e. rename it. Than TYPO3 thinks there is no localconf and will try to install a new site and new localConfiguration.php file.

You skip the 123 process.
Now you can create a new Encryption Key which won't work
Bug #47738

Now you need to enter your db details.

The database can now be changed also in All Configuration - scroll down complete to the bottom - This point should be the first point and not the last as without DB Typo3 won't work - so it is the most important part!
Task #47740

With the next reload you will get a complete white page and inaccessible system.

You have no way to get to the screen to choose to enter your DB - best do it manually with an editor in localConfiguration.php

You need to clear typo3temp folder completely - remove and make it new setting the right permissions is fastest way.

Now you can access again the install tool.

Unfortunately it will show you again a white screen.

typo3/install/index.php?TYPO3_INSTALL[type]=config

This is even you have only the standard default extensions and none of your extensions installed!
Check Bug #47730

or you get i.e.
Fatal error: Call to a member function fetch_object() on a non-object in /typo3_src-6.1.0/typo3/sysext/core/Classes/Database/DatabaseConnection.php on line 1289

even your front and backend of the site is working
Bug #47744

a solution is to change the word "config" to "about" and wow - the installtool will show up.
typo3/install/index.php?TYPO3_INSTALL%5Btype%5D=about

Now you can perform the Upgrade Wizard which is in Menu at 4th place but should actually be on FIRST place after an Upgrade IMHO
Task #47729

If you will do a database compare usually your compare will time out!!!

Solution is to perform the upgrade wizard first or to perform the update after an database compare in many smaller parts.

we recommend doing /index.php?TYPO3_INSTALL[type]=update first:

It will ask you to change the version from 3.8 to 6.1 - it is telling 3.8 as it had no previous localconf file anymore as this did not work at all for the upgrade.

Than it is switching forth and back between step 2 and 3 which is complete unlogical as if people in TYPO3 can't count!
Why not name it 1 2 3 4 5 6 etc. This would also be much easier to communicate to people when something went wrong!
Bug #47732

By default TYPO3 is trying to force you to install the following extensions which should NOT be checked by default!

Frontend Editing
User>Open Documents
Recycler
Scheduler
Simulate Static URLs (which will bring you in conflict with all those people who actually are running cooluri and realURL!)
Bug #47733

In the next point you get forced to install workspaces and versioning - no way around beside skipping the wizard. You have to install both by default as there is no option for installing i.e. only versioning.
Bug #47734
This point should be removed from the installtool like the previous one for installing the system extensions.

When you go back to the install tool than again you get offered to install those useless extensions if you haven't used them in an existing site. They can be installed later!

We continue with point 3 in the list the FAL stuff and following

When you perform th elast point in th elist which is: Migrate all file relations from tt_content.image and pages.media
don't get confused if it says: "

Migrate all file relations from tt_content.image and pages.media

Update successful!

It will ask you again to perform this update
Bug #47736

We click manually on "Upgrade Wizard and than ignore all offered steps as those are steps which should not appear in an install tool or have already been performed.z

We choose the last step Final Step Compare Database

Here you will see that in the upgrade wizard was no step which actually created the last 3 missing tables

select/deselect all

CREATE TABLE sys_category ( uid int(11) NOT NULL auto_increment, pid int(11) NOT NULL default '0', tstamp int(11) NOT NULL default '0', crdate int(11) NOT NULL default '0', cruser_id int(11) NOT NULL default '0', deleted tinyint(4) NOT NULL default '0', hidden tinyint(4) NOT NULL default '0', starttime int(11) unsigned NOT NULL default '0', endtime int(11) unsigned NOT NULL default '0', t3ver_oid int(11) NOT NULL default '0', t3ver_id int(11) NOT NULL default '0', t3ver_wsid int(11) NOT NULL default '0', t3ver_label varchar(30) NOT NULL default '', t3ver_state tinyint(4) NOT NULL default '0', t3ver_stage int(11) NOT NULL default '0', t3ver_count int(11) NOT NULL default '0', t3ver_tstamp int(11) NOT NULL default '0', t3ver_move_id int(11) NOT NULL default '0', t3_origuid int(11) NOT NULL default '0', sys_language_uid int(11) NOT NULL default '0', l10n_parent int(11) NOT NULL default '0', l10n_diffsource mediumblob NOT NULL, title tinytext NOT NULL, description text NOT NULL, parent int(11) NOT NULL default '0', items int(11) NOT NULL default '0', PRIMARY KEY (uid), KEY parent (pid), KEY t3ver_oid (t3ver_oid,t3ver_wsid) );

CREATE TABLE sys_category_record_mm ( uid_local int(11) NOT NULL default '0', uid_foreign int(11) NOT NULL default '0', tablenames varchar(255) NOT NULL default '', sorting int(11) NOT NULL default '0', sorting_foreign int(11) NOT NULL default '0', KEY uid_local_foreign (uid_local,uid_foreign), KEY uid_foreign_tablenames (uid_foreign,tablenames) );

CREATE TABLE static_tsconfig_help ( uid int(11) NOT NULL auto_increment, guide int(11) NOT NULL default '0', md5hash varchar(32) NOT NULL default '', description text, obj_string varchar(255) NOT NULL default '', appdata blob, title varchar(255) NOT NULL default '', PRIMARY KEY (uid), KEY guide (guide,md5hash) );

----
Bug #47737

Performing a "write to database" might lead to a timeout

Solution: do it step by step and IMPORTANT create FIRST the still missing tables which have not been created by the Upgrade Wizard.

If you want to reactivate all your extensions you should delete NONE of them at this point.

----
Continue with configuring TYPO3

Don't click on Basic Configuration as it still leads you to a blank page at this point.
----

Check the image processing
Do it as it will motivate you as it will work instantly especially if you have installed gm


Do in all Configuration all necessary steps like in former versions


Logging into Backend:

If you previously used rsa than you have to create a new user as the extension for this authentification methode won't be available for your first login!

After creating a new user you can start reinstalling your extensions

i.e. templavoila and framework for templaVoila 2.0.0a1 which is working in 6.1. You can later configure it to use the rendering mode of version 1 via TYPOscript
Unfortunately realurl, wecconfig, weccontentelements, is not working!

framework for templaVoila Version 1.* seems not to be working

If an Extensions leads to a blank page or similar deinstall it manually from localConfiguration file and additionally delete manually the typo3temp/Cache Folder as the link in Install Tool to delete the .temp files seems still to try to delete the now nonexisting .temp files in typo3conf.
Bug #47741

After Installing extensions you might get the following message
"More information regarding this error might be available online."
But there is usually no information but a blank page
Bug #47742

----
After you have reinstalled the previous extensions

Hopefully enjoy 6.1


Related issues 11 (0 open11 closed)

Related to TYPO3 Core - Bug #48138: Cannot connect to the current databaseClosedOliver Hader2013-05-13

Actions
Related to TYPO3 Core - Bug #47737: 3 Tables don't get created by upgrade WizardClosed2013-04-30

Actions
Related to TYPO3 Core - Bug #47738: Encryption Key could not get created in new siteClosed2013-04-30

Actions
Related to TYPO3 Core - Task #47740: Move $TYPO3_CONF_VARS['DB'] to the TOP of All ConfigurationClosed2013-04-30

Actions
Related to TYPO3 Core - Bug #47730: After update from 4.7 - White Page in Install ToolClosed2013-04-30

Actions
Related to TYPO3 Core - Bug #47744: Fatal error: Call to a member function fetch_object() on a non-object in ClosedAlexander Opitz2013-04-30

Actions
Related to TYPO3 Core - Task #47729: Upgrade Wizard in Install Tool at the wrong Position (unlogical)Closed2013-04-30

Actions
Related to TYPO3 Core - Task #47732: Upgrade Wizard: Headlines start with wrong numbersClosed2013-04-30

Actions
Related to TYPO3 Core - Bug #47733: Don't set extensions checked by default in InstallSysExtsUpdateClosed2013-04-30

Actions
Related to TYPO3 Core - Bug #47736: Migrate all file relations from tt_content.image ... buttom missingClosed2013-04-30

Actions
Related to TYPO3 Core - Bug #47741: Cached files don't get deleted by install toolClosed2013-04-30

Actions
Actions

Also available in: Atom PDF