From mbarts at gmx.ch  Sun Sep  9 18:14:58 2007
From: mbarts at gmx.ch (Martin Borer)
Date: Sun, 09 Sep 2007 18:14:58 +0200
Subject: [TYPO3-irre] Localization of child records
In-Reply-To: <mailman.1.1186427083.26139.typo3-project-irre@lists.netfielders.de>
References: <mailman.1.1186427083.26139.typo3-project-irre@lists.netfielders.de>
Message-ID: <mailman.1.1189354488.14754.typo3-project-irre@lists.netfielders.de>

Hi all,

could someone help me? I've patched my T3-Core but I have no idea how 
the localization of IRRE child records has to be done.

I've made a "classical" localization with the kickstarter Extension (2 
Tables, inline Records as integer). After replacing the integers with 
inline relations the localization doesn't seam to work in irre view.

Has someone a smal example? tca.php, ext_tables.php, ext_tables.sql? Or 
an extension?

I know that localization of irre is still experimental, but I want to 
experiment a little bit with it... ;)

Greets
Martin

From jsegars at alumni.rice.edu  Thu Sep 13 22:53:57 2007
From: jsegars at alumni.rice.edu (Jeff Segars)
Date: Thu, 13 Sep 2007 20:53:57 +0000 (UTC)
Subject: [TYPO3-irre]  Sorting of IRRE Children
Message-ID: <mailman.1.1189716837.29729.typo3-project-irre@lists.netfielders.de>

Hey Olly,
I've got an interesting issue with sorting of IRRE children. In my
extension, I have categories and child records within those
categories.  The child records can be manually sorted within the
backend list view and this manual sorting is reused when displaying
the records in the frontend.

When I add a new child record via IRRE, the sorting for every child
record within a category is updated. I return to list view and they're
all grouped together at the top of the list. Obviously, this messes up
the previous manual sort order but I don't think there's a clear way
that the list view sorting of all records and IRRE sorting of child
records can co-exist.

Is there any way to disable manual sorting for a particular table
within IRRE while still allowing it within the standard backend list
view?

Thanks,
Jeff



From oh at inpublica.de  Fri Sep 14 08:25:56 2007
From: oh at inpublica.de (Oliver Hader)
Date: Fri, 14 Sep 2007 08:25:56 +0200
Subject: [TYPO3-irre] Sorting of IRRE Children
In-Reply-To: <mailman.1.1189716837.29729.typo3-project-irre@lists.netfielders.de>
References: <mailman.1.1189716837.29729.typo3-project-irre@lists.netfielders.de>
Message-ID: <mailman.1.1189751133.18265.typo3-project-irre@lists.netfielders.de>

Hi Jeff,

Jeff Segars schrieb:
> Hey Olly,
> I've got an interesting issue with sorting of IRRE children. In my
> extension, I have categories and child records within those
> categories.  The child records can be manually sorted within the
> backend list view and this manual sorting is reused when displaying
> the records in the frontend.
> 
> When I add a new child record via IRRE, the sorting for every child
> record within a category is updated. I return to list view and they're
> all grouped together at the top of the list. Obviously, this messes up
> the previous manual sort order but I don't think there's a clear way
> that the list view sorting of all records and IRRE sorting of child
> records can co-exist.
> 
> Is there any way to disable manual sorting for a particular table
> within IRRE while still allowing it within the standard backend list
> view?

If using $TCA[<table>]['ctrl']['sortby'] for both - list view and IRRE -
it will lead to conflicts. IRRE creates the sort indexes only for the
scope of the parent object and the list module does this for all child
records.

But you could use and individual field that stores the sorting if used
in the IRRE context by setting the 'foreign_sortby' property, e.g.

$TCA[<table>]['columns'][<field>]['config'] = array(
  'type' => 'inline',
  'foreign_table' => 'tx_myext_child',
  'foreign_field' => 'parent',
  'foreign_sortby' => 'sorting',
  ...
);

Hope that helps in your situation.


olly
-- 
Oliver Hader
http://inpublica.de/

