Re: [TYPO3-english] sr_feuser_register and admin review

[Oliver Salzburg]

On 2011-12-15 08:06, Katja Lampela wrote:

Hi,

I can't get the admin review feature functioning in registration process.

Anybody can confirm this doesn't work or maybe I have something wrong in
my setup?

TYPO3 4.5.8
sr_feuser_register 2.6.1

if I have enableAdminReview=1
the admin gets the approval email ok, but clicking the approval link
doesn't activate the feuser. The record stays hidden.

If I disable this and let the registrator himself activate the
registration with the link he gets in confirmation email, then
activation works ok.



If I remember correctly, both things have to happen.
The admin approves the user, but the user still has to activate the
account. The first step is to allow the user into the system, the second
step is still in place to confirm the email address.

Does that make any sense?
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] sr_feuser_register and admin review

[Katja Lampela]

Hi,

15.12.2011 10:43, Oliver Salzburg kirjoitti:

If I remember correctly, both things have to happen.
The admin approves the user, but the user still has to activate the
account. The first step is to allow the user into the system, the second
step is still in place to confirm the email address.

Does that make any sense?


Yes. The procedure seems to go like this:
1. registration -> 2. confirm mail to registrator + confirmation -> 3. confirm 
mail to admin

and that last step should activate (clicking the approve registration link) the 
registration, but it doesnt.

If I disable the review process the second step already activates the 
registration.

--
With kind regards

Katja Lampela
*Lieska-tuotanto*
www.lieska.net

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

Re: [TYPO3-english] sr_feuser_register and admin review

[Nicola Cerchiari]

Hi Katja,
have you tried to remove the step of user confirmation keeping the admin
review? Does it work that way?

If I remember good I faced something similar with the same version of
sr_feuser and had to modify slightly the code...

When I'll have some spare time I'll check if I can find bac kthe
modification, sorry but some time has passed since ;)

Bests,
Nicola

2011/12/15 Katja Lampela 

> Hi,
>
> 15.12.2011 10:43, Oliver Salzburg kirjoitti:
>
>  If I remember correctly, both things have to happen.
>> The admin approves the user, but the user still has to activate the
>> account. The first step is to allow the user into the system, the second
>> step is still in place to confirm the email address.
>>
>> Does that make any sense?
>>
>
> Yes. The procedure seems to go like this:
> 1. registration -> 2. confirm mail to registrator + confirmation -> 3.
> confirm mail to admin
>
> and that last step should activate (clicking the approve registration
> link) the registration, but it doesnt.
>
> If I disable the review process the second step already activates the
> registration.
>
>
> --
> With kind regards
>
> Katja Lampela
> *Lieska-tuotanto*
> www.lieska.net
>
> __**_
> TYPO3-english mailing list
> TYPO3-english@lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-**english
>
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] sr_feuser_register and admin review

[Oliver Salzburg]

On 2011-12-15 09:47, Katja Lampela wrote:

Hi,

15.12.2011 10:43, Oliver Salzburg kirjoitti:

If I remember correctly, both things have to happen.
The admin approves the user, but the user still has to activate the
account. The first step is to allow the user into the system, the second
step is still in place to confirm the email address.

Does that make any sense?


Yes. The procedure seems to go like this:
1. registration -> 2. confirm mail to registrator + confirmation -> 3.
confirm mail to admin

and that last step should activate (clicking the approve registration
link) the registration, but it doesnt.

If I disable the review process the second step already activates the
registration.



Whenever there is email in play, I triple-check all email addresses and
especially sender/recipient names (if available to set). I've had tons
of issues where email addresses won't validate with swiftmailer and the
extension fails (sometimes silently). Same goes for reply-to addresses.

As a sidenote, if it is an option, I replaced sr_feuser_register with
datamints_feuser in my installation. Might be a valid option as well if
all else fails.

Cheers

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

[TYPO3-english] Problems with locallang.xml translation since 4.6

[Sören Kracker]

I can't get any other translations than default and de in 4.6. This all 
worked in 4.5!
This is really strange, because the content gets translated correctly 
(so language is set properly), but translations using locallang.xml 
don't work. Neither locallang of extensions (formhandler or overriding 
via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor 
translations via typoscript (using LLL:translation.xml:string) are 
working. TYPO3 finds the xml files and fetches default strings and those 
for de too, but for en I always get the default translation.
Is there any change regarding XLIFF? I have absolutely no idea what's 
wrong here.


I have this setting for language config and English:
config {
sys_language_overlay = hideNonTranslated
sys_language_mode = content_fallback
linkVars = L
}
[globalVar = GP:L = 1]
config {
sys_language_uid = 1
language = en
locale_all = en_GB
htmlTag_langKey = en
}
[global]

Simplified xml file (for formhandler):



module
Language labels for plugin tx_formhandler



Zurücksetzen


Reset


Reset




Thanks for your help in advance

Sören
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Sören Kracker]

Just made a test with other languages: ES+CZ work. It seems that TYPO3 
thinks that EN (sys_language_uid = 1) would be my default language. But 
that should be DE (sys_language_uid = 0). Any ideas?
I can't get any other translations than default and de in 4.6. This 
all worked in 4.5!
This is really strange, because the content gets translated correctly 
(so language is set properly), but translations using locallang.xml 
don't work. Neither locallang of extensions (formhandler or overriding 
via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor 
translations via typoscript (using LLL:translation.xml:string) are 
working. TYPO3 finds the xml files and fetches default strings and 
those for de too, but for en I always get the default translation.
Is there any change regarding XLIFF? I have absolutely no idea what's 
wrong here.


