[TYPO3-english] Typo3 4.5.11 to 6.2 Upgrade

Discussion:

Wiesław Golsz

2016-05-06 14:27:22 UTC

Hello, I have problem - I can't choose the database (step 3). I can open
a list of databases, but they are inactive. Likewise, I can not create a
new database. Regards, Wieslaw

Mark Boland

2016-05-06 14:50:19 UTC

Permalink

Hi Wieslaw,

do you want to upgrade or start from scratch?

If you do want to upgrade, update your 4.5 installation to the latest version first (4.5.40), then follow one of the step-by-step instructions available on the net or in the archives of this mailing list.

What you describe is instead the 1-2-3 installation screen for new installations.

Cheers,

Mark

Post by WiesÅaw Golsz
Hello, I have problem - I can't choose the database (step 3). I can open
a list of databases, but they are inactive. Likewise, I can not create a
new database. Regards, Wieslaw
_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Wiesław Golsz

2016-05-06 15:14:52 UTC

Permalink

Thank you very much Mark,

This is not a problem of the "last" version 4.5 - I use 4.5.11

The first problem - creation typo3_src symlink

My admin solved the problem, but temporarily - with SSH.

I have tried to recreate the symlinks suggested at:
https://docs.typo3.org/typo3cms/InstallationGuide/QuickInstall/GetAndUnpack/Index.html

and some other notification have appeared at:
http://6.domain.com/typo3_src-6.2.22/typo3/sysext/install/Start/Install.php

Therefore, my question is whether the installation (upgrade to 6.2) is
possible without SSS?

Second problem - on the 3 (of 5 stages) appears in a standard window:
/Select database, you have two options: Select, use an existing empty
database/: etc. But I can not make a selection and choose a specific
database. It is gray and "dead", no response. The same I can not create
a new database.

Cheers,

Post by Mark Boland
Hi Wieslaw,
do you want to upgrade or start from scratch?
If you do want to upgrade, update your 4.5 installation to the latest version first (4.5.40), then follow one of the step-by-step instructions available on the net or in the archives of this mailing list.
What you describe is instead the 1-2-3 installation screen for new installations.
Cheers,
Mark

_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Mark Boland

2016-05-06 15:29:27 UTC

Permalink

Hi Wieslaw,

the Symlink is not mandatory. The one Symlink that your admin created for you will suffice if you always upload new updates via FTP into the same folder (e.g. ’typo3_src/‚).

What I asked of you is if you want to do an in-place upgrade from 4.5 to 6.2, because you would then first want to update the ‚old‘ installation to the latest available, as there were minor changes in the database from .11 to .40 that are needed for a smooth transition to 6.2. These are missing in the 6.2 package and that will probably cause an unstable system.

If you are doing an in-place update you won’t be asked for your database credentials anyway.

If you followed the upgrade instructions, you already updated all used 3rd party extensions to the highest version supported by 4.5 and switched them off before upgrading?

Cheers,

Mark

Post by WiesÅaw Golsz
Thank you very much Mark,
This is not a problem of the "last" version 4.5 - I use 4.5.11
The first problem - creation typo3_src symlink
My admin solved the problem, but temporarily - with SSH.
https://docs.typo3.org/typo3cms/InstallationGuide/QuickInstall/GetAndUnpack/Index.html
http://6.domain.com/typo3_src-6.2.22/typo3/sysext/install/Start/Install.php
Therefore, my question is whether the installation (upgrade to 6.2) is
possible without SSS?
/Select database, you have two options: Select, use an existing empty
database/: etc. But I can not make a selection and choose a specific
database. It is gray and "dead", no response. The same I can not create
a new database.
Cheers,

_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Wiesław Golsz

2016-05-06 20:14:16 UTC

Permalink

Hi,

According suggestions, I update to Typo3 to v4.5.40 and tried to upgrade
to 6.2. but received this same error -

/Oops, an error occurred! TYPO3 Fatal Error: No database selected!

