Project

General

Profile

Actions

Bug #16558

closed

ERROR when you install the extension

Added by Toralf Lenz over 17 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
felogin
Target version:
-
Start date:
2006-09-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

caller t3lib_DB::sql_query

ERROR Unknown column 'tx_newloginbox_show_forgot_password' in 'where clause'

lastBuiltQuery SELECT count(*)
FROM tt_content
WHERE
CType="list" AND list_type="newloginbox_pi1" AND
(
tx_newloginbox_show_forgot_password OR
tx_newloginbox_header_welcome OR
tx_newloginbox_msg_welcome OR
tx_newloginbox_header_success OR
tx_newloginbox_msg_success OR
tx_newloginbox_header_error OR
tx_newloginbox_msg_error OR
tx_newloginbox_header_status OR
tx_newloginbox_msg_status OR
tx_newloginbox_header_logout OR
tx_newloginbox_msg_logout
)

debug_backtrace SC_mod_tools_em_index->main // SC_mod_tools_em_index->showExtDetails // ext_update->access // t3lib_DB->sql_query // t3lib_DB->debug

v3.0.0
(issue imported from #M4208)


Related issues 3 (0 open3 closed)

Has duplicate TYPO3 Core - Bug #16866: SQL error on install v.3.0.1Closed2007-01-18

Actions
Has duplicate TYPO3 Core - Bug #17129: Unknown column tx_newloginbox_show_forgot_passwordClosed2007-03-18

Actions
Has duplicate TYPO3 Core - Bug #17511: newloginbox is missing sqlClosed2007-08-09

Actions
Actions #1

Updated by Stefan Strasser over 17 years ago

I can't reproduce it on a blank installation of Typo3 4.0.2 and newloginbox V 3.0.0

Did you only import newloginbox or did you import and install it?
What Typo3-Version do You use?
Which extensions are installed?

Actions #2

Updated by Toralf Lenz over 17 years ago

TYPO3 4.0.2

localconf.php:
$TYPO3_CONF_VARS['SYS']['sqlDebug'] = '1';

"Install extension..." or "Remove extension" and always the error appears!

Actions #3

Updated by Stefan Strasser over 17 years ago

error is only being displayed with sqldebug turned on

Actions #4

Updated by Stefan Strasser over 17 years ago

That is not really a bug. It does not have any negative effect to the function of the extension. In contrary: this error is used to check something.

The cause of this sql-error is the following:
- In the extension manager there is in each extension at top right a menu containing 'Information', 'Edit Files' and eventually 'Update'. This menu you see if you install or remove the extension or if you look at the details of an extension.
- In the newloginbox-extension there is an update-function because in ancient times the configuration-items were stored in separate table-fields, but now in the flexform-xml-field. And in the update-api there is a mechanism to check if the update-entry should be displayed in the menu or not. Usually the update-entry won't show if the extension is already up to date.
- To perform this check the newloginbox-extension looks for content in the fields mentioned in the sql-error-message. If these fields are not found, an sql error occurs and newloginbox is convinced that there is no update necessary as the old fields are not there.

The code of this check is in function access() in class.ext_update.php.

Actions #5

Updated by Stefan Strasser over 17 years ago

As it is not really a bug...

Actions

Also available in: Atom PDF