I have this setting for language config and English:
config {
sys_language_overlay = hideNonTranslated
sys_language_mode = content_fallback
linkVars = L
}
[globalVar = GP:L = 1]
config {
sys_language_uid = 1
language = en
locale_all = en_GB
htmlTag_langKey = en
}
[global]

Simplified xml file (for formhandler):



module
Language labels for plugin tx_formhandler



Zurücksetzen


Reset


Reset




Thanks for your help in advance

Sören
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

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

[TYPO3-english] extbase store data into 2 tables with one form

[rocky]

Hey,

I am trying to use Extbase and Fluid to develop an extension. The 
Frontend form has fields whose data will be stored in 2 tables when user 
clicked on "Submit". Is this doable by using Repository or I need to use 
PHP code directly?


Thanks in advance!

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

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Xavier Perseguers]

Hi Lars,

> I can imagine, that there is a better way then unset all unneeded keys…

Thanks for digging into this, I just reworked your patch to prevent a
manual loop over all keys and pushed it to Gerrit on behalf of yourself:

https://review.typo3.org/#change,7269

We have a short Skype meeting with Dominique in a few seconds for this
and other related L10n questions... :)

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

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

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

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Victor Livakovsky]

Hi, Sören.


Simplified xml file (for formhandler):



module
Language labels for plugin tx_formhandler



Zurücksetzen


Reset


Reset





Is it misspell in the mail or you really have two "en" sections in your 
locallang.xml file? Maybe this causes a problem? 


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

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Lars Patrick Heß]

Hi Xavier,

i had tested your code in a customer project and it does not work correctly, i 
had changed it to this:

protected function doParsingFromRootForElement(SimpleXMLElement $root, 
$element) {
$bodyOfFileTag = $root->data->languageKey;

// Check if the source llxml file contains localized 
records
$localizedBodyOfFileTag = 
$root->data->xpath("languageKey[@index='" . $this->languageKey . "']");
if ($element === 'target' && count($localizedBodyOfFileTag) == 
0) {
return array();
}

$parsedData = $this->getParsedDataForElement($bodyOfFileTag, 
$element);
if ($element === 'target' && isset($localizedBodyOfFileTag[0]) 
&& $localizedBodyOfFileTag[0] instanceof SimpleXMLElement) {
$parsedDataTarget = 
$this->getParsedDataForElement($localizedBodyOfFileTag[0], $element);
$mergedData = array_merge($parsedData, 
$parsedDataTarget);

if ($this->languageKey === 'default') {
$parsedData = array_intersect_key($mergedData, 
$parsedData);
$parsedData = array_intersect_key($mergedData, 
$parsedDataTarget);
} else {
$parsedData = array_intersect_key($mergedData, 
$parsedDataTarget);
}
}

return $parsedData;
}

in my dev-environment it works very well, but not in the preview-system :(… 
later i will test it further...


Am 15.12.2011 um 11:31 schrieb Xavier Perseguers:

> Hi Lars,
> 
>> I can imagine, that there is a better way then unset all unneeded keys…
> 
> Thanks for digging into this, I just reworked your patch to prevent a
> manual loop over all keys and pushed it to Gerrit on behalf of yourself:
> 
> https://review.typo3.org/#change,7269
> 
> We have a short Skype meeting with Dominique in a few seconds for this
> and other related L10n questions... :)
> 
> -- 
> Xavier Perseguers
> Release Manager TYPO3 4.6
> 
> TYPO3  inspiring people to share!
> Get involved: http://typo3.org
> 
> ___
> TYPO3-english mailing list
> TYPO3-english@lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

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

[TYPO3-english] TYPO3 - ORACLE

[Peter Löffelhardt]

Hello TYPO3 community,

for our current project it’s a must have to get TYPO3 running in association
with an ORACLE database
and the TYPO3 extension ‘TemplaVoila’. In addition it is necessary to run it
on TYPO3 version 4.5.8 or 
lower (due to the required PHP-Version).
 
Till now we didn’t solve this by ourselves so we are looking for an
experienced TYPO3 developer who
can setup a working installation based on the given requirements. Be assured
- you’ll get well paid!

 
In brief: We want you to provide an operative TYPO3 installation with
following requirements:
 
-  Newest TYPO3 version which is running on PHP version 5.2.x
(currently it is the 4.5.8)  

-  … in combination with an ORACLE database (10g)

-  running with an completely functional TemplaVoila installation

 
If you’re interested we please you to contact us!

 

 

 

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

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Sören Kracker]

Hi Victor,

sorry, yes, that was a  misspelling. There is only one key "en".
I've debugged in doParsingFromRootForElement in t3lib_l10n_parser_Llxml 
and there $this->languageKey is set to 'default' when calling 
example.com/en. So somehow my TYPO3 thinks en is default. Very strange...


Am 15.12.2011 11:42, schrieb Victor Livakovsky:

Hi, Sören.


Simplified xml file (for formhandler):



module
Language labels for plugin tx_formhandler



Zurücksetzen


Reset


Reset





Is it misspell in the mail or you really have two "en" sections in 
your locallang.xml file? Maybe this causes a problem?

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

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

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Dominique Feyer]

In 4.6 en === default it's not a bug currently but I understand your
needs and it make sense to change that.

Can you please open a bug on the forge issue tracker ?
http://forge.typo3.org/projects/team-translation/issues

Thanks