'DB' => array(
'extTablesDefinitionScript' => 'extTables.php',
'host' => 'localhost',
'password' => 'mypassword',
'port' => 3306,
'username' => 'db_username',
/
No db name. How I can set my db in /LocalConfiguration.php/?

Can you help me? Wieslaw

Post by Mark Boland
Hi Wieslaw,
the Symlink is not mandatory. The one Symlink that your admin created for you will suffice if you always upload new updates via FTP into the same folder (e.g. ’typo3_src/‚).
What I asked of you is if you want to do an in-place upgrade from 4.5 to 6.2, because you would then first want to update the ‚old‘ installation to the latest available, as there were minor changes in the database from .11 to .40 that are needed for a smooth transition to 6.2. These are missing in the 6.2 package and that will probably cause an unstable system.
If you are doing an in-place update you won’t be asked for your database credentials anyway.
If you followed the upgrade instructions, you already updated all used 3rd party extensions to the highest version supported by 4.5 and switched them off before upgrading?
Cheers,
Mark

_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Mark Boland

2016-05-06 20:37:34 UTC

Permalink

You ARE upgrading in-place, don't you? You are installing 6.2 in the same folder that you had for the 4.5 installation? If yes, 6.2 will get the details of your DB connection from localconf.php, convert it, and write it back to LocalConfiguration.php.

To start the upgrade, you invoke the install tool (with /typo3/install) in your browser and follow the instructions under Upgrade. Backend and Frontend will not work until you finished the process.

Detailed instruction can be found in the Wiki [1].

If you go through the 1-2-3 installer instead, you will get a completely new configuration (separate database, separate settings). Your page tree will then be empty.

Have a nice weekend

Mark

[1] https://docs.typo3.org/typo3cms/InstallationGuide/6.2/Upgrade/Index.html

Post by WiesÅaw Golsz
Hi,
According suggestions, I update to Typo3 to v4.5.40 and tried to upgrade
to 6.2. but received this same error -
/Oops, an error occurred! TYPO3 Fatal Error: No database selected!
'DB' => array(
'extTablesDefinitionScript' => 'extTables.php',
'host' => 'localhost',
'password' => 'mypassword',
'port' => 3306,
'username' => 'db_username',
/
No db name. How I can set my db in /LocalConfiguration.php/?
Can you help me? Wieslaw

_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Jigal van Hemert

2016-05-07 08:32:46 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
According suggestions, I update to Typo3 to v4.5.40 and tried to upgrade
to 6.2. but received this same error -
/Oops, an error occurred! TYPO3 Fatal Error: No database selected!
'DB' => array(
'extTablesDefinitionScript' => 'extTables.php',
'host' => 'localhost',
'password' => 'mypassword',
'port' => 3306,
'username' => 'db_username',
/
No db name. How I can set my db in /LocalConfiguration.php/?

'DB' => array(
'database' => 'typo3_62',
'extTablesDefinitionScript' => 'extTables.php',
'host' => '*******',
'password' => '*******',
'port' => 3306,
'username' => '******',
),

Note that in 4.x you can add settings and code to localconf.php and they
were preserved if you changed settings in the Install Tool. In 6.2 the
LocalConfiguration.php file is completely rewritten with each change
(changed setting in Install Tool, changes in installed extensions, ...).

If you need complicated code to make settings in your installation you
can add these to a file "AdditionalConfiguration.php" in the same
directory as LocalConfiguration.php

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-07 15:36:13 UTC

Permalink

After doing the upgrade I am in the admin panel, I did DB check (update
reference index) all wass ok.

Now I tred install Calendar Base (cal_1.5.9). It was removed during the
upgrade from 4.5.40 to 6.2.

I receive an error:

/Fatal error: require_once() [function.require]: Failed opening required
'PATH_t3libclass.t3lib_treeview.php'
(include_path='/home/www/6.bestchoicefx.com/typo3/contrib/pear/:.:/usr/local/php5.3/lib//php')
in
/home/www/6.bestchoicefx.com/typo3conf/ext/cal/res/class.tx_cal_treeview.php
on line 63/

what can I do? Regards

_______________________________________________
TYPO3-english mailing list
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Jigal van Hemert

2016-05-07 17:25:49 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
After doing the upgrade I am in the admin panel, I did DB check (update
reference index) all wass ok.

The reference index should have been updated *before* the upgrade.
Upgrade wizards in the Install Tool may use this index to find relations
between records. But you're already past this point, so let's just hope
it wasn't too bad before you started the upgrade.

Post by WiesÅaw Golsz
Now I tred install Calendar Base (cal_1.5.9). It was removed during the
upgrade from 4.5.40 to 6.2.

If it was the Install Tool that removed it the reason was that the
Install Tool tried to load files from that extension that are also
loaded when you use the TYPO3 backend. It detected that it caused fatal
errors and offered you to uninstall the extension(s).

This would imply that the extension isn't compatible with TYPO3 6.2 and
you should not try to install it.
Luckily the authors of the extension published a version that is
compatible, so you can upgrade it to the latest version in the Extension
Manager before installing it.

First you have to uninstall it to get back into the backend:

1) If the Install Tool previously offered to uninstall it during the
upgrade the easiest solution is to go back to the Install Tool, open the
"Important actions" tab and use the button "Check extensions". This will
detect that the extension causes problems and offers the option to
uninstall the extension

2) If you removed it prior to the upgrade you can try the method
described above. If that doesn't help, use your (S)FTP tool and edit the
file typo3conf/PackageStates.php (be very careful, if this file is
damaged TYPO3 will replace it with a new one and most extensions
(including many system extensions) will be uninstalled; you can install
them again, it just takes some extra time). For each extension it
contains block like this:

'news' =>
array (
'manifestPath' => '',
'composerName' => 'georgringer/news',
'state' => 'active',
'packagePath' => 'typo3conf/ext/news/',
'classesPath' => 'Classes/',
'suggestions' =>
array (
),
),

(this is the block for the 'news' extension).
Find the block for 'cal' and change the value after 'state' into "inactive".
Upload the file.

Now you should be able to access the backend again.

Open the Extension Manager and see if there is an update icon in the
leftmost column "Upd.". If you hold the cursor above the icon it should
show a tooltip "Update to version 1.10.3". If that is the case you can
update the 'cal' extension to that version.

If it doesn't show that text, use the selectbox near the top to choose
the option "Get Extensions". This might take a while to load the
information of all extensions. It may also be necessary to use the
button "Update now" on the right side of the screen to import the latest
information of all extensions in TER; it shows how old the information is.
Use the search box to lookup the extension 'cal' and install that latest
version from here.

Hope that helps

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-07 18:42:32 UTC

Permalink

Thank you very much Jigal, OK done.

This time much more serious error. I use an application developed by
WEC. It is widely used in the network, but WEC support no longer exists.

It is very important ext "/WEC Site Config/" Site-wide configuration
module for constants, templates, and add-on features.
https://typo3.org/extensions/repository/view/wec_config

I get this error:

/Fatal error: require_once() [function.require]: Failed opening required
'PATH_t3libclass.t3lib_extobjbase.php'
(include_path='/home/www/6.bestchoicefx.com/typo3/contrib/pear/:.:/usr/local/php5.3/lib//php')
in
/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/features/class.tx_wecconfig_features.php
on line 31/

Q1. if anyone solved this problem (use for Typo3 6.2). Without "WEC Site
Config" it is possible not manage for example templates

Q2. Is there any alternative?

Q3. How to fix this error

Regards,
*
*

Post by Jigal van Hemert
Hi,

Post by WiesÅaw Golsz
After doing the upgrade I am in the admin panel, I did DB check (update
reference index) all wass ok.

The reference index should have been updated *before* the upgrade.
Upgrade wizards in the Install Tool may use this index to find
relations between records. But you're already past this point, so
let's just hope it wasn't too bad before you started the upgrade.

Post by WiesÅaw Golsz
Now I tred install Calendar Base (cal_1.5.9). It was removed during the
upgrade from 4.5.40 to 6.2.

If it was the Install Tool that removed it the reason was that the
Install Tool tried to load files from that extension that are also
loaded when you use the TYPO3 backend. It detected that it caused
fatal errors and offered you to uninstall the extension(s).
This would imply that the extension isn't compatible with TYPO3 6.2
and you should not try to install it.
Luckily the authors of the extension published a version that is
compatible, so you can upgrade it to the latest version in the
Extension Manager before installing it.
1) If the Install Tool previously offered to uninstall it during the
upgrade the easiest solution is to go back to the Install Tool, open
the "Important actions" tab and use the button "Check extensions".
This will detect that the extension causes problems and offers the
option to uninstall the extension
2) If you removed it prior to the upgrade you can try the method
described above. If that doesn't help, use your (S)FTP tool and edit
the file typo3conf/PackageStates.php (be very careful, if this file is
damaged TYPO3 will replace it with a new one and most extensions
(including many system extensions) will be uninstalled; you can
install them again, it just takes some extra time). For each extension
'news' =>
array (
'manifestPath' => '',
'composerName' => 'georgringer/news',
'state' => 'active',
'packagePath' => 'typo3conf/ext/news/',
'classesPath' => 'Classes/',
'suggestions' =>
array (
),
),
(this is the block for the 'news' extension).
Find the block for 'cal' and change the value after 'state' into "inactive".
Upload the file.
Now you should be able to access the backend again.
Open the Extension Manager and see if there is an update icon in the
leftmost column "Upd.". If you hold the cursor above the icon it
should show a tooltip "Update to version 1.10.3". If that is the case
you can update the 'cal' extension to that version.
If it doesn't show that text, use the selectbox near the top to choose
the option "Get Extensions". This might take a while to load the
information of all extensions. It may also be necessary to use the
button "Update now" on the right side of the screen to import the
latest information of all extensions in TER; it shows how old the
information is.
Use the search box to lookup the extension 'cal' and install that
latest version from here.
Hope that helps

