[TYPO3-dev] How to get default XML data from known DS?

Kay Strobach typo3 at kay-strobach.de
Mon Mar 4 13:40:13 CET 2013


Hello JoH,

sad to hear, that tceMain doesn't add defaults, if no value is added :(
Perhaps you can use the hook in tcemain to add this behaviour (preDBHook
or similar, it's easy to find).

@gridelements, i want to build sth. like tvframework without tv and with
pure ts.

I already did a lot of work to achieve that goal.
http://www.typo3-themes.org/themedirectory/extensions/

I wanted to use gridelements, but was blocked by the fact, that i still
need DB records to provide elements. So i use fluidcontent for now to
provide the content elements known by tvframework.

-> If you know a way to add everything use by gridelements using TS,
please point me to the correct docs :D

You can find all the code on github, but not yet in (TER and forge):
https://github.com/kaystrobach?tab=repositories

Thanks in advice
Kay

Am 04.03.13 13:25, schrieb JoH asenau:
>> shouldn't tcemain do exactly that?
> 
> I didn't find a method generating the pi_flexform XML to be saved to the
> database directly from the DS. Each of the methods expects the data to
> be already available so it just has to be converted based on a
> comparison between incoming data and data structure.
> 
> What I would like to do is to convert the datastructure XML to some
> default data XML directly without having to provide the incoming data
> via an editing form.
> 
>> PS:
>>    i tried to contact you recently over startnext, and otherways, but
>>    got no answer :(
>>
>>    I'm working on ext:themes and tried to decide, wether gridelements or
>>    fedext should be used primary, keeping compatibility to both
> 
> I noticed that, when the message came in, but was too busy then.
> Afterwards I forgot about it - sorry for that!
> 
> Actually grid elements are meant to be a replacement for FCEs that
> provide structured containers for usual content elements only. They
> might contain additional configuration like checkboxes or selectboxes to
> activate certain JS effects (which is why I have been asking for a
> solution here), but they should not be abused as "individual content
> elements".
> 
> Additionally grid elements provide a way to handle "unsued elements" via
> colPos -2, drag & drop for moving, copying (with CTRL key) and creation
> of new elements, pasting elements as reference, references to a whole
> page instead of just one element and a "get me a copy form another page"
> solution.
> 
> So if you want to move the backend layouts of pages to the next level
> and want to get some comfortable features to improve your working
> performance as a power user, grid elements are the way to go. If you
> just need a new content element type with a certain set of input fields,
> some TCA in extTables.php +  some appropriate TS for a new CType should
> do a better job.
> 
> HTH
> 
> Joey
> 


-- 
http://www.kay-strobach.de - Open Source Rocks

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

Answer was useful - feel free to donate:
  -
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2
  - https://flattr.com/profile/kaystrobach




More information about the TYPO3-dev mailing list