Sören Kracker wrote:
> I can't get any other translations than default and de in 4.6. This all
> worked in 4.5!
> This is really strange, because the content gets translated correctly
> (so language is set properly), but translations using locallang.xml
> don't work. Neither locallang of extensions (formhandler or overriding
> via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor
> translations via typoscript (using LLL:translation.xml:string) are
> working. TYPO3 finds the xml files and fetches default strings and those
> for de too, but for en I always get the default translation.
> Is there any change regarding XLIFF? I have absolutely no idea what's
> wrong here.
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Sören Kracker]

Thanks Dominique,
I've filed a bug report:
http://forge.typo3.org/issues/32590

Am 15.12.2011 12:04, schrieb Dominique Feyer:

In 4.6 en === default it's not a bug currently but I understand your
needs and it make sense to change that.

Can you please open a bug on the forge issue tracker ?
http://forge.typo3.org/projects/team-translation/issues

Thanks

Sören Kracker wrote:

I can't get any other translations than default and de in 4.6. This all
worked in 4.5!
This is really strange, because the content gets translated correctly
(so language is set properly), but translations using locallang.xml
don't work. Neither locallang of extensions (formhandler or overriding
via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor
translations via typoscript (using LLL:translation.xml:string) are
working. TYPO3 finds the xml files and fetches default strings and those
for de too, but for en I always get the default translation.
Is there any change regarding XLIFF? I have absolutely no idea what's
wrong here.

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

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

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Xavier Perseguers]

Hi Lars,

Could you please do your review in Gerrit? You just have to log on
https://review.typo3.org/#change,7269, put your typo3.org credentials
and put your comments rights into the patch by double-clicking.

So you found a bug in your code? Because I basically took your code. No
problem of course :)

Xavier

Lars Patrick Heß wrote:
> Hi Xavier,
> 
> i had tested your code in a customer project and it does not work correctly, 
> i had changed it to this:
> 
>   protected function doParsingFromRootForElement(SimpleXMLElement $root, 
> $element) {
>   $bodyOfFileTag = $root->data->languageKey;
> 
>   // Check if the source llxml file contains localized 
> records
>   $localizedBodyOfFileTag = 
> $root->data->xpath("languageKey[@index='" . $this->languageKey . "']");
>   if ($element === 'target' && count($localizedBodyOfFileTag) == 
> 0) {
>   return array();
>   }
> 
>   $parsedData = $this->getParsedDataForElement($bodyOfFileTag, 
> $element);
>   if ($element === 'target' && isset($localizedBodyOfFileTag[0]) 
> && $localizedBodyOfFileTag[0] instanceof SimpleXMLElement) {
>   $parsedDataTarget = 
> $this->getParsedDataForElement($localizedBodyOfFileTag[0], $element);
>   $mergedData = array_merge($parsedData, 
> $parsedDataTarget);
> 
>   if ($this->languageKey === 'default') {
>   $parsedData = array_intersect_key($mergedData, 
> $parsedData);
>   $parsedData = array_intersect_key($mergedData, 
> $parsedDataTarget);
>   } else {
>   $parsedData = array_intersect_key($mergedData, 
> $parsedDataTarget);
>   }
>   }
> 
>   return $parsedData;
>   }
> 
> in my dev-environment it works very well, but not in the preview-system :(… 
> later i will test it further...
> 
> 
> Am 15.12.2011 um 11:31 schrieb Xavier Perseguers:
> 
>> Hi Lars,
>>
>>> I can imagine, that there is a better way then unset all unneeded keys…
>> Thanks for digging into this, I just reworked your patch to prevent a
>> manual loop over all keys and pushed it to Gerrit on behalf of yourself:
>>
>> https://review.typo3.org/#change,7269
>>
>> We have a short Skype meeting with Dominique in a few seconds for this
>> and other related L10n questions... :)
>>
>> -- 
>> Xavier Perseguers
>> Release Manager TYPO3 4.6
>>
>> TYPO3  inspiring people to share!
>> Get involved: http://typo3.org
>>
>> ___
>> TYPO3-english mailing list
>> TYPO3-english@lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> 

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

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

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

Re: [TYPO3-english] TYPO3 - ORACLE

[Olivier Dobberkau]

Am 15.12.11 11:50, schrieb Peter Löffelhardt:

> -  Newest TYPO3 version which is running on PHP version 5.2.x
> (currently it is the 4.5.8)  
> 
> -  … in combination with an ORACLE database (10g)
> 
> -  running with an completely functional TemplaVoila installation



Hi Peter,


TYPO3 and Oracle, a long standing love affair! Add Templavoila to it and
you have a drama and not a romance. If you place them on an old stage
like php 5.2 then you wont make it a classic but a box-office desaster.
Add some more to cast list like DAM, Versions and Workspaces and you
have a japanese godzilla movie full of destruction.


My 5 cents here: Drop Oracle as a requirement. It will save you lots of
money implementing stuff all over again. Dont forget those Oracle DBAs
can get MySQL support from a company called Oracle.

If you still need support then feel free to query some of the listed
companies here: (disclosure: mine is one of them)

http://association.typo3.org/members/ref/assoc/memberlist/32/

Best regards,

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

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Dominique Feyer]

Hi everybody,

During the review of the patch available on Gerrit, I think that it's
not a bug ;) but a feature.

4.6 introduce a caching mechanism for the l10n parser (based on the
caching framework).

Lars, can you try this procedure:

Add this line in your localconf.php
$GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;

Clear configuration cache and reload the backend, you now have a new
item in the clear cache menu to clear the l10n cache.