Jigal van Hemert

2016-05-07 20:49:20 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
This time much more serious error. I use an application developed by
WEC. It is widely used in the network, but WEC support no longer exists.
It is very important ext "/WEC Site Config/" Site-wide configuration
module for constants, templates, and add-on features.
https://typo3.org/extensions/repository/view/wec_config
/Fatal error: require_once() [function.require]: Failed opening required
'PATH_t3libclass.t3lib_extobjbase.php'
(include_path='/home/www/6.bestchoicefx.com/typo3/contrib/pear/:.:/usr/local/php5.3/lib//php')
in
/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/features/class.tx_wecconfig_features.php
on line 31/

Most of the time these errors are not hard to fix, although it can take
some time if you encounter a lot of them each time you fix one.

In TYPO3 4.3 (if I remember correctly) a mechanism was introduced to
automatically load classes in PHP. This meant that you didn't need to
use lines like

require_once( PATH_t3libclass . 't3lib_extobjbase.php');

in your code. You could just use the class and it would automatically be
loaded.
Many extension authors still kept those lines because the code still
worked. In 6.x the autoloader was changed and these errors appeared if
extension code still used those unnecessary lines.

Post by WiesÅaw Golsz
Q3. How to fix this error

Look carefully at the error! It says that the require_once didn't work
in ....../ext/wec_config/features/class.tx_wecconfig_features.php on
line 31.