From jsegars at alumni.rice.edu  Fri Sep 14 16:32:33 2007
From: jsegars at alumni.rice.edu (Jeff Segars)
Date: Fri, 14 Sep 2007 14:32:33 +0000 (UTC)
Subject: [TYPO3-irre] Sorting of IRRE Children
References: <mailman.1.1189716837.29729.typo3-project-irre@lists.netfielders.de>
	<mailman.1.1189751133.18265.typo3-project-irre@lists.netfielders.de>
Message-ID: <mailman.1.1189780353.14812.typo3-project-irre@lists.netfielders.de>

Hey Olly,
Thanks for the followup :)  I had thought about the approach you
recommend and its probably the best option I have right now.

For my particular case, I don't think its the ideal long term scenario
though.  Since there is manual sorting for the list module, the only
time the IRRE sorting will be used is in IRRE view.  I think it would
probably be more intuitive to the user if there was no IRRE sorting
option at all since the sorting doesn't change anything externally. I
can see users getting confused as they move child records around and
it doesn't change list view or the frontend.

What would you think about adding TCA option to turn sorting off,
regardless of the settings in the foreign table.  My situation may be
unique enough that this setting doesn't make sense for the core, but
I'll leave that up to you ;)

Thanks!
Jeff


Oliver Hader <oh at inpublica.de> wrote:
>  If using $TCA[<table>]['ctrl']['sortby'] for both - list view and
> IRRE - it will lead to conflicts. IRRE creates the sort indexes only
> for the scope of the parent object and the list module does this for
> all childrecords.

>  But you could use and individual field that stores the sorting if
> usedin the IRRE context by setting the 'foreign_sortby' property, e.g.

>  $TCA[<table>]['columns'][<field>]['config'] = array(
>    'type' => 'inline',
>    'foreign_table' => 'tx_myext_child',
>    'foreign_field' => 'parent',
>    'foreign_sortby' => 'sorting',
>    ...
>  );




From kraftb at kraftb.at  Thu Sep 27 01:15:16 2007
From: kraftb at kraftb.at (Bernhard Kraft)
Date: Thu, 27 Sep 2007 01:15:16 +0200
Subject: [TYPO3-irre] Localization of child records
In-Reply-To: <mailman.1.1186427083.26139.typo3-project-irre@lists.netfielders.de>
References: <mailman.1.1186427083.26139.typo3-project-irre@lists.netfielders.de>
Message-ID: <mailman.1.1190848542.13042.typo3-project-irre@lists.netfielders.de>

Oliver Hader wrote:
> Hi folks,
> 
> one of the missing features of IRRE is the possibility to translate
> child records when viewing the parent record. I've created an initial
> and experimental fix for this issue.
> 
> The patch was created again TYPO3 4.1.2/4.1.3-dev and can be found at:
> http://bugs.typo3.org/view.php?id=6087

Hi Oliver !


I took a look at your patch and noticed that it mainyl is about properly 
copying the sub-records when a container gets localized.

But what about possiblities like known from Flexform sections 
"lDEF/vDEF" paradigma:

So that you could either have different sub-records in each containr - 
or a strict 1:1 binding - meaning if you have for example:


Product Record (container)
  |-- Price Variant A (sub-record)
  |-- Price Variant B (sub-record)
  |-- Price Variant C (sub-record)

and you translate the "Product record" that it is a "must" to have 3 
sub-records in the translated record again - so that the translated 
sub-records are directly bound to the original language containr. Like 
when you move around a Price in the original-language container it will 
also move in all translated containers.


For more info see my RFC sent to the core list (I guess I should have 
done that later - after discussing this with you here - sorry for being 
so quick in posting to the core list :( )
http://lists.netfielders.de/pipermail/typo3-team-core/2007-September/009323.html

I also attached my patch to your bugnote:
http://bugs.typo3.org/view.php?id=6087

---------------------------

PS: I introduced some new "terms" in this scenario. When I talk of an 
"sub-record" or "IRRE-record" i mean a sub-element - embedded into a 
"container record" ...

So a "product" would for example be a "container" while all the 
price-variants available for this product - which are visible/rendered 
in the IRRE field would get called "sub-record"

I do not know if you have choosen similar terms for this purpose - but I 
think it is neccessary to come to a common language in this case - as 
else we both would mean different things all the time.

---------------------------

greets,
Bernhard