After that reload your frontend.

Please do that on a vanilla 4.6 (without your patch).

Keep me in touche with the result.

Bests

Xavier Perseguers wrote:
> Hi Lars,
> 
> Could you please do your review in Gerrit? You just have to log on
> https://review.typo3.org/#change,7269, put your typo3.org credentials
> and put your comments rights into the patch by double-clicking.
> 
> So you found a bug in your code? Because I basically took your code. No
> problem of course :)
> 
> Xavier
> 
> Lars Patrick Heß wrote:
>> Hi Xavier,
>>
>> i had tested your code in a customer project and it does not work correctly, 
>> i had changed it to this:
>>
>>  protected function doParsingFromRootForElement(SimpleXMLElement $root, 
>> $element) {
>>  $bodyOfFileTag = $root->data->languageKey;
>>
>>  // Check if the source llxml file contains localized 
>> records
>>  $localizedBodyOfFileTag = 
>> $root->data->xpath("languageKey[@index='" . $this->languageKey . "']");
>>  if ($element === 'target' && count($localizedBodyOfFileTag) == 
>> 0) {
>>  return array();
>>  }
>>
>>  $parsedData = $this->getParsedDataForElement($bodyOfFileTag, 
>> $element);
>>  if ($element === 'target' && isset($localizedBodyOfFileTag[0]) 
>> && $localizedBodyOfFileTag[0] instanceof SimpleXMLElement) {
>>  $parsedDataTarget = 
>> $this->getParsedDataForElement($localizedBodyOfFileTag[0], $element);
>>  $mergedData = array_merge($parsedData, 
>> $parsedDataTarget);
>>
>>  if ($this->languageKey === 'default') {
>>  $parsedData = array_intersect_key($mergedData, 
>> $parsedData);
>>  $parsedData = array_intersect_key($mergedData, 
>> $parsedDataTarget);
>>  } else {
>>  $parsedData = array_intersect_key($mergedData, 
>> $parsedDataTarget);
>>  }
>>  }
>>
>>  return $parsedData;
>>  }
>>
>> in my dev-environment it works very well, but not in the preview-system :(… 
>> later i will test it further...
>>
>>
>> Am 15.12.2011 um 11:31 schrieb Xavier Perseguers:
>>
>>> Hi Lars,
>>>
 I can imagine, that there is a better way then unset all unneeded keys…
>>> Thanks for digging into this, I just reworked your patch to prevent a
>>> manual loop over all keys and pushed it to Gerrit on behalf of yourself:
>>>
>>> https://review.typo3.org/#change,7269
>>>
>>> We have a short Skype meeting with Dominique in a few seconds for this
>>> and other related L10n questions... :)
>>>
>>> -- 
>>> Xavier Perseguers
>>> Release Manager TYPO3 4.6
>>>
>>> TYPO3  inspiring people to share!
>>> Get involved: http://typo3.org
>>>
>>> ___
>>> TYPO3-english mailing list
>>> TYPO3-english@lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> 
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Dominique Feyer]

And before further work on this issue, please can you try this:

4.6 introduce a caching mechanism for the l10n parser (based on the
caching framework).

Add this line in your localconf.php
$GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;

Clear configuration cache and reload the backend, you now have a new
item in the clear cache menu to clear the l10n cache.

After that reload your frontend.

Please do that on a vanilla 4.6 (without patch).

Keep me in touche with the result.

On a local setup of the 4.7 I override en key, with
$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['typo3/sysext/lang/locallang_core.xml'][]
= 'fileadmin/locallang_core.xml';

And my english string are used (not the default key from the lang
extension).

Sören Kracker wrote:
> Thanks Dominique,
> I've filed a bug report:
> http://forge.typo3.org/issues/32590
> 
> Am 15.12.2011 12:04, schrieb Dominique Feyer:
>> In 4.6 en === default it's not a bug currently but I understand your
>> needs and it make sense to change that.
>>
>> Can you please open a bug on the forge issue tracker ?
>> http://forge.typo3.org/projects/team-translation/issues
>>
>> Thanks
>>
>> Sören Kracker wrote:
>>> I can't get any other translations than default and de in 4.6. This all
>>> worked in 4.5!
>>> This is really strange, because the content gets translated correctly
>>> (so language is set properly), but translations using locallang.xml
>>> don't work. Neither locallang of extensions (formhandler or overriding
>>> via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor
>>> translations via typoscript (using LLL:translation.xml:string) are
>>> working. TYPO3 finds the xml files and fetches default strings and those
>>> for de too, but for en I always get the default translation.
>>> Is there any change regarding XLIFF? I have absolutely no idea what's
>>> wrong here.
>> ___
>> TYPO3-english mailing list
>> TYPO3-english@lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] Problems with locallang.xml translation since 4.6

[Sören Kracker]

You didn't mean testing on 4.6.0 or?
I tested on 4.6.1 and it makes no difference there.

Am 15.12.2011 15:24, schrieb Dominique Feyer:

And before further work on this issue, please can you try this:

4.6 introduce a caching mechanism for the l10n parser (based on the
caching framework).

Add this line in your localconf.php
$GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;

Clear configuration cache and reload the backend, you now have a new
item in the clear cache menu to clear the l10n cache.

After that reload your frontend.

Please do that on a vanilla 4.6 (without patch).

Keep me in touche with the result.

On a local setup of the 4.7 I override en key, with
$GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']['typo3/sysext/lang/locallang_core.xml'][]
= 'fileadmin/locallang_core.xml';