Edit the file and put two slashes in front of the 'require_once' on the
mentioned line. This turns the rest of the line into a comment and it
will no longer be executed. It will look a bit like:

//require_once( PATH_t3libclass . 't3lib_extobjbase.php');

(I don't know the exact line, but you get the idea)

Warning for the future:
- in 6.x all class names in the core were changed; the names are now
easier to read
- 6.2 still knows the old names like the existed in 4.5 and extensions
can still use the old names
- 7.6 doesn't know the old names anymore, but there is an extension
'compatibility6' which makes it possible to still use the old class
names; it comes with a price, performance is a lot worse with that
extension installed
- 8.x don't know the old names and there is no extension that adds
support for those old class names

You can use a lot of 4.x compatible extensions with 6.2, but it would be
wise to look for alternatives before upgrading to 7 LTS or 8.x.
Alternative would be to edit the extensions and replace all the old
class names with the new names. In some cases more code needs to be
replaced, but you could hire a TYPO3 programmer to make those changes.

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-07 21:32:42 UTC

Permalink

OK Jigaj, but next error in this code (class.tx_wecconfig_features.php):

/function countFeatures() {//
// global $TYPO3_DB;//
// //
// $table = 'tx_wecconfig_features';//
// $res = $TYPO3_DB->exec_SELECTquery ('count(uid)', $table,
'deleted=0');//
// $row = $TYPO3_DB->sql_fetch_assoc($res);//
//
// $count = $row['count(uid)'];//
// } else {//
// $count = 0;//
// }//
// return $count;//
// }/

Fatal error: Cannot access protected property
TYPO3\CMS\Core\Database\DatabaseConnection::$link in
/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/features/class.tx_wecconfig_features.php
on line 192

Where line 192 is: /if(is_object($TYPO3_DB) && $TYPO3_DB->link) {//
/

Post by Jigal van Hemert
Hi,

Most of the time these errors are not hard to fix, although it can
take some time if you encounter a lot of them each time you fix one.
In TYPO3 4.3 (if I remember correctly) a mechanism was introduced to
automatically load classes in PHP. This meant that you didn't need to
use lines like
require_once( PATH_t3libclass . 't3lib_extobjbase.php');
in your code. You could just use the class and it would automatically
be loaded.
Many extension authors still kept those lines because the code still
worked. In 6.x the autoloader was changed and these errors appeared if
extension code still used those unnecessary lines.

Post by WiesÅaw Golsz
Q3. How to fix this error

Look carefully at the error! It says that the require_once didn't work
in ....../ext/wec_config/features/class.tx_wecconfig_features.php on
line 31.
Edit the file and put two slashes in front of the 'require_once' on
the mentioned line. This turns the rest of the line into a comment and
//require_once( PATH_t3libclass . 't3lib_extobjbase.php');
(I don't know the exact line, but you get the idea)
- in 6.x all class names in the core were changed; the names are now
easier to read
- 6.2 still knows the old names like the existed in 4.5 and extensions
can still use the old names
- 7.6 doesn't know the old names anymore, but there is an extension
'compatibility6' which makes it possible to still use the old class
names; it comes with a price, performance is a lot worse with that
extension installed
- 8.x don't know the old names and there is no extension that adds
support for those old class names
You can use a lot of 4.x compatible extensions with 6.2, but it would
be wise to look for alternatives before upgrading to 7 LTS or 8.x.
Alternative would be to edit the extensions and replace all the old
class names with the new names. In some cases more code needs to be
replaced, but you could hire a TYPO3 programmer to make those changes.

Jigal van Hemert

2016-05-07 22:05:20 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
Fatal error: Cannot access protected property
TYPO3\CMS\Core\Database\DatabaseConnection::$link in
/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/features/class.tx_wecconfig_features.php
on line 192
Where line 192 is: /if(is_object($TYPO3_DB) && $TYPO3_DB->link) {//

You can safely remove the second condition:

if(is_object($TYPO3_DB)) {

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-08 08:37:42 UTC

Permalink

I took a few steps further and template is already active. But when I
try to open an error appears:

Oops, an error occurred!
TYPO3 Fatal Error: Extension key "tstemplate_ceditor" is NOT loaded!
In wiki:
https://wiki.typo3.org/Exception/CMS/1365429656

In LocalConfiguration.php
typo3conf/LocalConfiguration.php - array([EXT][extConf][your_extension_key])

I do not have this ("tstemplate_ceditor") array

Regards, Wieslaw

Post by Jigal van Hemert
Hi,

if(is_object($TYPO3_DB)) {

Jigal van Hemert

2016-05-08 11:07:44 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
I took a few steps further and template is already active. But when I
Oops, an error occurred!
TYPO3 Fatal Error: Extension key "tstemplate_ceditor" is NOT loaded!
https://wiki.typo3.org/Exception/CMS/1365429656
In LocalConfiguration.php
typo3conf/LocalConfiguration.php - array([EXT][extConf][your_extension_key])
I do not have this ("tstemplate_ceditor") array

That was the Constant Editor in TYPO3 4.5; in 6.2 it's rewritten. It
looks like the only thing needed are the icons in the gfx directory in
that (system) extension. You can very likely change two lines in
constants/class.tx_wecconfig_constants.php : lines 82 and 83 (in the
original file)

$tmpl->ext_localGfxPrefix = t3lib_extMgm::extPath('tstemplate_ceditor');
$tmpl->ext_localWebGfxPrefix =
$GLOBALS['BACK_PATH'].t3lib_extMgm::extRelPath('tstemplate_ceditor');

change them to:

$tmpl->ext_localGfxPrefix = t3lib_extMgm::extPath('tstemplate') .
'Resources/Public/';
$tmpl->ext_localWebGfxPrefix =
$GLOBALS['BACK_PATH'].t3lib_extMgm::extRelPath('tstemplate') .
'Resources/Public/';

You're brave to still hang in there :-) Let's see what problem pops up
next...

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-08 15:07:24 UTC

Permalink

Many thx Jigal,

Next step i next error, I hope that it's close to end.

*Fatal error*: Call to undefined method
TYPO3\CMS\Core\Utility\GeneralUtility::testInt() in
*/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/constants/class.tx_wecconfig_constants.php*
on line *139

*P.S. Sorry, I'm not a programmer, the last time something was
programming 40 years ago and in Fortran :-). In meantime, a little html
and similar.

Regards, Wieslaw*
*

Post by Jigal van Hemert
Hi,

Post by WiesÅaw Golsz
I took a few steps further and template is already active. But when I
Oops, an error occurred!
TYPO3 Fatal Error: Extension key "tstemplate_ceditor" is NOT loaded!
https://wiki.typo3.org/Exception/CMS/1365429656
In LocalConfiguration.php
typo3conf/LocalConfiguration.php -
array([EXT][extConf][your_extension_key])
I do not have this ("tstemplate_ceditor") array

That was the Constant Editor in TYPO3 4.5; in 6.2 it's rewritten. It
looks like the only thing needed are the icons in the gfx directory in
that (system) extension. You can very likely change two lines in
constants/class.tx_wecconfig_constants.php : lines 82 and 83 (in the
original file)
$tmpl->ext_localGfxPrefix = t3lib_extMgm::extPath('tstemplate_ceditor');
$tmpl->ext_localWebGfxPrefix =
$GLOBALS['BACK_PATH'].t3lib_extMgm::extRelPath('tstemplate_ceditor');
$tmpl->ext_localGfxPrefix = t3lib_extMgm::extPath('tstemplate') .
'Resources/Public/';
$tmpl->ext_localWebGfxPrefix =
$GLOBALS['BACK_PATH'].t3lib_extMgm::extRelPath('tstemplate') .
'Resources/Public/';
You're brave to still hang in there :-) Let's see what problem pops up
next...

Jigal van Hemert

2016-05-08 20:38:23 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
*Fatal error*: Call to undefined method
TYPO3\CMS\Core\Utility\GeneralUtility::testInt() in
*/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/constants/class.tx_wecconfig_constants.php*
on line *139

That function is now called:

\TYPO3\CMS\Core\Utility\MathUtility::canBeInterpretedAsInteger()

On line 139 you'll probably find t3lib_div::testInt(); the compatibility
layer directed the call to the new class name. This didn't work out in
this case as the function was moved.

Post by WiesÅaw Golsz
*P.S. Sorry, I'm not a programmer, the last time something was
programming 40 years ago and in Fortran :-). In meantime, a little html
and similar.

No problem. You are just unfortunate to need an extension that has no
suitable version for 6.2.

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-08 22:45:10 UTC

Permalink

Thx Jigal, if I understand correctly, it is not possible is to use "WEC
Site Config".

It is problem, becuse this ext is crucial, it allows to select - for
example - template. without that page looks like this:
http://6.bestchoicefx.com/

Is there ext. - consistent with 6.2, which in this regard replaces "WEC
Site Config"?

Regards

Post by Jigal van Hemert
Hi,

\TYPO3\CMS\Core\Utility\MathUtility::canBeInterpretedAsInteger()
On line 139 you'll probably find t3lib_div::testInt(); the
compatibility layer directed the call to the new class name. This
didn't work out in this case as the function was moved.

Post by WiesÅaw Golsz
*P.S. Sorry, I'm not a programmer, the last time something was
programming 40 years ago and in Fortran :-). In meantime, a little html
and similar.

No problem. You are just unfortunate to need an extension that has no
suitable version for 6.2.

Jigal van Hemert

2016-05-09 11:06:12 UTC

Permalink

Hi,

Post by WiesÅaw Golsz
Thx Jigal, if I understand correctly, it is not possible is to use "WEC
Site Config".

I didn't mean to say that. There isn't a version in TER that is
compatible with 6.2, but with the changes you are making it will
eventually become compatible.

The change for that fatal error would just be to replace the call to the
function testInt() with the function I mentioned (keep the parameters,
just change the entire function name (plus the path in front of it).

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-09 16:06:28 UTC

Permalink

Hi,

I change in line 139
if (t3lib_div::_POST('submit') ||
(*t3lib_div::testInt(*t3lib_div::_POST('submit_x')) &&
*t3lib_div::testInt(*t3lib_div::_POST('submit_y')))) {
to
if (t3lib_div::_POST('submit') ||
(*\TYPO3\CMS\Core\Utility\MathUtility::canBeInterpretedAsInteger(*t3lib_div::_POST('submit_x'))
&&
*\TYPO3\CMS\Core\Utility\MathUtility::canBeInterpretedAsInteger(*t3lib_div::_POST('submit_y'))))
{

Here it looks ok, but I received error in line 177:
$tmpl->ext_readDirResources($TYPO3_CONF_VARS['MODS']['web_ts']['onlineResourceDir']);

*Fatal error*: Call to undefined method
TYPO3\CMS\Core\TypoScript\ExtendedTemplateService::ext_readDirResources()
in
*/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/constants/class.tx_wecconfig_constants.php*
on line *177

*Already near the end?

Regards, Wieslaw

Post by Jigal van Hemert
Hi,

Post by WiesÅaw Golsz
Thx Jigal, if I understand correctly, it is not possible is to use "WEC
Site Config".

I didn't mean to say that. There isn't a version in TER that is
compatible with 6.2, but with the changes you are making it will
eventually become compatible.
The change for that fatal error would just be to replace the call to
the function testInt() with the function I mentioned (keep the
parameters, just change the entire function name (plus the path in
front of it).

Jigal van Hemert

2016-05-10 09:11:01 UTC

Permalink

Hi,

I just sent you a modified (untested) version of wec_config by email.

Hopefully all necessary modifications are in this version to make it
compatible with TYPO3 6.2.

--
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org

Wiesław Golsz

2016-05-07 21:53:39 UTC

Permalink

Excuse me: this frament should be as:

/function countFeatures() {//
// global $TYPO3_DB;//
// *if**(is_object($TYPO3_DB) && $TYPO3_DB->link) {*//
// $table = 'tx_wecconfig_features';//
// $res = $TYPO3_DB->exec_SELECTquery ('count(uid)', $table,
'deleted=0');//
// $row = $TYPO3_DB->sql_fetch_assoc($res);//
//
// $count = $row['count(uid)'];//
// } else {//
// $count = 0;//
// }//
// return $count;//
//}/

Where *line 192* is: /if(is_object($TYPO3_DB) && $TYPO3_DB->link) {//

/ERROR

Fatal error: Cannot access protected property
TYPO3\CMS\Core\Database\DatabaseConnection::$link in
/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/features/class.tx_wecconfig_features.php
on line 192

Why cannot access to database???

Regars,

Post by WiesÅaw Golsz
/function countFeatures() {//
// global $TYPO3_DB;//
// //
// $table = 'tx_wecconfig_features';//
// $res = $TYPO3_DB->exec_SELECTquery ('count(uid)',
$table, 'deleted=0');//
// $row = $TYPO3_DB->sql_fetch_assoc($res);//
//
// $count = $row['count(uid)'];//
// } else {//
// $count = 0;//
// }//
// return $count;//
// }/
Fatal error: Cannot access protected property
TYPO3\CMS\Core\Database\DatabaseConnection::$link in
/home/www/6.bestchoicefx.com/typo3conf/ext/wec_config/features/class.tx_wecconfig_features.php
on line 192
Where line 192 is: /if(is_object($TYPO3_DB) && $TYPO3_DB->link) {//
/

Post by Jigal van Hemert
Hi,

Most of the time these errors are not hard to fix, although it can
take some time if you encounter a lot of them each time you fix one.
In TYPO3 4.3 (if I remember correctly) a mechanism was introduced to
automatically load classes in PHP. This meant that you didn't need to
use lines like
require_once( PATH_t3libclass . 't3lib_extobjbase.php');
in your code. You could just use the class and it would automatically
be loaded.
Many extension authors still kept those lines because the code still
worked. In 6.x the autoloader was changed and these errors appeared
if extension code still used those unnecessary lines.

Post by WiesÅaw Golsz
Q3. How to fix this error

Look carefully at the error! It says that the require_once didn't
work in
....../ext/wec_config/features/class.tx_wecconfig_features.php on
line 31.
Edit the file and put two slashes in front of the 'require_once' on
the mentioned line. This turns the rest of the line into a comment
//require_once( PATH_t3libclass . 't3lib_extobjbase.php');
(I don't know the exact line, but you get the idea)
- in 6.x all class names in the core were changed; the names are now
easier to read
- 6.2 still knows the old names like the existed in 4.5 and
extensions can still use the old names
- 7.6 doesn't know the old names anymore, but there is an extension
'compatibility6' which makes it possible to still use the old class
names; it comes with a price, performance is a lot worse with that
extension installed
- 8.x don't know the old names and there is no extension that adds
support for those old class names
You can use a lot of 4.x compatible extensions with 6.2, but it would
be wise to look for alternatives before upgrading to 7 LTS or 8.x.
Alternative would be to edit the extensions and replace all the old
class names with the new names. In some cases more code needs to be
replaced, but you could hire a TYPO3 programmer to make those changes.