Project

General

Profile

Actions

Bug #18361

closed

locallang_db.xml parse(?) problem

Added by Daniel Matuschek over 16 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2008-03-04
Due date:
% Done:

0%

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

Description

After upgrading from Typo3 4.1 to 4.2beta, I'm not able to use extensions that were created with the kickstarter.
Error message is:
The file "... locallang_db.xml" is no TYPO3 language file!

Downgrading to Typo3 4.1 solves this problem.

There are no problems with the frontend rendering of the extension.

(issue imported from #M7741)

Actions #1

Updated by Steffen Kamper over 16 years ago

this doesn't happens with "all" extensions. Please look to this extension cause this error, you may see an empty file, delete it!

Actions #2

Updated by Daniel Matuschek over 16 years ago

The locallang_db.xml file is not empty and the problem occurs with every extension I created with a previous version of the kickstarter (don't know anymore which version was used).

The locallang_db is not an empty file, but correct XML.

Looking at the code the the current version of the kickstarter creates, it looks different then the old code in ext_tables.php:

code of the old kickstarter:
t3lib_extMgm::addPlugin(array('LLL:EXT:dm_gallery/locallang_db.xml:tt_content.list_type_pi1', $_EXTKEY.'_pi1'),'list_type');

code of current kickstarter:
t3lib_extMgm::addPlugin(array('LLL:EXT:test/locallang_db.xml:tt_content.CType_pi1', $_EXTKEY.'_pi1'),'CType');

With 4.1 the old code is still working without problems.

Actions #3

Updated by Daniel Matuschek over 16 years ago

Seems to work again in 4.2RC1

Actions #4

Updated by Ingo Renner over 16 years ago

no change required

Actions

Also available in: Atom PDF