And my english string are used (not the default key from the lang
extension).

Sören Kracker wrote:

Thanks Dominique,
I've filed a bug report:
http://forge.typo3.org/issues/32590

Am 15.12.2011 12:04, schrieb Dominique Feyer:

In 4.6 en === default it's not a bug currently but I understand your
needs and it make sense to change that.

Can you please open a bug on the forge issue tracker ?
http://forge.typo3.org/projects/team-translation/issues

Thanks

Sören Kracker wrote:

I can't get any other translations than default and de in 4.6. This all
worked in 4.5!
This is really strange, because the content gets translated correctly
(so language is set properly), but translations using locallang.xml
don't work. Neither locallang of extensions (formhandler or overriding
via $GLOBALS['TYPO3_CONF_VARS']['SYS']['locallangXMLOverride'] ) nor
translations via typoscript (using LLL:translation.xml:string) are
working. TYPO3 finds the xml files and fetches default strings and those
for de too, but for en I always get the default translation.
Is there any change regarding XLIFF? I have absolutely no idea what's
wrong here.

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

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

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

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Lars Patrick Heß]

Hi Dominique,

i had cleared the cache many times, the language cache too… When i replace the 
function t3lib_div::readLLfile with the old one from a 4.5 branch, everything 
works fine!

The new mechanism does sometimes not load the correct translations. In my 
opinion it happens when you are loading a language from a XML filere where 
nocht all possible langiage-keys are available in your target language. Now 
when a language-file is loaded by the locallangXMLOverride mechanism for 
merging with the original one, correct translations will be replaced with wrong 
loaded ones.


Am 15.12.2011 um 15:21 schrieb Dominique Feyer:

> Hi everybody,
> 
> During the review of the patch available on Gerrit, I think that it's
> not a bug ;) but a feature.
> 
> 4.6 introduce a caching mechanism for the l10n parser (based on the
> caching framework).
> 
> Lars, can you try this procedure:
> 
> Add this line in your localconf.php
> $GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;
> 
> Clear configuration cache and reload the backend, you now have a new
> item in the clear cache menu to clear the l10n cache.
> 
> After that reload your frontend.
> 
> Please do that on a vanilla 4.6 (without your patch).
> 
> Keep me in touche with the result.
> 
> Bests
> 
> Xavier Perseguers wrote:
>> Hi Lars,
>> 
>> Could you please do your review in Gerrit? You just have to log on
>> https://review.typo3.org/#change,7269, put your typo3.org credentials
>> and put your comments rights into the patch by double-clicking.
>> 
>> So you found a bug in your code? Because I basically took your code. No
>> problem of course :)
>> 
>> Xavier
>> 
>> Lars Patrick Heß wrote:
>>> Hi Xavier,
>>> 
>>> i had tested your code in a customer project and it does not work 
>>> correctly, i had changed it to this:
>>> 
>>> protected function doParsingFromRootForElement(SimpleXMLElement $root, 
>>> $element) {
>>> $bodyOfFileTag = $root->data->languageKey;
>>> 
>>> // Check if the source llxml file contains localized 
>>> records
>>> $localizedBodyOfFileTag = 
>>> $root->data->xpath("languageKey[@index='" . $this->languageKey . "']");
>>> if ($element === 'target' && count($localizedBodyOfFileTag) == 
>>> 0) {
>>> return array();
>>> }
>>> 
>>> $parsedData = $this->getParsedDataForElement($bodyOfFileTag, 
>>> $element);
>>> if ($element === 'target' && isset($localizedBodyOfFileTag[0]) 
>>> && $localizedBodyOfFileTag[0] instanceof SimpleXMLElement) {
>>> $parsedDataTarget = 
>>> $this->getParsedDataForElement($localizedBodyOfFileTag[0], $element);
>>> $mergedData = array_merge($parsedData, 
>>> $parsedDataTarget);
>>> 
>>> if ($this->languageKey === 'default') {
>>> $parsedData = array_intersect_key($mergedData, 
>>> $parsedData);
>>> $parsedData = array_intersect_key($mergedData, 
>>> $parsedDataTarget);
>>> } else {
>>> $parsedData = array_intersect_key($mergedData, 
>>> $parsedDataTarget);
>>> }
>>> }
>>> 
>>> return $parsedData;
>>> }
>>> 
>>> in my dev-environment it works very well, but not in the preview-system :(… 
>>> later i will test it further...
>>> 
>>> 
>>> Am 15.12.2011 um 11:31 schrieb Xavier Perseguers:
>>> 
 Hi Lars,
 
> I can imagine, that there is a better way then unset all unneeded keys…
 Thanks for digging into this, I just reworked your patch to prevent a
 manual loop over all keys and pushed it to Gerrit on behalf of yourself:
 
 https://review.typo3.org/#change,7269
 
 We have a short Skype meeting with Dominique in a few seconds for this
 and other related L10n questions... :)
 
 -- 
 Xavier Perseguers
 Release Manager TYPO3 4.6
 
 TYPO3  inspiring people to share!
 Get involved: http://typo3.org
 
 ___
 TYPO3-english mailing list
 TYPO3-english@lists.typo3.org
 http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>> 
> ___
> TYPO3-english mailing list
> TYPO3-english@lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

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

[TYPO3-english] Repeated headers with Templavoilà

[Sergio]

Hi,

a few months ago, it happened to me that when I pushed the button "Set"
twice in the headers part inside a Templavoilà template, the headers were
repeated twice (strange behaviour, I don't know if this caused that). I
don't remember how I solved it, and it has happened to me again. Would you
know? I tried to delete the Templavoià template and created a new one, but
the headers are still repeated when I refresh the frontend cache. That's
strange...

Thanks in advance,
Sergio
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] Repeated headers with Templavoilà

[Sergio]

I realized the problem in the same instant I posted this thread! I use the
same Flexible content element twice on the page.

Would you know if there is a way to avoid repeating the headers?

Thanks in advance,
Sergio
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

[TYPO3-english] Re: Repeated headers with Templavoilà

[Kay Strobach]

On 15.12.2011 18:23, Sergio wrote:
> I realized the problem in the same instant I posted this thread! I use the
> same Flexible content element twice on the page.
> 
> Would you know if there is a way to avoid repeating the headers?
> 
> Thanks in advance,
> Sergio


Yeah, add the related header to the page template and not to the fce -
as far as i remember this is a known bug.

Regards
Kay
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

[TYPO3-english] XCLASS with Extbase Extensions?

[Alexander Dick]

Hi List,

is there any way how one can extend/override an Extbase Class, like the 
traditional XCLASS functionality? Didn't find anything yet.


best regards
Alex
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Lars Patrick Heß]

Now i am working with this version:

protected function doParsingFromRootForElement(SimpleXMLElement $root, 
$element) {
$bodyOfFileTag = $root->data->languageKey;

// Check if the source llxml file contains localized 
records
$localizedBodyOfFileTag = 
$root->data->xpath("languageKey[@index='" . $this->languageKey . "']");

// If no records found return empty array
if ($element === 'target' && count($localizedBodyOfFileTag) === 
0)
return array();

$parsedData = $this->getParsedDataForElement($bodyOfFileTag, 
$element);
if ($element === 'target' && isset($localizedBodyOfFileTag[0]) 
&& $localizedBodyOfFileTag[0] instanceof SimpleXMLElement) {
$parsedTargetData = 
$this->getParsedDataForElement($localizedBodyOfFileTag[0], $element);

$mergedData = array_merge($parsedData, 
$parsedTargetData);
if ($this->languageKey === 'default') {
$mergedData = array_intersect_key($mergedData, 
$parsedTargetData);
$parsedData = array_intersect_key($mergedData, 
$parsedData);
} else{
$parsedData = array_intersect_key($mergedData, 
$parsedTargetData);
}
}

return $parsedData;
}

Currently it looks good… I hope this fixes the bug on the right way…

Am 15.12.2011 um 16:22 schrieb Lars Patrick Heß:

> Hi Dominique,
> 
> i had cleared the cache many times, the language cache too… When i replace 
> the function t3lib_div::readLLfile with the old one from a 4.5 branch, 
> everything works fine!
> 
> The new mechanism does sometimes not load the correct translations. In my 
> opinion it happens when you are loading a language from a XML filere where 
> nocht all possible langiage-keys are available in your target language. Now 
> when a language-file is loaded by the locallangXMLOverride mechanism for 
> merging with the original one, correct translations will be replaced with 
> wrong loaded ones.
> 
> 
> Am 15.12.2011 um 15:21 schrieb Dominique Feyer:
> 
>> Hi everybody,
>> 
>> During the review of the patch available on Gerrit, I think that it's
>> not a bug ;) but a feature.
>> 
>> 4.6 introduce a caching mechanism for the l10n parser (based on the
>> caching framework).
>> 
>> Lars, can you try this procedure:
>> 
>> Add this line in your localconf.php
>> $GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['cache']['clear_menu'] = TRUE;
>> 
>> Clear configuration cache and reload the backend, you now have a new
>> item in the clear cache menu to clear the l10n cache.
>> 
>> After that reload your frontend.
>> 
>> Please do that on a vanilla 4.6 (without your patch).
>> 
>> Keep me in touche with the result.
>> 
>> Bests
>> 
>> Xavier Perseguers wrote:
>>> Hi Lars,
>>> 
>>> Could you please do your review in Gerrit? You just have to log on
>>> https://review.typo3.org/#change,7269, put your typo3.org credentials
>>> and put your comments rights into the patch by double-clicking.
>>> 
>>> So you found a bug in your code? Because I basically took your code. No
>>> problem of course :)
>>> 
>>> Xavier
>>> 
>>> Lars Patrick Heß wrote:
 Hi Xavier,
 
 i had tested your code in a customer project and it does not work 
 correctly, i had changed it to this:
 
protected function doParsingFromRootForElement(SimpleXMLElement $root, 
 $element) {
$bodyOfFileTag = $root->data->languageKey;
 
// Check if the source llxml file contains localized 
 records
$localizedBodyOfFileTag = 
 $root->data->xpath("languageKey[@index='" . $this->languageKey . "']");
if ($element === 'target' && count($localizedBodyOfFileTag) == 
 0) {
return array();
}
 
$parsedData = $this->getParsedDataForElement($bodyOfFileTag, 
 $element);
if ($element === 'target' && isset($localizedBodyOfFileTag[0]) 
 && $localizedBodyOfFileTag[0] instanceof SimpleXMLElement) {
$parsedDataTarget = 
 $this->getParsedDataForElement($localizedBodyOfFileTag[0], $element);
$mergedData = array_merge($parsedData, 
 $parsedDataTarget);
 
if ($this->languageKey === 'default') {
$parsedData = array_intersect_key($mergedData, 
 $parsedData);
$parsedData = array_intersect_key($mergedData, 
 $parsedDataTarget);
} else {
$parsedData = array_intersect_key($mergedData, 
 $parsedDataTarget);
}
}
 
return $parsedData;
}
>>

Re: [TYPO3-english] XCLASS with Extbase Extensions?

[Lars Patrick Heß]

You have to use the DependencyInjection system, you can do something like this 
in your typoscript configuration to override controllers etc.:

config.tx_extbase {
objects {
Tx_FooExt_Controller_OriginalController.className = 
Tx_MyExt_Controller_OtherController
}
}

:-)

Am 15.12.2011 um 20:03 schrieb Alexander Dick:

> Hi List,
> 
> is there any way how one can extend/override an Extbase Class, like the 
> traditional XCLASS functionality? Didn't find anything yet.
> 
> best regards
> Alex
> ___
> TYPO3-english mailing list
> TYPO3-english@lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

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

Re: [TYPO3-english] XCLASS with Extbase Extensions?

[Alexander Dick]

Aaaah - cool thanks! :-)

And how does the new class have to be defined?

class Tx_MyExt_Controller_OtherController {

or

class Tx_MyExt_Controller_OtherController extends 
Tx_FooExt_Controller_OriginalController {


}

thanks
Alex

Am 15.12.2011 20:10, schrieb Lars Patrick Heß:

You have to use the DependencyInjection system, you can do something like this 
in your typoscript configuration to override controllers etc.:

config.tx_extbase {
objects {
Tx_FooExt_Controller_OriginalController.className = 
Tx_MyExt_Controller_OtherController
}
}

:-)

Am 15.12.2011 um 20:03 schrieb Alexander Dick:


Hi List,

is there any way how one can extend/override an Extbase Class, like the 
traditional XCLASS functionality? Didn't find anything yet.

best regards
Alex
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english



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

Re: [TYPO3-english] XCLASS with Extbase Extensions?

[Lars Patrick Heß]

Both of them is possible, but if you want change a functionality you have to 
extend from the original one :-)

Am 15.12.2011 um 20:13 schrieb Alexander Dick:

> Aaaah - cool thanks! :-)
> 
> And how does the new class have to be defined?
> 
> class Tx_MyExt_Controller_OtherController {
> 
> or
> 
> class Tx_MyExt_Controller_OtherController extends 
> Tx_FooExt_Controller_OriginalController {
> 
> }
> 
> thanks
> Alex
> 
> Am 15.12.2011 20:10, schrieb Lars Patrick Heß:
>> You have to use the DependencyInjection system, you can do something like 
>> this in your typoscript configuration to override controllers etc.:
>> 
>> config.tx_extbase {
>>  objects {
>>  Tx_FooExt_Controller_OriginalController.className = 
>> Tx_MyExt_Controller_OtherController
>>  }
>> }
>> 
>> :-)
>> 
>> Am 15.12.2011 um 20:03 schrieb Alexander Dick:
>> 
>>> Hi List,
>>> 
>>> is there any way how one can extend/override an Extbase Class, like the 
>>> traditional XCLASS functionality? Didn't find anything yet.
>>> 
>>> best regards
>>> Alex
>>> ___
>>> TYPO3-english mailing list
>>> TYPO3-english@lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>> 
> ___
> TYPO3-english mailing list
> TYPO3-english@lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

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

Re: [TYPO3-english] XCLASS with Extbase Extensions?

[Lars Patrick Heß]

Now I am no longer sit in a train, so I can write a bit more:

Normaly you used in your inject*-Functions phps typehinting, so you must extend 
from the original class or interface.

When it is a controller you have to extend from 
"Tx_Extbase_MVC_Controller_ActionController", i don't know if extbase DI system 
checks if the overwritten controller class is an instance of the original one…


Am 15.12.2011 um 20:21 schrieb Lars Patrick Heß:

> Both of them is possible, but if you want change a functionality you have to 
> extend from the original one :-)
> 
> Am 15.12.2011 um 20:13 schrieb Alexander Dick:
> 
>> Aaaah - cool thanks! :-)
>> 
>> And how does the new class have to be defined?
>> 
>> class Tx_MyExt_Controller_OtherController {
>> 
>> or
>> 
>> class Tx_MyExt_Controller_OtherController extends 
>> Tx_FooExt_Controller_OriginalController {
>> 
>> }
>> 
>> thanks
>> Alex
>> 
>> Am 15.12.2011 20:10, schrieb Lars Patrick Heß:
>>> You have to use the DependencyInjection system, you can do something like 
>>> this in your typoscript configuration to override controllers etc.:
>>> 
>>> config.tx_extbase {
>>> objects {
>>> Tx_FooExt_Controller_OriginalController.className = 
>>> Tx_MyExt_Controller_OtherController
>>> }
>>> }
>>> 
>>> :-)
>>> 
>>> Am 15.12.2011 um 20:03 schrieb Alexander Dick:
>>> 
 Hi List,
 
 is there any way how one can extend/override an Extbase Class, like the 
 traditional XCLASS functionality? Didn't find anything yet.
 
 best regards
 Alex
 ___
 TYPO3-english mailing list
 TYPO3-english@lists.typo3.org
 http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>> 
>> ___
>> TYPO3-english mailing list
>> TYPO3-english@lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> 

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

[TYPO3-english] Salted hashes and security

[Victor Livakovsky]

Hi, List.

I just started using TYPO3 4.6, where 'rsaauth' and 'saltedpasswords' 
extensions are installed from very beginning. That's nice and good for 
security. But I can't understand, why system report claims, that website is 
insecure, when I set "BE.forceSalted" and unset "BE.updatePasswd"? Yes, I 
know, that user, created by Install Tool will no longer be able to log in 
with this configuration - but this only increases security, since, even if 
someone gets access to Install Tool, he still will not be able to get to BE.
Or I don't understand something? 


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

Re: [TYPO3-english] Salted hashes and security

[Markus Klein]

Hi!

What is the exact message shown by the report?

Kind regards
Markus

> -Original Message-
> From: typo3-english-boun...@lists.typo3.org 
> [mailto:typo3-english-boun...@lists.typo3.org] On Behalf Of Victor Livakovsky
> Sent: Thursday, December 15, 2011 6:04 PM
> To: typo3-english@lists.typo3.org
> Subject: [TYPO3-english] Salted hashes and security
> 
> Hi, List.
> 
> I just started using TYPO3 4.6, where 'rsaauth' and 'saltedpasswords'
> extensions are installed from very beginning. That's nice and good for 
> security. But I can't understand, why system report claims, that
> website is insecure, when I set "BE.forceSalted" and unset "BE.updatePasswd"? 
> Yes, I know, that user, created by Install Tool will no
> longer be able to log in with this configuration - but this only increases 
> security, since, even if someone gets access to Install Tool, he
> still will not be able to get to BE.
> Or I don't understand something?
> 
> ___
> TYPO3-english mailing list
> TYPO3-english@lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

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

[TYPO3-english] gridelements in 4.6

[Domi]

Hello

I just try out the new gridelements extension, which brings very nice 
DragnDrop feature for the content elements in the BE. I created some CE 
Layouts and was able including them into the page.
How do I adjust my CEs frontend rendering? there is no additional 
markup. Also the grid container and grid container columns in the tab 
extended are empty.


Does anybody has a working configuration of gridelements?

Thanks

Cheers Dominic
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

[TYPO3-english] cooluri bug

[Douglas La Farge]

Not sure where to report this so I'll post it here.

I went to COMPARE in the install tool and was given this notice:

There seems to be a number of differencies between the database and the 
selected SQL-file.
Please select which statements you want to execute in order to update your 
database:


Removing tables (rename with prefix)

select/deselect all

 ALTER TABLE link_cache RENAME zzz_deleted_link_cache; 
Records in table: 35

 ALTER TABLE link_oldlinks RENAME zzz_deleted_link_oldlinks; 

This is clearly incorrect as if I execute the above queries cooluri breaks.

I'm guessing it's a bug in cooluri 1.0.28. maybe it's typo3 4.6.1.

regards,
doug
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Re: [TYPO3-english] SOLVED Extensions go blank in BE after upgrade

[yanagik317]

Bah, two strikes on me.

PHP was configured to log to a file but the destination directory 
didn't exist.  Once created, it became apparent what the problem was.  
I had a soft link named /docroot/typo3conf pointing to 
/not/a/docroot/typo3conf, and the extensions were basically trying to 
include /not/a/docroot/typo3/init.php, which didn't exist.  Once fixed, 
all the extensions became lively in BE.


Testing upgrading from 4.2.12 to 4.4.12.  I'm encouraged by otherwise 
good results so far despite skipping 4.3, if anyone finds this of 
interest.


Thanks to those that replied.

--Koji

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

Re: [TYPO3-english] Bug in locallangXMLOverride mechanism since TYPO3 4.6?

[Xavier Perseguers]

Hi Lars,

Lars Patrick Heß wrote:
> $mergedData = array_intersect_key($mergedData, $parsedTargetData);
>   $parsedData = array_intersect_key($mergedData, 
> $parsedData);

Thanks for this. But please, as you have done a code review on
review.typo3.org, please, please put your comment right into the code,
just as the others did. On the review page you see the different files
being changed, click on the "Side-by-Side" link in the "Diff" column to
show the patch and then double click on any line to put a comment.

To help you I just put your comment as you should have done it because
giving a -1 by code review and telling us "you must also intersect with
$parsedDataTarget array" is not really helpful but putting this comment
right into the code *is*.

Thanks

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

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

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

Re: [TYPO3-english] gridelements in 4.6

[Chris Müller]

Hi Domi,

to render your content elements in frontend just use the following 
typoscript snippet. In the following example you have a two column layout.


tt_content.gridelements_pi1 {
  20.10.setup {
# 1 = The uid of your CE backend layout
1 {
  columns {
# 1 = the first column number
# you can use stdWrap properties
1 {
  renderObj =< tt_content
  wrap = |
}
# 2 = the second column number
2 {
  renderObj =< tt_content
  wrap = |
}
  }

  # here you can use also stdWrap properties
  # also you can include fields from your
  # flexform configuration (here: color)
  stdWrap.wrap = |
  stdWrap.insertData = 1
}
  }
}

I hope this helps you.

Regards,
Chris.

Am 16.12.2011 04:33, schrieb Domi:

Hello

I just try out the new gridelements extension, which brings very nice
DragnDrop feature for the content elements in the BE. I created some CE
Layouts and was able including them into the page.
How do I adjust my CEs frontend rendering? there is no additional
markup. Also the grid container and grid container columns in the tab
extended are empty.

Does anybody has a working configuration of gridelements?

Thanks

Cheers Dominic


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

Re: [TYPO3-english] gridelements in 4.6

[Domi]

Ah, thanks for this snippet, now I know how to deal.

But still: whats about the tab extended, where I see two empty drop 
downs? How can I deal with them?


Cheers Dominic
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english